I do have connection to my usb/putty and thats it! Don’t ask how but the SDCARD silver slot came off… for a while there I was getting my tft and the usb/putty route and could always right arrow key then make selection using keyboard value. I think I TFT’d something for another which I don’t get, must’ve renamed bad file and tft took it and installed it. I do recall going from NAND to eMMC
gave it a shot for the first time… after unplugging and plugging the power back in… all looks completed but still not booting…
D:\ser6MAX\Downloads\mtk_uartboot-v0.1.1-x86_64-pc-windows-msvc>mtk_uartboot.exe -p mt7986-ram-ddr4-bl2.bin --aarch64 -f openwrt-24.10.0-mediatek-filogic-bananapi_bpi-r3-snand-bl31-uboot.fip mtk_uartboot - 0.1.1 Using serial port: COM11 Handshake… hw code: 0x7986 hw sub code: 0x8a00 hw ver: 0xca01 sw ver: 0x1 Baud rate set to 460800 sending payload to 0x201000… Checksum: 0xae50 Setting baudrate back to 115200 Jumping to 0x201000 in aarch64… Waiting for BL2. Message below:
NOTICE: BL2: v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7986-ram-ddr4) NOTICE: BL2: Built : 23:09:37, Feb 3 2025 NOTICE: WDT: Cold boot NOTICE: WDT: disabled NOTICE: CPU: MT7986 (2002MHz) NOTICE: EMI: Using DDR4 settings NOTICE: EMI: Detected DRAM size: 2048MB NOTICE: EMI: complex R/W mem test passed NOTICE: Starting UART download handshake …
BL2 UART DL version: 0x10 Baudrate set to: 921600 FIP sent.
NOTICE: Received FIP 0x10efe9 @ 0x40400000 …
even after power cycle no cigar. anything i am missing here?
It gave you a uboot in ram of board,so afrer mtk_uartboot exits open minicom or screen on same uart to enter this temporary uboot to flash any of the accessible storages (nand/nor,emmc)
no dice good sir.
@frank-w hi sir, any thoughts on why all sends to ram just when i open the serial through putty or others its just blank and hitting enter doesn’t bring up the commands prompt?
Which files have you used? You need special bl2 to get it working…when both (ram-bl2 and fip) are transferred your board ahould be in uboot…depending on autoboot maybe further,but you should see anything on uart with minicom except it hangs and does not print something after you switched…so maybe you have to hurry after fip was transferred
based on video it looks good so far…but noticed ch340…is this the internal usb2serial on r3mini or an external one? remember ch340 can be 5v which may damage the board
external on r3… not the mini… i did use your files but saw they were for the mini… do you have for the non mini? also… i have the switch hot glued so no way it can switch to 5v. plus… if i had it on 5v… I wouldn’t have gotten as far as i did… load up the terminal faster after its loaded… will try momentarily…
No,not yet needed as r3 has sd slot. But basicly it is same soc so it should basicly work (but pinctrl could be different,so maybe no peripheral,but uart should work).
You can build ram with my repo using ram as device in mtk-atf. See my github pipeline for steps to build all. You should disable bootcmd in uboot-builtin env (uEnv_bpi-r3.txt).
Have added ram build to last version in my repo (2025-01),but not tested yet.
edit: last ci-run missed the bl2.bin for ram, sorry, updated it
oh my thanks! when I attempted it, got far then it errored… will try now!
EDIT: no luck both emmc and nand says
Waiting for BL2. Message below:
==================================
==================================
Timeout waiting for specified message.
should the bl2 files be .bin or .img? I only see .img while the r3-mini files are bin.
For ramboot you need bl2.bin
Img is for flashing as it contains additional header
to confirm if i load the emmc file then the switches should be set to emmc as well? using the files youve provided, same thing happens, no uboot prompt when I load putty
Had not yet time to test ramboot on r3 using the generated binaries,sorry
ah, I understand. by when would you say your time would be open to investigate?
I try asap as i also need to test RSS on r3,but can’t give you exact timeline 