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.

TMS320F28P650DK: ADC setup will cause "Intterrupt_illegalOperationHander."

Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: LAUNCHXL-F28P65X, SYSCONFIG

Hi, Experts

    I encountered some issues with my project running on the LAUNCHXL-F28P65X. my project base on demo project"ipc_ex4_msgqueue_sysconfig_multi" and plan to add ADC Module, PWM Module and ADC ISR.

issue 1:  the code " DEVICE_DELAY_US(1000);" in setup ADC function will cause project to enter "Intterrupt_illegalOperationHander" after running.

issue 2: after I delete code" DEVICE_DELAY_US(1000);" the function ADC_ISR will cause "Intterrupt_illegalOperationHander." after CPU02 start to run.

  • Hello Steven,

    my project base on demo project"ipc_ex4_msgqueue_sysconfig_multi" and plan to add ADC Module, PWM Module and ADC ISR.

    Since you're starting with an example project, it looks like you should have all the right paths and libraries included; are there any warnings you get when compiling the project? Are you able to step through your code and get into the delay function at all? If not, please provide a screenshot of the Disassembly view so I can see what the compiler created.

    issue 2: after I delete code" DEVICE_DELAY_US(1000);" the function ADC_ISR will cause "Intterrupt_illegalOperationHander." after CPU02 start to run.

    Are you able to isolate the location where the illegal ISR gets jumped to? Is it a certain point in your code? If you don't know for certain, you can always use the RPC (return program counter) register to see where it jumped from and keep backtracking from there using breakpoints.

  • Hi, Amir

    the screenshot of disassembly view is below when "Intterrupt_illegalOperationHander" caused by "DEVICE_DELAY_US(1000)";:

  • And the screenshot of warning after compiling the project is below:

  • Hi, Amir

     I have found the root cause, as the setting of CPU01 ".TI.ramfunc" running Ram space is conflicting with CLA.