MCF8316AEVM: start-up sequence and subsequent NAK crash

Kamesh Durvasula

Part Number: MCF8316AEVM
Other Parts Discussed in Thread: MCF8316A

Hi Ti team,

We have finally got our motor to rotate using the SMT32 disco board (I2C). But when we try to stop it (set 0 I2C Duty), it starts sending NAK.

Below is the crash sequence for the above issue (its pretty much an output from the Logic Analyzer with our comments included)

Any help in resolving this issue is greatly appreciated.

Thanks,

Kamesh

Initialize registers.
write to 0x60 ack data: 0x50 0x04 0xBC 0x8C 0x6C 0x5C 0xF8 0x2D
write to 0x60 ack data: 0x50 0x04 0xBA 0x6A 0x4A 0xA4 0xFD 0xEF
write to 0x60 ack data: 0x50 0x07 0x34 0x00 0x00 0x00 0x00 0x28
write to 0x60 ack data: 0x50 0x07 0x36 0x00 0x00 0x00 0x00 0xEC
write to 0x60 ack data: 0x50 0x07 0x26 0x00 0x00 0x00 0x00 0xDE
write to 0x60 ack data: 0x50 0x07 0x24 0x00 0x00 0x00 0x00 0x1A
write to 0x60 ack data: 0x50 0x05 0x22 0x00 0x00 0x00 0x00 0x03
write to 0x60 ack data: 0x50 0x05 0x46 0x20 0x27 0x33 0x03 0x74
write to 0x60 ack data: 0x50 0x05 0x38 0x00 0x00 0x00 0x00 0xEC
write to 0x60 ack data: 0x50 0x06 0x72 0x5E 0x14 0x00 0x00 0xB3
write to 0x60 ack data: 0x50 0x06 0xDE 0x78 0xA5 0x33 0x04 0x37
write to 0x60 ack data: 0x50 0x04 0x44 0x00 0x00 0x01 0x00 0xD8
write to 0x60 ack data: 0x50 0x04 0x42 0x00 0x00 0x09 0x00 0x3B
write to 0x60 ack data: 0x50 0x04 0x40 0x00 0x00 0xF6 0xFF 0xDB
write to 0x60 ack data: 0x40 0x02 0x0E 0x00 0x00 0xFD
write to 0x60 ack data: 0x40 0x06 0x68 0x03 0x00 0x22
write to 0x60 ack data: 0x40 0x06 0x9A 0x0B 0x00 0x30
write to 0x60 ack data: 0x50 0x04 0x10 0x23 0x1D 0x00 0x00 0x7F
write to 0x60 ack data: 0x50 0x04 0xD8 0xCE 0x24 0xE7 0xFF 0xA3
write to 0x60 ack data: 0x50 0x04 0xD6 0xBA 0x90 0xF0 0x00 0x15
write to 0x60 ack data: 0x50 0x04 0xD4 0xDC 0xC8 0x14 0x00 0x92
write to 0x60 ack data: 0x50 0x04 0xD2 0x00 0x00 0x20 0x00 0x8D
write to 0x60 ack data: 0x50 0x04 0xE8 0x46 0x5C 0x1C 0x00 0x32
write to 0x60 ack data: 0x50 0x04 0xE6 0x47 0x74 0xF8 0xFF 0x80
write to 0x60 ack data: 0x50 0x04 0xE4 0x1E 0x36 0xF4 0xFF 0xB2
write to 0x60 ack data: 0x50 0x04 0xE2 0x9C 0xC3 0xDB 0xFF 0x25
write to 0x60 ack data: 0x50 0x05 0xF0 0x3E 0x74 0xE6 0xFF 0xC5
write to 0x60 ack data: 0x50 0x05 0xEE 0x00 0x00 0x00 0x00 0xCA
write to 0x60 ack data: 0x50 0x04 0x82 0xAE 0x61 0x20 0x00 0xE2
write to 0x60 ack data: 0x50 0x04 0x80 0x00 0x00 0x00 0x00 0x1D
write to 0x60 ack data: 0x50 0x04 0x7E 0xAE 0x62 0x02 0x00 0x44
write to 0x60 ack data: 0x40 0x04 0x68 0x03 0x00 0x0E
write to 0x60 ack data: 0x40 0x04 0x78 0x02 0x00 0xB9
write to 0x60 ack data: 0x50 0x04 0x7A 0x00 0x40 0x9E 0x01 0x7F
write to 0x60 ack data: 0x50 0x05 0xC8 0x00 0x00 0x00 0x00 0xE5
write to 0x60 ack data: 0x50 0x00 0xF2 0x00 0x00 0x00 0x00 0xE3
write to 0x60 ack data: 0x50 0x00 0xF0 0x45 0xF0 0x01 0x00 0x8B
write to 0x60 ack data: 0x50 0x00 0xEE 0x00 0x00 0x00 0x00 0x47
write to 0x60 ack data: 0x50 0x00 0xEC 0x00 0x00 0x00 0x80 0x0A
write to 0x60 ack data: 0x50 0x00 0xEA 0x00 0x00 0x00 0x00 0xC8
write to 0x60 ack data: 0x50 0x00 0xE8 0x00 0x00 0x00 0x0A 0x3A
write to 0x60 ack data: 0x50 0x00 0xE6 0x00 0x00 0x00 0x00 0x5E
write to 0x60 ack data: 0x50 0x00 0xE4 0x00 0x00 0x31 0x0D 0x55
write to 0x60 ack data: 0x50 0x00 0xE2 0x00 0x00 0x00 0x00 0xD1
write to 0x60 ack data: 0x50 0x00 0xE0 0x00 0x00 0x00 0x00 0x15
write to 0x60 ack data: 0x50 0x00 0xA2 0xA7 0x01 0x00 0x00 0xEF
write to 0x60 ack data: 0x50 0x00 0xA0 0xFD 0x10 0xB3 0x04 0xEE
write to 0x60 ack data: 0x50 0x00 0xAE 0x00 0x00 0x20 0x00 0x21
write to 0x60 ack data: 0x50 0x00 0xAC 0x00 0x01 0x40 0x1C 0x2F
write to 0x60 ack data: 0x50 0x00 0xAA 0x00 0x00 0x00 0x40 0xC7
write to 0x60 ack data: 0x50 0x00 0xAE 0x00 0x30 0x00 0x00 0x6E
write to 0x60 ack data: 0x50 0x00 0xA6 0x00 0x00 0x00 0x18 0xDE
write to 0x60 ack data: 0x50 0x00 0xA4 0x80 0xE4 0xD0 0x2D 0x7F
write to 0x60 ack data: 0x50 0x00 0x92 0x00 0x80 0xC0 0x64 0x92
write to 0x60 ack data: 0x50 0x00 0xA6 0x00 0x00 0x00 0x18 0xDE
write to 0x60 ack data: 0x50 0x00 0x90 0x0E 0x82 0xE8 0x17 0x1C
write to 0x60 ack data: 0x50 0x00 0x9E 0x00 0x00 0x00 0x00 0xD9
write to 0x60 ack data: 0x50 0x00 0x9C 0x00 0x00 0x00 0x00 0x1D
write to 0x60 ack data: 0x50 0x00 0x9A 0x00 0x00 0x00 0x00 0x56
write to 0x60 ack data: 0x50 0x00 0x98 0x00 0x00 0x00 0x00 0x92
write to 0x60 ack data: 0x50 0x00 0x96 0x00 0x00 0x00 0x00 0xC0
write to 0x60 ack data: 0x50 0x00 0x94 0x00 0x00 0x00 0x00 0x04
write to 0x60 ack data: 0x50 0x00 0x8E 0xC6 0x49 0x00 0x0A 0xBF
write to 0x60 ack data: 0x50 0x00 0x8C 0x00 0x00 0x80 0x1C 0xCD
write to 0x60 ack data: 0x50 0x00 0x8A 0x22 0xD9 0xAD 0x1A 0x24
write to 0x60 ack data: 0x50 0x00 0x88 0xB0 0x01 0x35 0x15 0x80
write to 0x60 ack data: 0x50 0x00 0x86 0x04 0x60 0x86 0x13 0xDE
write to 0x60 ack data: 0x50 0x00 0x84 0xD4 0x07 0x60 0x0B 0x71
write to 0x60 ack data: 0x50 0x00 0x82 0x64 0xF0 0x3A 0x28 0xBF
write to 0x60 ack data: 0x50 0x00 0x80 0x20 0x8C 0x63 0x44 0x97

