[U-Boot] Not getting any prompt on hyper terminal
Dear All,
I am new to this U-Boot boot loader environment. We have a AMCC PPC 440EP processor board which is derived from AMCC Yosemite board. I meant, we have prepared (customised) our own board which is equivalent to AMCC Yosemite board. For this board, I build the U-Boot boot loader with the help of ELDK on Ubuntu x86 host system. However, I have modified the following file contents as per my board and processor attributes.
file name located directory ------------- ------------------------ 1) yosemite.h u-boot/include/configs 2) board.c u-boot/arch/powerpc/lib 3) init.S and yosemite.c u-boot/board/amcc/yosemite 4) start.S u-boot/arch/powerpc/cpu/ppc4xx After above four file modifications, the u-boot.bin file is created and able to load into our board. However, we are NOT getting any prompt on the hyper terminal. When we debug the sources through our laterbach debugger, we found that the control entered into the relocate_code() function which is called from board_init_f () function. The board_init_f () function is available in board.c file. However, the relocate_code() is implemented in the start.S file. As this is a assembly file, I am not able to understand it completely.
The memories that we are using in our board are DDR SDRAM (64MB - Bank0), Boot flash (32MB - CS0), Application flash (32MB - CS1). We modified these parameters in the yosemite.h file and after loading the u-boot.bin file, we are able to see all the memories configured correctly. However, we are not getting the U-Boot prompt on the hyper terminal.
Please let me know, If I am missing any thing here.
Any help would be greatly appreciated.
Thanks and Regards, Srinivas G
On Tue, Oct 26, 2010 at 3:21 PM, Srinivas Ganji srinivasganji@gmail.comwrote:
Dear All,
I am new to this U-Boot boot loader environment. We have a AMCC PPC 440EP processor board which is derived from AMCC Yosemite board. I meant, we have prepared (customised) our own board which is equivalent to AMCC Yosemite board. For this board, I build the U-Boot boot loader with the help of ELDK on Ubuntu x86 host system. However, I have modified the following file contents as per my board and processor attributes.
file name located directory
- yosemite.h u-boot/include/configs
- board.c u-boot/arch/powerpc/lib
- init.S and yosemite.c u-boot/board/amcc/yosemite
- start.S u-boot/arch/powerpc/cpu/ppc4xx
After above four file modifications, the u-boot.bin file is created and able to load into our board. However, we are NOT getting any prompt on the hyper terminal. When we debug the sources through our laterbach debugger, we found that the control entered into the relocate_code() function which is called from board_init_f () function. The board_init_f () function is available in board.c file. However, the relocate_code() is implemented in the start.S file. As this is a assembly file, I am not able to understand it completely.
The memories that we are using in our board are DDR SDRAM (64MB - Bank0), Boot flash (32MB - CS0), Application flash (32MB - CS1). We modified these parameters in the yosemite.h file and after loading the u-boot.bin file, we are able to see all the memories configured correctly. However, we are not getting the U-Boot prompt on the hyper terminal.
Please let me know, If I am missing any thing here.
Any help would be greatly appreciated.
Thanks and Regards, Srinivas G
Dear All,
I am getting the following output on the hyper terminal without U-Boot prompt.
U-Boot 2010.09-00369-g1ba91ba-dirty (Oct 26 2010 - 10:35:31) CPU: AMCC PowerPC 440EP Rev. C at 333.333 MHz (PLB=133 OPB=66 EBC=33 PCI=33 MH z) Bootstrap Option E - Boot ROM Location EBC (16 bits) Internal PCI arbiter enabled, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache Board: Yosemite - AMCC PPC440EP Evaluation Board, Rev. 0, PCI-Async=33 MHz I2C: ready DRAM: 64 MiB After init sequence functions completed! addr = 04000000 Before AND - Top of RAM usable for U-Boot at: 04000000 Top of RAM usable for U-Boot at: 04000000 Reserving 822k for U-Boot at: 03f32000 Reserving 1032k for malloc() at: 03e30000 Reserving 144 Bytes for Board Info at: 03e2ff70 Reserving 88 Bytes for Global Data at: 03e2ff18 Stack Pointer at: 03e2fef8 bd->bi_memsize: 67108864 New Stack Pointer is: 03e2fef8 before relocate_code() By the way, I build the sources with the following commands from u-boot directory.
make YOSEMITE_config make all
Please let me know, if you need any additional information. I will provide.
Thanks and Regards, Srinivas G
Dear Srinivas Ganji,
In message AANLkTimNnBbsL4DbW2QDciwET4dqjN4E8V_ZTGAgoESg@mail.gmail.com you wrote:
on Ubuntu x86 host system. However, I have modified the following file contents as per my board and processor attributes.
file name located directory
- yosemite.h u-boot/include/configs
- board.c u-boot/arch/powerpc/lib
- init.S and yosemite.c u-boot/board/amcc/yosemite
- start.S u-boot/arch/powerpc/cpu/ppc4xx
You should never need to modify arch/powerpc/lib/board.c and arch/powerpc/cpu/ppc4xx/start.S. I recommend you undo thse changes.
Also, you should create your own board configuration instead of messing with the yosemite files.
...
Reserving 144 Bytes for Board Info at: 03e2ff70 Reserving 88 Bytes for Global Data at: 03e2ff18 Stack Pointer at: 03e2fef8 bd->bi_memsize: 67108864 New Stack Pointer is: 03e2fef8 before relocate_code()
This problem in handled in the FAQ; please see http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation
make YOSEMITE_config
I am pretty sure this is NOT the command you used. Note thate case matters.
Best regards,
Wolfgang Denk
On Tue, Oct 26, 2010 at 3:48 PM, Wolfgang Denk wd@denx.de wrote:
Dear Wolfgang Denk,
Thanks for your information.
You should never need to modify arch/powerpc/lib/board.c and arch/powerpc/cpu/ppc4xx/start.S. I recommend you undo thse changes.
We have modified the start.S file for the following #define as our flash start address is 0xFF000000 according to flash size.
#define CONFIG_SYS_FLASH_BASE 0xf8000000 changed to # define CONFIG_SYS_FLASH_BASE 0xff000000
We have added only debug statements in board.c. We did not change any value/variable in this file.
Also, you should create your own board configuration instead of messing with the yosemite files.
We are using yosemite board configuration files as we derived our board as per the yosemite board. Please let me know, if there is any document / README for creating the own config files.
...
Reserving 144 Bytes for Board Info at: 03e2ff70 Reserving 88 Bytes for Global Data at: 03e2ff18 Stack Pointer at: 03e2fef8 bd->bi_memsize: 67108864 New Stack Pointer is: 03e2fef8 before relocate_code()
This problem in handled in the FAQ; please see http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation
Sure. I will look into it. I will update if there is any luck for me.
make YOSEMITE_config
I am pretty sure this is NOT the command you used. Note thate case matters.
The README file which is available in the main u-boot directory says use CAPITAL letters YOSEMITE only. That is the reason, I used it. I also saw in the google where they used the CAPITAL letters for building the u-boot.bin file for their specific board. Please let me know, If I am wrong or any thing I am missing here.
Thanks and Regards, Srinivas G
Dear Srinivas Ganji,
In message AANLkTimgrGaX47YgywVo-jDXA-pQpaf0sBB8c0BE5xGi@mail.gmail.com you wrote:
You should never need to modify arch/powerpc/lib/board.c and arch/powerpc/cpu/ppc4xx/start.S. I recommend you undo thse changes.
We have modified the start.S file for the following #define as our flash start address is 0xFF000000 according to flash size.
Please look at the code. You do not have to change this file. Just provide a correct definition in your board config file.
Please do not meddle with global files.
We have added only debug statements in board.c. We did not change any value/variable in this file.
"Only adding debug statements" may break a board as well, if you don't know exactly what you are doing.
We are using yosemite board configuration files as we derived our board as per the yosemite board. Please let me know, if there is any document / README for creating the own config files.
There is a little help in the README.
make YOSEMITE_config
I am pretty sure this is NOT the command you used. Note thate case matters.
The README file which is available in the main u-boot directory says use CAPITAL letters YOSEMITE only. That is the reason, I used it. I also saw in the google where they used the CAPITAL letters for
I really have no idea what you are talking about: there is not a single reference to Yosemite (in whatever spelling) in the README.
And the make target is "yosemite_config", and has always been like that. If this is different for you, your source tree must be seriously modified (read: messed up).
Best regards,
Wolfgang Denk
participants (2)
-
Srinivas Ganji -
Wolfgang Denk