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.

CCS/TMS320F28388D: CM core runs to defaultISR

Part Number: TMS320F28388D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi all,

when I porting SYS/BIOS to CM core, which is ever based on C2000ware libraries, it runs to defaultISR, waiting for ever:

At the same time, I exported the Register file from CCS, which is showed below:

2134.Desktop.rar

Please help me resolve it.

Thanks!

QL

  • Hi QL,

    defaultISR is not a function plugged in by SYS/BIOS. When moving to SYS/BIOS, you must use the Hwi to register ISRs. 

    Note: you can use CCS->Tools->ROV Classic->Hwi to look at the status of the ISRs.

    Todd

  • Hi Todd,

    exactly as you said, I registered IRQ11(i.e. DCAN1INT0) as a Hwi in BIOS on CM core, please refer the following picture for more information.

    Thanks!

    QL

  • Hi Todd,

    I tried again and remove function calls from interrupt.c which is a module in C2000ware project. Now the Hwis are like this:

    Am I right now? Anything else should I think again?

    QL

  • Hi Todd,

    I have another question:

    As mentioned above, there are NMI interrupts, User  interrupts, and several systematic interrupts(like HardFault), is it necessay to configure all of them

    in my BIOS project? In other words, do them make differences if I don't configure them at all?

    If I need to make any configuration of NMI or HardFault based on Hwi thread, how to do with them in Hwi modules?

    Thanks a lot!

    QL

  • user6114104 said:

    As mentioned above, there are NMI interrupts, User  interrupts, and several systematic interrupts(like HardFault), is it necessay to configure all of them in my BIOS project? In other words, do them make differences if I don't configure them at all?

    Yes, if you anticipate these interrupts activating you should configure them with your handler function. Otherwise, as shown in the above table, if they occur they will by default trigger the Hwi exception handler.

    user6114104 said:

    If I need to make any configuration of NMI or HardFault based on Hwi thread, how to do with them in Hwi modules?

    Please see this thread about using Hwi_plug(): e2e.ti.com/.../3345435