Software entering undefined_handler after configuring ADC

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Software entering undefined_handler after configuring ADC

1,127件の閲覧回数
Abdulrahman
Contributor I

Hello All,

 

I am currently configuring the ADC module in the target "S32G99" and interrupts are enabled upon end of conversion.

When flashing in the ram everything runs smoothly but when flashing in the NOR Flash, the startup code runs and after the instruction bl startup_go_to_user_mode the software enters undefined_handler. 

This only happens upon configuring the ADC, keep in mind that the project is not running on the plugins provided by nxp " Platform, Base, .. etc " but rather a full AUTOSAR deployment where the OS is running and the ISR is configured with their respective exception number ( 86 / 87 ) and a priority of 64

 

Any Idea on why is this occurring ?

0 件の賞賛
返信
1 返信

1,110件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

We understand that you are not using any NXP RTD packages, is this correct? Are you using any NXP development board? Or is this a custom board?

For what we can provide, reaching an undefined_handler scenario can range from the IRQ handler not being defined correctly (or not defined at all) to the IRQ not being installed correctly or in the correct order. Following the example available under the RTD, the following sequence is followed:

DanielAguirre_0-1698341831297.png

Given that, if true, you are not using any NXP packages, we cannot confirm if these are the possible problems that you have. We do apologize.

We can also recommend contacting your local NXP FAE/DFAE, they could possibly provide more insight on your current situation.

Please, let us know.

0 件の賞賛
返信