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.

c6455 bootloader problems



i have a similar problem like here

http://e2e.ti.com/support/embedded/bios/f/355/t/39936.aspx

i've coded a secondary bootloader which loads program from flash to L2 and branches to c_int00

burned the program with bootloader to flash.

the program runs very well if I start with  CCS3.3(without gel!). it runs if i debug but it doesn't run on reset without connecting with CCS

it's a DSP/BIOS program

the bootloader runs well copys all sections from rom to L2(but doesnt init EMIFA or DDR, i have tried it but it didn't have any effect)

i could optain that the programm falls in UTL_halt after running the USER Init function

maybe be non-maskable interrupt(NMI) is pending ( bit 1 of IER is set )

there is no gel,but does CCS do something other on startup???

what is the diffrence between running with ccs in debug and without???

  • Danny,

    When you say there is no GEL, do you mean that you do not execute anything from the GEL file or the workspace has no GEL file associated with it?

    What boot mode do you have the device pins set for?

    If there is no GEL, CCS can be configured so it does not do anything that you do not tell it to do. When you connect, it will stop the processor in some cases. Look at your options to see if you have anything setup to happen automatically. I do not have CCS 3.3 so I cannot tell you the exact steps, but somewhere in the menus are some option settings for the debugger, such as to automatically GoMain().

    In the thread you referenced above, there is a mention of a helpful Wiki page name Debugging from Flash. Take a look at that article for some ideas on how to debug your boot problems and let us know what ideas work well for you or what new information you find out.

    Regards,
    RandyP

  • no GEL means there is no GEL file in workspace.

    the device was set in EMIFA 8 Bit rom boot

    I,ve found the problem:

    It was the EMIF wich wasn't right initialized (or to late).

    Solvation was to setup the EMIF right befor the bootloader copies section into internal cache.

    I don't know why the program runs while dubuging it with CCS3.3(without any gel))