• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 102 subscribers
  • Views 160 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.

OMAP-L138: Custom ubl/uboot debug - CCS

Muthu Kumar
Prodigy 140 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138,

Hi,

I am having a customized OMAPL138 board with customized UBL and u-boot code.
The customized UBL binary is been built out from the OMAP-L138_FlashAndBootUtils on ubuntu. Recently made some changes in UBL code, so I am planning to debug the UBL code using CCS utility to verify the functionality.

Below are the queries...

1. Now need SOP for debugging the customized UBL on CCS on the OMAPL138 board.

2. Installed CCS Version: 10.3.0.00007 on windows 10. I want to confirm that this version support OMAP L138, and moreover the UBL binary has been compiled on the Linux platform, but the CCS installed in the windows 10. Want to ensure that, this not create any dependency issue while debugging. (Read somewhere, this created dependency issue)

Thanks in advance...

MUTHUKUMAR V

  • 0
    TI__Guru 54475 points

    Hi Muthu,
    Some reference on HW setup on OMAP-L138 with CCS.
    software-dl.ti.com/.../index_how_to_guides.html
    Best,
    -Hong

  • 0
    TI__Guru** 114410 points

    Hi Muthukumar,

    The UBL source in OMAPL138 Flash and Boot utilities is legacy/mature code and not recommended to be used. We have OMAPL138 supported in the latest SDK with 4.17 kernel. and uboot. Is there any reason that you are choosing to use the legacy code.

    If you still wish to debug the UBL source, you can load the .out that the build generates on the ARM9 on OMAPL138 using CCS but note that when booting from flash you need this in AIS format so it is better if you flash the UBL to flash and setup a spinlock in the code so you can test ubl booting into onchip memory using ROM bootloader and then step through the UBL code to debug it.

    There are no issues using binaries built in Linux host on windows machines for debugging. However for debugging you will need the source to be on the Windows machine as well.

    Regards,

    Rahul