Quantcast
Channel: Motor drivers forum - Recent Threads
Viewing all articles
Browse latest Browse all 22040

MCF8315A: MCF8315A

$
0
0
Part Number: MCF8315A

Tool/software:

Hello,
I'm working on a project with four MCF8315A Driver chips mounted on the same PCB and controlled by a microcontroller through a common I2C bus.
I had no problems establishing communication with the Drivers, changing their I2C_SLAVE_ADDR, SPEED_MODE and BUS_VOLT settings and saving them to the EEPROM.
I also read all the other Driver Registers - their contents correspond to the defaults values taken from the TI documentation.

Then I tried to start the MPET procedure on one of the MCF8315A Drivers.
According to the Documentation, this can be done:
  1) either through the MPET_CMD bit in ALGO_DEBUG2 Register, provided that MPET_R = 1b or MPET_L = 1b
  2) or by applying a non-zero Speed Reference through the OVERRIDE and DIGITAL_SPEED_CTRL fields of ALGO_DEBUG1 Register,
     provided that in CLOSED_LOOP2 Register MOTOR_RES = 0 or MOTOR_IND = 0, which are the default values of these parameters

I tried both ways, but there was neither visual/acoustic reaction, nor any change in the Driver Registers, except that the MPET_CMD bit went back from '1' to '0' swiftly in the first case.

I have no idea how to proceed further as I can't see any reason for such behavior.
The only probable cause I can imagine is the SYS_INIT_DONE bit in the ALGO_STATUS Register which stays '0', which according to the Documentation "indicates firmware is still copying EEPROM to shadow memory".
There are no more explanations for this bit in the Documentation, and of course, "copying EEPROM to shadow memory" is complete as I can read the entire shadow memory.

Please, help me figure out what could be the cause of this problem and how I could solve it.
Thanks in advance!


Viewing all articles
Browse latest Browse all 22040

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>