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.

CCS/PROCESSOR-SDK-DRA8X-TDA4X: How to debug the u-boot.img with CCS

Part Number: PROCESSOR-SDK-DRA8X-TDA4X

Tool/software: Code Composer Studio

Hi experts,

In PSDKLA documents https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/latest/exports/docs/linux/Foundational_Components_U-Boot.html#uboot-spl-debugging-tips

It mentions a method to debug the uboot spl. We would like to use the same way to debug the u-boot.img so that we could solve the problem with the u-boot drivers issue on our board.

However,  we found that we could not get the correct u-boot symbol after we connect the target "CortexA72_0_0". There seems to be an offset between the symbol  "board-support/u-boot_build/a53/u-boot" and the code. We would like to know what is the offset here. 

Thanks a lot!

Yuan J.

 

  • Hi Yuan,

    I will try this at my end and get back to you.

    Thanks,
    Keerthy

  • Hi Keerthy,

    Glad to hear the reply, thanks for your help!

  • Hi Yuan,

    In the u-boot prompt the 'bdinfo' command gives all the required information.

    => bdinfo
    arch_number = 0x0000000000000000
    boot_params = 0x0000000000000000
    DRAM bank = 0x0000000000000000
    -> start = 0x0000000080000000
    -> size = 0x0000000080000000
    DRAM bank = 0x0000000000000001
    -> start = 0x0000000880000000
    -> size = 0x0000000080000000
    baudrate = 115200 bps
    TLB addr = 0x00000000ffff0000
    relocaddr = 0x00000000ffee7000
    reloc off = 0x000000007f6e7000
    irq_sp = 0x00000000fdebbc70
    sp start = 0x00000000fdebbc70
    Early malloc usage: 2ca8 / 8000
    fdt_blob = 0x00000000fdebbc88


    So if i calculate the relocaddr from original address:

    Original start address is 0x80800000 + reloc off 0x7f6e7000
    relocated address = 0x80800000  + 0x7f6e7000 = 0xFFEE7000

    Please resolve this issue if you have no further questions.

    Best Regards,
    Keerthy

  • Hi Keerthy, 

    Thanks for your relay. Glad to have the offset. However, it does not take effect when I write the offset into the blank.

    In fact, I have tried every possible combination between  "code offset" and "data offset" with the 0x000000007f6e7000. 

    Could you please tell me how to fill the blank below so that the symbol could be found? Thanks for your help!

    Best Regards,

    Yuan

  • Hi Yuan,

    I am checking internally on this. I will get back to you once i have feedback.

    Best Regards,
    Keerthy

  • Hi Yuan,

    I believe you are still looking for a solution on this. I am still yet to find solution. Let me know
    if you had some luck with this.

    Best Regards,
    Keerthy

  • Hi Yuan,

    I am able to reproduce this issue and I haven't been able to find a solution yet. We have reached out to other internal teams to get some additional help. But this process could take longer and therefore I suggest you to look for alternate solutions and update this thread if you have been able to make progress. I will also keep you posted as soon as we have additional information.

    Best Regards,
    Keerthy

  • Hi Keerthy,

    Thanks for your reply. Although we still cannot debug the code with CCS,  we have added some log into the src code so that we could keep programming.

    Best Regards.

    Yuan

  • Hi Yuan,

    That is good to hear that you are able to proceed. I will keep you posted if i make progress on this thread.

    Best Regards,
    Keerthy