[U-Boot-Users] Use reset CMD to start another u-boot failed.
The original u-boot running on board was burn AT 0xFFF00000, (Flash is mapped to 0xFE000000-0xFFFFFFFF) The CFG_RESET_ADDRESS = 0xFE000000
The original and new u-boot file difference is only two place. 1. CONFIG_AUTOBOOT_PROMPT (use it to verify the new u-boot startup correctly) 2. board/myboard/config.mk->TEXT_BASE = 0xFE000000 Then I place the new u-boot.bin file to the 0xFE000000, and then run the "reset" cmd from original u-boot's prompt.
but it's seem the new u-boot was not startup. the console still print the original u-boot's CONFIG_AUTOBOOT_PROMPT.
Am I miss some step? Or some where need to pay attention to?
============ The original u-boot flinfo. Original u-boot.bin was place to the FFF00000-FFF3FFFF(2 sector) CFG_ENV_ADDR = FFF40000(1 sector),CFG_RESET_ADDRESS = 0xFE000000
cilon=> flinfo
Bank # 1: Intel 28F128J3A (16 Mbit, 128 x 128K) Size: 16 MB in 128 Sectors Sector Start Addresses: FE000000 FE020000 FE040000 FE060000 FE080000 FE0A0000 FE0C0000 FE0E0000 FE100000 FE120000 FE140000 FE160000 FE180000 FE1A0000 FE1C0000 FE1E0000 FE200000 FE220000 FE240000 FE260000 FE280000 FE2A0000 FE2C0000 FE2E0000 FE300000 FE320000 FE340000 FE360000 FE380000 FE3A0000 FE3C0000 FE3E0000 FE400000 FE420000 FE440000 FE460000 FE480000 FE4A0000 FE4C0000 FE4E0000 FE500000 FE520000 FE540000 FE560000 FE580000 FE5A0000 FE5C0000 FE5E0000 FE600000 FE620000 FE640000 FE660000 FE680000 FE6A0000 FE6C0000 FE6E0000 FE700000 FE720000 FE740000 FE760000 FE780000 FE7A0000 FE7C0000 FE7E0000 FE800000 FE820000 FE840000 FE860000 FE880000 FE8A0000 FE8C0000 FE8E0000 FE900000 FE920000 FE940000 FE960000 FE980000 FE9A0000 FE9C0000 FE9E0000 FEA00000 FEA20000 FEA40000 FEA60000 FEA80000 FEAA0000 FEAC0000 FEAE0000 FEB00000 FEB20000 FEB40000 FEB60000 FEB80000 FEBA0000 FEBC0000 FEBE0000 FEC00000 FEC20000 FEC40000 FEC60000 FEC80000 FECA0000 FECC0000 FECE0000 FED00000 FED20000 FED40000 FED60000 FED80000 FEDA0000 FEDC0000 FEDE0000 FEE00000 FEE20000 FEE40000 FEE60000 FEE80000 FEEA0000 FEEC0000 FEEE0000 FEF00000 FEF20000 FEF40000 FEF60000 FEF80000 FEFA0000 FEFC0000 FEFE0000
Bank # 2: Intel 28F128J3A (16 Mbit, 128 x 128K) Size: 16 MB in 128 Sectors Sector Start Addresses: FF000000 FF020000 FF040000 FF060000 FF080000 FF0A0000 FF0C0000 FF0E0000 FF100000 FF120000 FF140000 FF160000 FF180000 FF1A0000 FF1C0000 FF1E0000 FF200000 FF220000 FF240000 FF260000 FF280000 FF2A0000 FF2C0000 FF2E0000 FF300000 FF320000 FF340000 FF360000 FF380000 FF3A0000 FF3C0000 FF3E0000 FF400000 FF420000 FF440000 FF460000 FF480000 FF4A0000 FF4C0000 FF4E0000 FF500000 FF520000 FF540000 FF560000 FF580000 FF5A0000 FF5C0000 FF5E0000 FF600000 FF620000 FF640000 FF660000 FF680000 FF6A0000 FF6C0000 FF6E0000 FF700000 FF720000 FF740000 FF760000 FF780000 FF7A0000 FF7C0000 FF7E0000 FF800000 FF820000 FF840000 FF860000 FF880000 FF8A0000 FF8C0000 FF8E0000 FF900000 FF920000 FF940000 FF960000 FF980000 FF9A0000 FF9C0000 FF9E0000 FFA00000 FFA20000 FFA40000 FFA60000 FFA80000 FFAA0000 FFAC0000 FFAE0000 FFB00000 FFB20000 FFB40000 FFB60000 FFB80000 FFBA0000 FFBC0000 FFBE0000 FFC00000 FFC20000 FFC40000 FFC60000 FFC80000 FFCA0000 FFCC0000 FFCE0000 FFD00000 FFD20000 FFD40000 FFD60000 FFD80000 FFDA0000 FFDC0000 FFDE0000 FFE00000 FFE20000 FFE40000 FFE60000 FFE80000 FFEA0000 FFEC0000 FFEE0000 FFF00000 (RO) FFF20000 (RO) FFF40000 (RO) FFF60000 FFF80000 FFFA0000 FFFC0000 FFFE0000
Leon.Z leon.kernel@gmail.com 2008-04-14
Hi Leon,
You could help us a little answer your questions by giving some more details - pretty obvious things like architecture or board name come to mind...
The original u-boot running on board was burn AT 0xFFF00000, (Flash is mapped to 0xFE000000-0xFFFFFFFF) The CFG_RESET_ADDRESS = 0xFE000000
What was the original U-Boot? Was that a configuration in mainline?
Why on earth are you trying to tamper with CFG_RESET_ADDRESS? This should really not be changed as it is only used to do force a reset of a board *for certain architectures*. I am not even sure that CFG_RESET_ADDRESS is relevant for your board. Moreover if you read the source code, this address is usually a *nonexistant* address to force a machine check exception. It is definitely not a hook to start a different incarnation of U-Boot.
The original and new u-boot file difference is only two place.
- CONFIG_AUTOBOOT_PROMPT (use it to verify the new u-boot startup correctly)
- board/myboard/config.mk->TEXT_BASE = 0xFE000000
Then I place the new u-boot.bin file to the 0xFE000000, and then run the "reset" cmd from original u-boot's prompt.
but it's seem the new u-boot was not startup. the console still print the original u-boot's CONFIG_AUTOBOOT_PROMPT.
Am I miss some step? Or some where need to pay attention to?
The short answer is - only change what you need in your configuration and replace the "original u-boot". I have no idea why changing CONFIG_AUTOBOOT_PROMPT needs a separate U-Boot at all.
The original u-boot flinfo. Original u-boot.bin was place to the FFF00000-FFF3FFFF(2 sector) CFG_ENV_ADDR = FFF40000(1 sector),CFG_RESET_ADDRESS = 0xFE000000
cilon=> flinfo
Bank # 1: Intel 28F128J3A (16 Mbit, 128 x 128K) Size: 16 MB in 128 Sectors Sector Start Addresses: FE000000 FE020000 FE040000 FE060000 FE080000
[....]
Without any details about your board, this information is pretty useless to us.
Cheers Detlev
participants (2)
-
Detlev Zundel -
Leon.Z