What exactly happens on "Connect", "Run" and "Halt" (in addition to the GEL commands)?

That's fantastic Raphael:

I think that might be the issue I'm having.

Does this isr run by default or did you have to add it?

You mentioned it being in your linker setup.

Thanks,

Sam

Hi,

this ISR doesn't run by default, you have to tell the linker that you want to use it as entry point instead of the default, _c_int00. You can either do that somewhere in the linker options (right-click on your CCS4 project, Preferences, C5500 Linker, Symbol Management: -entry_point, -e = reset_ISR) or write the -e command in your CMD file. I did the latter, please find the .CMD code below  (which is from a CSL example). Make sure that your new reset function, e.g. reset_ISR, is defined in your vectors.asm and jumps to the standard entry point _c_int00 after execution, see the code I posted before.

-stack    0x2000                /* PRIMARY STACK SIZE    */
-sysstack 0x1000                /* SECONDARY STACK SIZE  */
-heap     0x2000                /* HEAP AREA SIZE        */ 

/* Set entry point to Reset vector                                  */
/* - Allows Reset ISR to force IVPD/IVPH to point to vector table.  */
-e reset_isr

MEMORY
{
  PAGE 0:
    VEC(RWX)      : origin = 0000100h length = 000100h  /* was: origin = 0000100h length = 000100h */
    DATA(RWX)     : origin = 0000200h length = 007E00h     /* was: origin = 0000200h length = 007E00h */
    PROG(RX)      : origin = 0008000h length = 010000h     
}

SECTIONS
{
  vectors (NOLOAD)                    /* not sure if this is necessary)        */   
  .vector    : > VEC ALIGN = 256      /* was: .intvec    : > VEC ALIGN = 256 */
  .text      : > PROG
  .data      : > DATA 
  .cinit     : > PROG
  .switch    : > PROG
  .stack     : > DATA
  .sysstack  : > DATA
  .bss       : > DATA
  .sysmem    : > DATA
  .const     : > PROG
  .cio         : > DATA
 
}

The IDLE commant could theoretically also be executed from somewhere in your C code, but I don't know the syntax for calling the assembler commands, therefore I chose the reset ISR option.

Hope this helps,

Raphael

Hi Raphael,

I made a quick and dirty test of your code example above, only that I put it as the first lines in main(). It did not work. Does it have to be before the call to c_int00? I have not investigated the vector area and reset vector configuration but of course I would probably find it with some research.

Please advice, I am a little bit tired on the trial-and-error to get the demo code working.

Best regards,

Lennart

Hi,

what do you mean with "It didn't work", did it compile but there was no visible effect? How did you call the assembler code from your c-code in main()?

I suggest you try to execute the lines from exactly the same location (the vectors.asm file), otherwise there might always be other things that go wrong.

Good luck,

Raphael

Raphael,

I am very grateful for your post. I struggle for a while, but you solution corrected the issue I was having with the FFT HWA. I did the routine in C like:

      IDLE_ICR = 0x000E;
      asm(" nop_16");
      asm(" nop_16");
      asm(" nop_16");
      asm(" nop_16");
      asm(" nop_16");
      asm(" nop_16");
      asm(" idle");

I guess there's probably a more concise way to to the asm code, but I am very relieved that this issue is finally resolved.

Thank you all contributors to this post, especially Raphael and Jonathan!!! 

inserting Jonathan's C code snippet at the starting of my system and PLL register initialization resolved an issue that was holding me up for a few days now. My SD card write program that was using DMA to write to SD card was working while I ran in Debug mode through CCS but not after I loaded the bootimag to a SPI flash. I had overlooked the IdleConfig Register in my initializations and after reading this post saw the 'fine print' on ICR in the C5535 technical reference manual.

Best

Milind

PS: I really wish TI had made their documentation more easy to read and search for information rather than fishing for information through over 500 pages of different documents and forms to resolve any single issue.