AM13E23019: Unexpected Interrupt and state in AM13E230x Motor Control Solution

Phuong Nguyen

Part Number: AM13E23019

I'm currently running the 3-Shunt Hall Sensored FOC motor solution from the AM13E23X SDK with a DRV8323RS driver and BLY172S-24V-4000 motor. Here are the edits I have made to the code to run the motor:

Motor_params.h
1. Added the macro block for BLY172S nameplate parameters
2. Updated the MOTOR_PH_Ls_d_H and MOTOR_PH_Ls_q_H aliases
Motor_params.c
1. Added const Motor_ParamsType for the BLY172S with the nameplate parameters and copied over the MOTOR_TEKNIC values for all other parameters.
2. Updated motorParams_M1 pointer to point to the new const

When I initially startup the debugger through CCS, I always enter the default_handler for unexpected interrupts before motorVars_M1 is set to the parameters I have set. It is not until I restart the debugger where these variables are populated with values. I have gotten the motor to spin with the same code setup, but it will not spin in every iteration. When the motor doesn't spin and I pass the default_handler, it will never exit calibration (in main.c) for some reason.

Screenshot 2026-09-18 171055.png

I have not changed files outside the ones I have listed. I was planning to use TiTune or instaspin to get more accurate parameter identification but I have not been able to get the motor to spin with this. I'm on sdk 26.01.00.03 but is there anything I'm missing in my set up that is triggering the interrupt or keeping me in an indefinite state?

10 days ago

0 Venkata Pavan Mahankali 8 days ago

TI__Intellectual 1300 points

Hi ,

Can you try system reset and restart the CPU before giving a debug Run command. Ideally complete power recycling the MCU should clear all the stale CPU & peripheral states before starting a new debug session, other wise System, CPU Reset and restart should help.

0 Phuong Nguyen 7 days ago in reply to Venkata Pavan Mahankali

TI__Prodigy 40 points

Hi,

I have done a system, cpu reset and restart but there I'm still running into the same problem. I haven't gotten the motor to spin anymore, even before I performed the reset. Could there be something wrong in my nameplate data causing this issue or if there is another file I needed to adjust before spinning the motor? I was planning on spinning titune to get more accurate measurements:

0 Phuong Nguyen 7 days ago in reply to Phuong Nguyen

TI__Prodigy 40 points

I am also running the sensorless solution, not the sensored solution, i accidentally wrote that in my initial post.

0 Venkata Pavan Mahankali 7 days ago in reply to Phuong Nguyen

TI__Intellectual 1300 points

Name plate shouldn't create an issue running into default handler on alternate runs. Can you try power cycling the board and MCU on every new debug session?

0 Simon Björklund 5 days ago

Prodigy 30 points

I had the same issue and the problem was that the ISR priority queue on the FOC loop changed from max priority to default which caused the interupt to never trigger. I could see this by measuring the ISR output pin.

Arm-based microcontrollers

Arm-based microcontrollers forum

AM13E23019: Unexpected Interrupt and state in AM13E230x Motor Control Solution