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.

Choice of ABI and Ethernet boot image creation

Hi all,

I have the following situation, where the same program works and alternatively doesn't.

When I download the .out file through the debugger the software runs as desired.

When I create an Ethernet download image, I download it, then in the debugger set the PC to the _c_int00 of the program and run it, the program gets lost running functions that look like TI_zero_init and TI_decompress_rle.

Does the choice of abi change the way the ethernet image is generated? Which step should be affected: hex6x, mergebtbl, bcovert64x or bootpacket?

Do you have any suggestions?

Regards,

e

  • How are you loading the ethernet boot image? Are you setting the device in Ethernet boot?

    Thanks,

    Arun.

  • Yes, I set the device in Ethernet boot. The code I am talking about goes to the memory of core2 with pcsendpkt.exe. Core0 executes an infinite while loop and does not start core2. I start core2 manually, by connecting the debugger and setting Load symbols only.

    If I redownload core2 with Load program and symbols then this problem does not appear.

    I looked again at the output of the hex6x utility and I get

    warning: duplicate section name
       ...(Extern_ctrl_sect) (ignored)
    warning: duplicate section name
       ...(Internal_table_sect) (ignored)
    warning: duplicate section name
       ...(.fardata.1) (ignored)

    In the map file I only see Internal_table_sect twice, both times with length not equal 0.

    Regards,

    eri

  • Can I manipulate the .out file in such a way as to rename one of the duplicate sections?

    I cannot rebuild the application. We only purchased the executable.

    Regards,

    eri