Read pin_config.
write to 0x60 ack data: 0xD0 0x00 0xA4
read to 0x60 ack data: 0x80 0xE4 0xD0 0x2D 0x16

Set BRAKE_INPUT_ON in pin_config.
write to 0x60 ack data: 0x50 0x00 0xA4 0x82 0xE4 0xD0 0x2D 0x53

Zero out DIGITAL_SPEED_CTRL in algo_debug1
write to 0x60 ack data: 0x50 0x00 0xEC 0x00 0x00 0x00 0x80 0x0A

Set CLR_FLT and CLR_FLT_RETRY_COUNT in algo_debug1
write to 0x60 ack data: 0x50 0x00 0xEA 0x00 0x00 0x00 0xB0 0xD1

Reset CLR_FLT and CLR_FLT_RETRY_COUNT in algo_debug1
write to 0x60 ack data: 0x50 0x00 0xEA 0x00 0x00 0x00 0x80 0x41

Read pin_config.
write to 0x60 ack data: 0xD0 0x00 0xA4
read to 0x60 ack data: 0x82 0xE4 0xD0 0x2D 0x3A

Reset BRAKE_INPUT_ON in pin_config.
write to 0x60 ack data: 0x50 0x00 0xA4 0x84 0xE4 0xD0 0x2D 0x27

