U-Boot doesnt allow settings (locked?)

Im currently adding support for a new board, everything works like a charm, but the flashing method is a bit messy (via directly flashing the image on the chip).

The problem is that during the selection phase of the boot method, uboot constantly defaults to option 3 (boot from nand), regardless of the key input. So i press the key 1 and uboot tells me: you selected option 3.
No key is working, the only one that works is key 2.

So i wanted to know if someone knows this kind of "locking" mechanism and can tell me how to "unlock" the bootloader.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2024.03.03 21:29:22 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot 1.1.3 (Apr 17 2018 - 16:46:28)


Board: Ralink APSoC DRAM:  64 MB

relocate_code Pointer at: 83fb8000

enable ephy clock...done. rf reg 29 = 5

SSC disabled.

spi_wait_nsec: 29 

spi device id: c8 40 17 c8 40 (4017c840)

Warning: un-recognized chip ID, please update bootloader!

raspi_read: from:30000 len:1000 

*** Warning - bad CRC, using default environment


============================================ 

Ralink UBoot Version: 4.3.0.0

-------------------------------------------- 

ASIC 7620_MP (Port5<->Phy)

DRAM component: 512 Mbits DDR, width 16

DRAM bus: 16 bit

Total memory: 64 MBytes

Flash component: SPI Flash

Date:Apr 17 2018  Time:16:46:28

============================================ 

icache: sets:512, ways:4, linesz:32 ,total:65536

dcache: sets:256, ways:4, linesz:32 ,total:32768 


 ##### The CPU freq = 580 MHZ #### 

 estimate memory size =64 Mbytes


Please choose the operation: 

   1: Load system code to SDRAM via TFTP. 

   2: Load system code then write to Flash via TFTP. 

   3: Boot system code via Flash (default).

   4: Entr boot command line interface.

   7: Load Boot Loader code then write to Flash via Serial. 

   9: Load Boot Loader code then write to Flash via TFTP. 

       0 

   

3: System Boot system code via Flash.

## Booting image at bc060000 ...

what's wrong with option 2 then ?

or did you mean 3 ?

Writing to flash is restricted, as uboot simply reboots after "fake" writing. It shows a progress bar but nothing really happens. Writing to ram (option 1) would do the trick, but as i mentioned the whole access to the bootloader is highly restricted.

if you can't get uboot to work, and there's no way of getting cli access to the stock fw, you don't really have much choice.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.