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.

CAPTIVATE-FR2633: Captivate design development

Guru 16770 points
Part Number: CAPTIVATE-FR2633
Other Parts Discussed in Thread: MSP-FET, MSP430FR2633, CAPTIVATE-PGMR,

Hi

I want to confirm a way to evaluate Captivate design and move it to customer's appliation.

Please see below file.

e2e_eval.xlsx


A is prototype. The prototype has been already finished evaluating.
So, application software is prepared in prototype.

B is final customer's application and it is on work now.

Application software that developed with A would be diverted to B.
And the application would be downloaded to MSP430FR2633 with MSP-FET in B design.
Is this way of development to final system feasible?

BestRegards

  • Hello na na78,

    The MSP430FR2633 programmed in customer 'A' design is programmed by the CAPTIVATE-PGMR using the SPY-BY-WIRE (TST and RST pins) on the MSP.
    In design 'B', if customer makes the MSP430FR2633 TST and RST pins available to a connector on the PCB, the MSPFET programmer can program the MSP the same way as is done in 'A'.

    Does this answer your question?
  • Hi Dennis

    Thank you for your reply.

    I will ask the customer to have a pin layout to connect to CAPTIVATE-PGMR from MSP430 customer board because fine tuning with Captivate Design Center  for the customer's layout might be needed.

    In this case, customer's boards would be programmed only by SBW.  

    Could it be reasonable?

    And I have additional question.

    CAPTIVATE-FR2633 has 32KHz XTAL externally.

    In schamatics, XTAL is surrounded with dot-line. (I don't know what it means)

    Is it possible to eliminate XTAL?  Is there any impact if XTAL is eliminated?

    BestRegards

  • Yes, if the customer is going to program and perform tuning with the CapTIvate programmer, then the board should have the following connections:

    * +3.3v (OPTIONAL) = if programmer provides power to the customer's board during programming and tuning. If board self powered then this is not needed.
    * GND
    * TST = programming
    * RST = programming

    The other pins needed depend on the communications interface (UART or I2C) customer is going to use with the Captivate design center.
    * TXD (UART) or SDA(I2C)
    * RXD (UART) or SCL(I2C)
    * IRQ (OPTIONAL) Only needed if using I2C

    The external 32Khz crystal is used to provide a very low power (1uA) clock source for the system and CapTIvate interval timer that allows the peripheral to perform measurements while the CPU remains in low power mode. This is important if device is battery powered. If not battery powered then the crystal is not needed and the internal REF0 clock source (15uA) can be used for CapTIvate instead.

    The other reason the external crystal may be needed is for a stable clock source for the clock system if UART interface is used and the device will experience changes in voltage (battery operation) or extreme changes in temperature. The crystal typically has a very low drift over temperature and maintains a reliable frequency that is needed to ensure no errors in the UART communications.
    If customer not using UART, then crystal not needed.
  • Hello na na78,

    I haven’t heard from you for a couple of days now, so I’m assuming you were able to resolve your issue.
    If this isn’t the case, please click the "This did NOT resolve my issue" button and reply to this thread with more information.
    If this thread locks, please click the "Ask a related question" button and in the new thread describe the current status of your issue and any additional details you may have to assist us in helping to solve your issues.

**Attention** This is a public forum