Set DIGITAL_SPEED_CTLR ~50&.
write to 0x60 ack data: 0x50 0x00 0xEC 0x00 0x00 0x00 0xD9 0x82

Start polling gate_drive_fault, controller_drive_fault and
algorithm_state looking either for a fault or
MOTOR_CLOSED_LOOP_ALIGNED
write to 0x60 ack data: 0xD0 0x00 0xE0
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xE9
write to 0x60 ack data: 0xD0 0x00 0xE2
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xBB
write to 0x60 ack data: 0xC0 0x02 0x0E
read to 0x60 ack data: 0x06 0x00
write to 0x60 ack data: 0xD0 0x00 0xE0
read to 0x60 ack data: 0x06 0x00 0x89 0x00 0x00
write to 0x60 ack data: 0xD0 0x00 0xE2
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xE9
write to 0x60 ack data: 0xC0 0x02 0x0E
read to 0x60 ack data: 0x00 0x00
write to 0x60 ack data: 0xD0 0x00 0xE0
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xBB
write to 0x60 ack data: 0xD0 0x00 0xE2
read to 0x60 ack data: 0x06 0x00 0x89 0x00 0x00
write to 0x60 ack data: 0xC0 0x02 0x0E
read to 0x60 ack data: 0x00 0x00
write to 0x60 ack data: 0xD0 0x00 0xE0
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xE9
write to 0x60 ack data: 0xD0 0x00 0xE2
read to 0x60 ack data: 0x00 0x00 0x00 0x00 0xBB

MOTOR_CLOSED_LOOP_ALIGNED found on this read.
write to 0x60 ack data: 0xC0 0x02 0x0E
read to 0x60 ack data: 0x09 0x00

Wait 1s then try to read algorithm_state (or any register).
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak
write to 0x60 nak

over 3 years ago

0 Aaron Barrera over 3 years ago

TI__Mastermind 26046 points

Hi Kamesh,

Eric will get you a reply tomorrow!

Thanks,
Aaron

0 Kamesh Durvasula over 3 years ago in reply to Aaron Barrera

Prodigy 155 points

Hi Aaron, Eric,

Any updates on the issue we are facing?

Thanks,

Kamesh

0 Adam Sidelsky over 3 years ago in reply to Kamesh Durvasula

TI__Guru 65220 points

Kamesh,

Eric is still working on this and will have an update for you tomorrow Dallas time.

Regards,

-Adam

0 Eric Chen over 3 years ago in reply to Kamesh Durvasula

TI__Genius 9220 points

Hi Kamesh,

As discussed on the call, to show the timing between the I2C commands, could you please attach a .logicdata file with the I2C data capture, beginning from setting the 50% speed cmd to when the NAKs start occurring.

Thanks,
Eric C.

0 Kamesh Durvasula over 3 years ago in reply to Eric Chen

Prodigy 155 points

Hi Eric,

I am unable to send the Logic Analyzer output via this messaging system. I will email you instead.

Thanks,

Kamesh

0 Aaron Barrera over 3 years ago in reply to Kamesh Durvasula

TI__Mastermind 26046 points

Hi Kamesh,

Have you sent the email yet?

Thanks,
Aaron

0 Kamesh Durvasula over 3 years ago in reply to Aaron Barrera

Prodigy 155 points

Hi Aaron,

