Running ADC soc code from Flash : DSP trapped in Illegal ISR .

Shantanu Nakhate76513

Intellectual 465 points

Other Parts Discussed in Thread: TMS320F28035, TMS320F2810

Hello,

I modified the sample adc SOC code for tms320f28035 for running it from flash. The code gets compiled properly.

When I run the code , The DSP gets trapped in Illegal ISR loop and program stops.

How should I solve this issue.

Best Regards,

Shantanu.

over 14 years ago

0 Manoj Santha Mohan over 14 years ago

TI__Guru 55700 points

Shantanu,

Hope you had made the following changes to the project:

When running from flash you can initialize flash by executing from flash. So, you need to add these two statements MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart); InitFlash(); after InitPieVectTable();
Add DSP2803x_MemCopy.c file to the project.

Define extern variables above main() function.

                                    extern Uint16 RamfuncsLoadStart;
                                    extern Uint16 RamfuncsLoadEnd;
                                    extern Uint16 RamfuncsRunStart;

Replace 28035_RAM_lnk.cmd with F28035.cmd
Compile the code.
Configure your GPIO's to boot to flash.

The following things could cause Illegal_ISR interrupt:

Device not properly configured to boot to flash mode.
The flash initialization routine should be executed from RAM. Did you check whether Initflash() gets executed out of RAM?
Stack overflow issues

Also, it is relatively easy to find out the source of illegal_ISR routine by checking the contents of the stack when illgal_ISR is entered. Please find the address and the data which triggers illegal ISR.

Regards,

Manoj

0 Shantanu Nakhate76513 over 14 years ago in reply to Manoj Santha Mohan

Intellectual 465 points

Hi,

I did the step run.

The program goes to ilegal ISR loop when it runs

(*Device_cal);

Please let me know how to solve the problem.

Regards,

Shantanu.

0 Manoj Santha Mohan over 14 years ago in reply to Shantanu Nakhate76513

TI__Guru 55700 points

Shantanu,

Try single stepping in "mixed mode" (which has both assembly and C instructions). When (*Device_cal) is executed the PC should go to 0x3D7C80. Did you see this happen?

Can you share with me the contents of 0x3D7C80 – 0x3D7CBF in data memory?

Regards,

Manoj