• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 621 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MCT8316A: debug issue

Cherry Zhou
Mastermind 22235 points
Part Number: MCT8316A
Other Parts Discussed in Thread: MSP430FR2355, , MCF8316AEVM, MCX8316AEVM, MCF8316A

Hi team,

Here's an issue from the customer may need your help:

As per the MCT8316AEVM User's guide, the firmware code project for the monolithic device communicating with the upper computer and 8316 is MCT8316AEVM_MSP430FR2355_Firmware:

However, this project is not available in the product development resources of the MCT8316A:

1) Could you help confirm if this project firmware for the 430 monolithic the MCT8316AEVM? And what is the MCx8323 in this project?

Since the customer is not able to purchase MCT8316AEVM, they are wondering whether the below method is possible: 

To initialize the MCT8316AEVM_MSP430FR2355_Firmware_GUI on the MSP430FR2355 LaunchPadTM development kit, And replace the 32.768 KHz of the 2355 on the LaunchPad with 4.0 MHz because the 2355 external crystal on the MCT8316AEVM is 4.0 MHz.

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Genius 9220 points

    HI Cherry,

    The MCx8316AEVM_MSP430FR2355 is the correct firmware for the MSP430FR2355 on the MCT8316AEVM. The file named MCx8323 was due to legacy reasons during development and should have been renamed to something generic. The same firmware project can be used for both MCT8316AEVM and MCF8316AEVM. Here's the latest version:

    0243.MCx8316AEVM_MSP430FR2355_Firmware.zip

    Yes, it is possible to replace the crystal on the LaunchPad with 4.0 MHz so that the clock setup code doesn't have to be modified. However, since the LaunchPad uses its onboard eZ-FET debugger as USB-UART interface, instead of the FTDI chip on the MCT8316AEVM, the communication speed would be significantly slower when communicating with the GUI.

    If they don't need the GUI and just want to use the MSP430FR2355 to send I2C read/writes to the MCT8316A, here's a MSP430FR2355 project that shows a simple example of writing to the device EEPROM. Please keep in mind that the example is for the MCF8316A, but they simply need to change the slave address and the register addresses to match MCT8316A.

    MCF8316AEVM_EEPROM_WRITE.zip

    Regards,
    Eric C.

  • 0 in reply to Eric Chen
    TI__Mastermind 22235 points

    Hi Eric C.,

    Thanks for your help and the documentations you given do help!

    Here're also 2 questions:

    1) When using the EZ-FET MSP430FR2355 to firmware the 2355, is there any relation to the crystal frequency for external use of the 2355 (32.768 KHz or 4.0 MHz)?

    The customer wants to first cure the MCx8316AEVM_MSP430FR2355_Firmware without changing the 2355 external crystal (32.768kHz). When done, replace it with an external 4.0MHz crystal, is this having any effect on updating the 2355 code again?

    2) If the customer would like to flash and debug the 8316A with the MCT8316AEVM GUI, is it possible to be implemented through the way below:

    After the 2355 is finished flashing, disconnect the EZFET_UARTRXD, EZFET_UARTTXD from the corresponding BCLUART_RXD, BCLUART_TXD connections jumper. And connect BCLUART_RXD, BCLUART_TXD, GND through the DuPont cable to the UART<-> USB adapter cable, USB connector to the PC.

    Does this resolve the issue of crystal frequency change which prevents the communication function of the upper computer from being used?

    Thanks and regards,

    Cherry

  • +1 in reply to Cherry Zhou
    TI__Genius 9220 points

    Hi Cherry,

    1. The MCx8316AEVM_MSP430FR2355_Firmware code configures the clock using the external 4MHz crystal as a FLL reference (I believe the firmware sets up the FR2355 MCLK, SMCLK, to be 24MHz using FLL) If the customer flashes the existing firmware onto the LaunchPad with a 32.768kHz crystal, the firmware will fail to initialize the clock system, and the program will probably get stuck at the clock initialization functions. They would need to modify the clock system setup code to initialize the clock with a 32.768kHz FLL clock reference instead.
    2. Yes, connecting the BCLUART_RXD, BCLUART_TXD, GND to a UART <-> USB adapter cable, which has a built-in FTDI chip, would theoretically allow the MCT8316AEVM GUI to identify the FTDI COM Port and communicate with the MSP430FR2355. You would then jumper wire P4.6 and P4.7 (UCB1SDA and UCB1SCL) to the MCT8316A for I2C communication.

    Regards,
    Eric C.