• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 531 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM437X: Booting through UART on custom board

Piyush Ghatole
Prodigy 70 points
Part Number: PROCESSOR-SDK-AM437X


Hello,

i am currently working on one of our product in which we used AM437x processor,
for that we developed our hardware and wanted to port Linux on it, I followed method given on the TI web to port u-boot on it,
please check below steps
1. Board boot sequence set to UART0
2. u-boot-spl.bin and u-boot.img generated for the board as per Getting start TI guide (Wiki)
3. Power ON the board, on the terminal I am getting CCCCCC.
4. Using the X-modem protocol I sent  u-boot-spl.bin and uploaded success.

Problem :
5. After this step I am not getting CCC on the terminal, even if I try to send a u-boot.img file, I am getting an ACK error.

Please help me to understand the problem and give a solution.

Regards,

Piyush Ghatole

  • 0
    TI__Guru**** 170011 points

    Hi Piyush,

    Piyush Ghatole said:

    Problem :
    5. After this step I am not getting CCC on the terminal, even if I try to send a u-boot.img file, I am getting an ACK error.

    You won't see CCCC on the terminal after u-boot-spl.bin is uploaded and executed. Instead the console should print SPL log.

    I am routing your query to our U-Boot expert for comments.

  • 0 in reply to Bin Liu
    TI__Guru 69950 points

    Hello,
    Is there any boot log from serial terminal after uploading "u-boot-spl.bin" over UART?
    If yes, can you share the log as an attachment?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 70 points

    Hello Hong & Bin,

    Thank you for responding...

    i am not getting any boot log from the serial terminal after uploading "u-boot-spl.bin".

    Best,

    Piyush Ghatole

  • 0 in reply to Piyush Ghatole
    TI__Guru 69950 points

    Hello,
    One of options is "attaching" JTAG to find out what happens.
    Do we have JTAG available on your board?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 70 points

    Hello, 

    Yes, I have XDS110.

    I have finished loading u-boot-spl.bin and u-boot-spl symbols at location 0x402F4000 using xds100 in ccs.

    under disassembly tab @0x402F4000 start function is located, but after step in it stuck at FIQ, 

    Can you please guide  me,  where to put breakpoints and check.

    Also I am referring TO training videos for u-boot debugging but in my board.c file I am unable to locate s.init function which is the starting function of SPL.

    Please suggest..

    Best,

    Piyush Ghatole

      

  • 0 in reply to Piyush Ghatole
    TI__Guru 69950 points

    Hello,
    Will you take a look at this e2e post on JTAG debug on SPL?
    e2e.ti.com/.../4432484
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 70 points

    Hello, 

    probably i made correct setup to debug the SPL,

    during the debug i noticed that debug files are not the same which i have generated for my custom board, e.g. i traced the path of board.c file during debugging and it was showing /boards/ti/AM43xx/board.c but expected path should be /boards/SE/ETH/board.c (it got created as per TI custom board porting guide).

    as i mentioned my code flow got stucked at FIQ, the last function executed before fiq is dm_fixup_for_dg_move(new_gd);

    if(gd->dm_root){

    new_gd->uclass_root->next->prev = new_gd->uclass_root;

    new_gd->uclass_root->prev->next = new_gd->uclass_root;

    }

    I also check and correlate the code flow suggested by you.

    Best,

    Piyush Ghatole

  • 0 in reply to Piyush Ghatole
    TI__Guru 69950 points

    Hello,
    I'd recommend to do a simple test first:
    1. "attach" JTAG to your board after your SPL is sent from UART,
    where "attach" is non-intrusive to the running board or NO HW RESET (don't run any GEL script...)
    2. break, and review disassembly, PC value... to see if the breaked code is in a/. bootrom OR b/. your SPL
    3. check your board etc.. if 2a/ or debug your SPL if 2b/.
    Best,
    -Hong