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.

MSP-EXP430FR5969: I noticed that the EZ-FET firmware doesn't apply partity settings

Part Number: MSP-EXP430FR5969
Other Parts Discussed in Thread: MSP430FR2311

It would be useful to have this, considering the crypto bootloader in SLAU657 defaults to even parity. Not a question, more FYI.

EZ-FET backchannel UART from RealTerm (also tested with TeraTerm)

FTDI:

  • Thanks for the input, this information will be passed along to the Tools Team.

    Edit: Please note from Table 10 of SLAU647 that the eZ-Firmware on the MSP-EXP430F5994LP supports even parity.

    Regards,
    Ryan

  • For convenience:

    http://www.ti.com/lit/ug/slau647f/slau647f.pdf

  • Is there any way to update the firmware on a Launchpad host MCU?, for example to bring it up to 3.8.0.2?

  • These changes are based on a hardware rev, not firmware, so it will not be possible to include this feature on older LaunchPads.

    Regards,
    Ryan
  • I am unable to get this even parity feature to work on m FR2311 Launchpad board. Here is the version info from MSPFlasher:

    * Driver      : loaded

    * Dll Version : 30902015

    * FwVersion   : 30902015

    * Interface   : DETECT

    * HwVersion   : E 4.0

    * JTAG Mode   : AUTO

    * Device      : MSP430FR2311

    * EEM         : Level 5, ClockCntrl 2

    * VCC OFF

    I can verify that all of the other special baudrate commands from 9620-9624 to work, but 9625 does not. Can someone confirm that this feature works? My test is to open the serial port with speed 9625 and see if parity bits are inserted on the scope.

    Is it possible that the speed value is being filtered in the .kext before making it to the ez-Fet? I can't find the source code for the Mac USB driver kernel extension.

    One other thing, I suspect that even if I were to get the 9625 code to trigger, won't the parity get disabled when I reopen it at 9600 (see ./src/uart/ComBase/COM_Base.c:209). Or it is intended that we run with a odd frequency?

     

**Attention** This is a public forum