Hi,
We are working with T2080RDB based custom board.
It boots from NOR Flash. UBoot booting often crashes, but sometimes succeeds with few exceptions in between booting. Please find the attached file for the UBoot failure logs.
Can somebody help us to figure out the reason for UBoot crashing?
Below are NOR Flash and clock details used on the board:
- 256MB NOR flash (PC28F00BM29EWHA)
- DDR3L and System Reference clock 66.66 MHz
Below details are for attached logs
- U-boot booting log on second revision board for failure scenario
- U-boot booting log on second revision board for success scenario
- RCW values
Original Attachment has been moved to: U_boot_log_success.txt.zip
Original Attachment has been moved to: U-boot_log_Failure.txt.zip
Original Attachment has been moved to: RCW_Values.txt.zip
Hi,
When an empty custom board comes, need I only burn RCW and Uboot?
What about the flash map address for your board?
I burn the RCW(e8000000) and Uboot(eff40000), and have no print in console...
Expect for your reply, and Thank you very much.
> I burn the RCW(e8000000) and Uboot(eff40000)
Which tool you've used and which board initialization file?
Is the NOR Flash size 256 MB?
Hi, Dear ufedor:
I used codewarrior 10.5.1 and the initialization file is "T2080RDB-PCIe_init_core.tcl".
My Nor Flash size is 128MB.
And I debuged the UBOOT, it says "0xfffffffc is empty string"....
Expect for your reply, and Thank you very much. Wish you a nice day.
In the original wording it is written:
> Below are NOR Flash and clock details used on the board:
> - 256MB NOR flash (PC28F00BM29EWHA)
Now you wrote:
> My Nor Flash size is 128MB.
Which is wrong?
It is needed to inspect the processor connection schematics.
This can be conveniently done if you create a Technical Case:
eh....,Sorry, I am another one, and My board's flash size is 128MB.
Please create a Technical Case:
OK
Use a debugger, connect to the board in case of success and failure and dump DDR controller registers values.