• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 577 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.

CCS V: 5.1 - Uboot debugging halts

venkat goli
Prodigy 130 points

Hi there,

I'm trying to debug Uboot on panda omap-4430 board. After loading the uboot , it runs through few functions then flashes following error message and terminates execution. Please find the attached screen shot for more details.

Kindly let me know what would have been going wrong?

Thanks & Regards,

Venkat

  • 0
    TI__Guru**** 482571 points

    Hello Venkat,

    The debugger cannot find the source files for source line debugging. In this case it cannot find "interrupts.c". If you have the Uboot source files, you can use the "Locate File..." button and browse to the location of it. The debugger than should be able to find the rest of the source files once it knows the location of the first,

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    Hello Ki,

    Thanks for your reply.

    I'm able to put the breakpoint in interrupt.c file and execute interrupt_init() function. This can be seen in the previous post screen shot attachment. When I tried to "step in" and execute, it does not execute entire function. It terminates execution as soon as the uboot load the timer value in register.

    Please let me know if you need any info.

    Thanks & Regards,

    Venkat

  • 0 in reply to venkat goli
    TI__Guru**** 482571 points

    I'm not sure what build of Uboot you are trying to debug but if you are trying to do source level debugging, make sure you have built Uboot with minimal optimization and full debug symbols.

  • 0 in reply to Ki
    Prodigy 130 points

    Hello Ki,

    We have compiled with -O0 optimization and -g (debug symbols) options.  Uboot is getting executed till interrupt_init() function. In the interrupt_init() we are accessing GPTIMER2 - module registers, as soon as we access these registers ccs is terminating the execution.

    When I tried commenting the code in interrupt_init(), it passed interrupt_init() file and gave the same kind of issue in serial_init() which is accessing UART3 - L4 interconnect.. I'm thinking it is because of accessing certain registers.

    The same uboot is working without any issues on the board but when debugging with CCS, I'm seeing this issue.

    Could you please let me know what could be the issue?

    Thanks & Regards,
    Venkat