• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 62 subscribers
  • Views 256 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

[FAQ] TMS570LC4357: Examples and Demos available for Hercules Controllers (E.g. TMS570x, RM57x and RM46x etc)

BQ79600EVM: Fault generated on SPI interface

vikas chaudhary
Prodigy 150 points
Part Number: BQ79600EVM
Other Parts Discussed in Thread: BQ79656EVM-021, BQ79616-Q1, BQ79616

Hi, 

I'm using LAUNCHXL2-TMS570012 launch pad as HOST and interface BQ79600EVM-030 (Bridge evaluation board) on SPI protocol,

BQ79656EVM-021 evaluation board is connected with  BQ79600EVM-030 on Daisy Chain protocol

Software - CCS

Firmware - BQ79600_SPI_Sample_Code

Problem - As per firmware initial point HOST send wake up tone to BQ79600, BQ79600 waked up but also generate the fault(Green and RED Led both are on)

In the next line of code its clear the fault but Red Led isn't OFF and its not reading any value from BQ79656 

My question is what wrong I did, It should be work?

Infact its working if I use UART protocol between Launch Pad  and BQ79600 instead of SPI

I change the Jumper position as well for using UART or SPI as per suggestion.

Kindly find attached pic of Jumpers position for SPI interface

    

  • 0
    TI__Intellectual 1845 points

    Hello,

    Can you attach captures of your SPI lines? Are you making sure to monitor the SPI_READY signal?

  • 0 in reply to Chase Fagen
    Prodigy 150 points

    Yes, SPI_READY is high after wake up tone to BQ79600

    --------------- REFERENCE Code--------------------------------

    //INITIALIZE 600
    //two wakes in case the MCU had nCS and MOSI = 0 at start (which would put the device in shutdown) or in case the device was previously put in shutdown through a shutdown ping
    SpiWake79600(); //send wake ping to bridge device ------------>Once wakeup to BQ79600 GREEN and RED led both are on (RED mean fault)
    delayus(3500); //wait tSU(WAKE_SHUT), at least 3.5ms
    SpiWake79600(); //send wake ping to bridge device
    delayus(3500); //tSU(WAKE_SHUT), at least 3.5ms

    //INITIALIZE BQ79616-Q1 STACK
    SpiWriteReg(0, CONTROL1, 0x20, 1, FRMWRT_SGL_W); //send wake tone to stack devices ------------------>BQ79616 led should be ON but its not
    delayms(11.6*TOTALBOARDS); //wake tone duration is ~1.6ms per board + 10ms per board for each device to wake up from shutdown = 11.6ms per 616 board.
    //AUTO-ADDRESS
    SpiAutoAddress(); //auto address sequence

    //RESET ANY COMM FAULT CONDITIONS FROM STARTUP
    SpiWriteReg(0, FAULT_RST1, 0xFF, 1, FRMWRT_STK_W); //Reset faults on stacked devices
    SpiWriteReg(0, FAULT_RST2, 0xFF, 1, FRMWRT_STK_W); //Reset faults on stacked devices
    SpiWriteReg(0, Bridge_FAULT_RST, 0x22, 1, FRMWRT_SGL_W); //Reset FAULT_COMM and FAULT_SYS on bridge device-------?RED led should be off                                                                                                                                                                                               here but its not OFF that the issue

    //ENABLE BQ79616-Q1 MAIN ADC
    SpiWriteReg(0, ACTIVE_CELL, 0x0A, 1, FRMWRT_STK_W); //set all cells to active
    SpiWriteReg(0, ADC_CTRL1, 0x06, 1, FRMWRT_STK_W); //continuous run and MAIN_GO
    delayus(5*TOTALBOARDS + 192); //5us reclocking per board and 192us for round robin to complete

    --------------------------------------------------------------------------------

    MOSI - blue

    MISO- Green

    SCK - Yellow

    CS - Voilet

    Stack wake up command  in Above image