I forwarded the email to Eric and Vishnu.

Thanks,

Kamesh

0 Adam Sidelsky over 3 years ago in reply to Kamesh Durvasula

TI__Guru 65220 points

Kamesh,

Aaron is out today but Vishnu and Eric should follow up.

Regards,

-Adam

0 Kamesh Durvasula over 3 years ago in reply to Adam Sidelsky

Prodigy 155 points

Hello Ti Team,

Any update on this issue?

Thanks,

Kamesh

0 Eric Chen over 3 years ago in reply to Kamesh Durvasula

TI__Genius 9220 points

Hi Kamesh,

I received the logic analyzer data, and I'm trying to recreate the failure on my board.

Could you please also try using 65kHz as PWM Frequency?

Thanks,
Eric C.

0 Vishnu Balaraj over 3 years ago in reply to Eric Chen

TI__Mastermind 24415 points

Kamesh,

Did you get a chance to check Eric's recommendation in the previous post? Also, the I2C clock on the top has ~20% duty cycle. It certainly doesn’t look like the I2C clock generated by the EVM’s MSP430. I2C clock duty cycle is typically at 50%.

Regards,

Vishnu

0 Kamesh Durvasula over 3 years ago in reply to Vishnu Balaraj

Prodigy 155 points

correct.Hi Vishnu,

We do not have any issues with the NAK issue anymore using the EVAL board.

We have issues when using a custom board that we designed with the MCF8316A on it.

I wanted to make sure that the schematic we have is correct.

0 Vishnu Balaraj over 3 years ago in reply to Kamesh Durvasula

TI__Mastermind 24415 points

Kamesh,

Thanks for sharing the schematic. I see that the SW_BK and GND_BK pins are floating. Can you connect R_BK and C_BK as recommended in the datasheet? Buck voltage is used in the internal circuitry so we recommend to populate these external components.

What is the voltage level of MOT3_DVDD? I see that this voltage source is shared by several other loads in your schematic. Can you ensure this pin is not overloaded?

Also, did you check our below recommendations that were suggested earlier?

Eric Chen said:
Could you please also try using 65kHz as PWM Frequency?

Vishnu Balaraj said:
Also, the I2C clock on the top has ~20% duty cycle. It certainly doesn’t look like the I2C clock generated by the EVM’s MSP430. I2C clock duty cycle is typically at 50%.

Regards,

Vishnu

0 Kamesh Durvasula over 3 years ago in reply to Vishnu Balaraj

Prodigy 155 points

Hi Vishnu,

Thanks for your suggestion. We figured the SW_BK and GND_BK pins when comparing the Eval kit and our schematic. Fixed it and now we have no more NACKs. (this worked at 60KHz). I will check on the duty signal of the clock line and confirm.

Now, that we have comm working... we are still UNABLE to get the motor rotating. We connected the GUi (via the MSP430 micro) to the motor controller on our custom board. The GUI is able to talk to the motor controller. We are able to set the I2C duty for speed... the voltage reads accurately. But the motor does not rotate and there are no faults.

Any reason why this is happening. The only thing that we do not have when compared to the Eval kit are that the NC pins not connected to GND. Does this make any difference?

Thanks

Kamesh

0 Kamesh Durvasula over 3 years ago in reply to Kamesh Durvasula

Prodigy 155 points

Is it possible for us to have a call tomorrow (9 Nov 2021). Please let me know. 4PM CST will be convenient. Please let us know.

Thanks,

Kamesh

0 Vishnu Balaraj over 3 years ago in reply to Kamesh Durvasula

TI__Mastermind 24415 points

Kamesh,

Good to know that the I2C communication is restored. What is the status of DRVOFF pin? When DRVOFF pin is driven active 'High', MCF8316A stops driving the motor by turning OFF all MOSFETs.

Regards,

Vishnu.

0 Kamesh Durvasula over 3 years ago in reply to Vishnu Balaraj

Prodigy 155 points

Hi Vishnu,

The DRV_OFF pin is set o GND at startup.

We are still unable to get the motor rotating.

Regards,

Kamesh

0 Vishnu Balaraj over 3 years ago in reply to Kamesh Durvasula

TI__Mastermind 24415 points

Kamesh,

Let's take this offline.

Note for other E2E customers following this thread: Findings will be posted here after the discussion.

Regards,

Vishnu

Motor drivers

Motor drivers forum

MCF8316AEVM: start-up sequence and subsequent NAK crash