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.

UBL symbolic debug with ccsv5.2 dm36x

Hello.

I am trying to use symbolic debugging with CCS 5.2 on a UBL_NAND project. I was able to do it once but I have been unable to reproduce. I suspect this may be a procedural issue setting up the environment but I am not sure. I am a Newbie so please bear with me.

I am using:

CCS v 5.2.0.00069

TI_PSP Davinci PSP SDK 03.21.00.04

TI XDS100V2 USB Emulator

Spectrum Digital DM36x EVM Rev G

I can build the ubl_DM36x_NAND.bin output file and load it into the Flash with the sfh_DM36x.exe utility using the UART boot mode. When I cycle the board I get the banner header from UBL from the UART. I want to be able to place breakpoints in the device.c file so I can verify settings, etc.. In the target configuration file, under the program tab, I have selected "Load symbols only".

When I try to launch the target configuration,  I get a dialog indicating the target endianness is incorrect for the output file. Here is a screen shot showing the dialog. In the build settings, everything is set to little endian.  I figure i have mucked up a setting somewhere but it is eluding me.

Can anyone clarify what needs to be done to fix this?

Thanks,

Brian

  • Brian,

    The screenshot didn't go through. However, it is very strange the endianess is being confused by the simple "load symbols only" operation.

    Just to confirm: when you connect, can you check at the bottom of the screen if the processor is set to LE? Check the screen below (it shows CortexA but it is similar for ARM9):

    Also, can you check if the target configuration is set to the proper endianess? Check:

    I'll try to think about other details that may be affecting the operation of your setup and will reply to this thread, ok? In the meantime please check the details above.

    Hope this helps,

    Rafael 

     

  • Rafael,

    Thanks for responding to my post.  The endianess problem is a strange one. I decided to install Code Composer Studio V5.2 on a different machine running Windows 7 and worked through the installation of the TI_PSP code again. I was running on a Windows XP machine.

    Fortunately, I am now able to symbollically debug the UBL code for the DM368 on the Spectrum Digital DM36x EVM board. 

    I figure that there is probably a bug when the General Settings are changed to a Generic ARM processor affecting the endianess of the target file. 

    Cheers,

    Brian

  • Brian,

    Very strange indeed. Thank you for reporting your findings and I will keep an eye on possible issues from other users.

    Cheers,

    Rafael