Reviving bricked device
Łukasz Wójcik
lukasz.wojcik at zoho.com
Tue Jan 9 09:59:20 CET 2024
Hi there,
Good day to you guys in new year. I am seeking advice on 'reviving'
bricked device. I have recently bricked my customer's device that is
running their own version of Uboot. Something went wrong during update.
I already have a working version of a binary. Uboot lies in NOR flash
chip, and the layout is as follows:
uboot 0x00000000 - 0x000dffff (size 0x000e0000, 896KB)
shmoo 0x000e0000 - 0x000effff (size 0x00010000, 64KB)
uboot-env 0x000f0000 - 0x000fffff (size 0x00010000, 64KB)
I'm not an Uboot expert, but I think 'u-boot.bin' contains environment
variables as well (or so it seems scanning it using 'strings'). How
should I program the chip so that it layout after the programming
conforms to the above memory map ?
Programming the 'executable' seems easy enough, I just put it at the
address 0x0, but how do I program environment variables at 0xf0000 ? Or
is this portion only for new environment variables ?
I would appreciate any sort of clues and suggestions,
Best regards,
-ŁW
More information about the U-Boot
mailing list