• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 165 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM3359: U-boot debug prints issue

Chinmay Choudhary
Prodigy 190 points
Part Number: AM3359

Hi All,

we are using AM3359 ICEv2, also using are using SDK v 04_03_00_05 for generating U-boot & Kernel(This SDK has u-boot v 17).While booting up with the SDK, we are able to see kernel prints but we are not able to stop the U-boot or see any u-boot prints.

However, our customer requirement is to use the u-boot 17 version, so we are sticking with this, also i have checked for the baudrate setting but not able to see any prints on the serial console.
Please let me know what can be done to resolve this.

Awaiting reply,

Regards,
Chinmay Choudhary

  • 0
    TI__Guru 57986 points

    Chinmay,

    so U-Boot works but there are no prints? Can you confirm that you use the ICEv2 platform and the SDK as-is (with no customizations)?

    There could be a couple of things wrong...

    • Printing to the "wrong" UART?
    • Missing/incorrect pinmux?

    To debug this try to use the current SDK to hopefully witness the UART working. Then use this as a know-good starting point to compare against your older U-Boot (boardfiles, defconfig, dts). You can also trap program execution in U-Boot with an endless loop (for example in board_r.c) and then use JTAG to verify SoC configuration (to double-check pinmux and that the correct UART is being accessed).

    Regards, Andreas