Part Number: MSP430-SDK
Other Parts Discussed in Thread: CAPTIVATE-FR2633
I have now spent almost a full day digging through
- the MSP430 Academy https://dev.ti.com/tirex/explore/node?node=A__AA78LmvkwjuaUT184Nz.jg__com.ti.MSP430_ACADEMY__bo90bso__LATEST
- the MSP430 Users Guide www.ti.com/.../slau445i.pdf
- the MSP430 Software Library docs https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPWare/2_40_00_37/exports/MSPWare_2_40_00_37/captivate/docs/users_guide/html/ch_lib.html
- marginally helpful forum answers e.g. https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/626377/msp430fr2633-custom-baud-rate-configuration
- clearer but I am beginning to suspect misleading forum answers e.g. https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1062712/msp430fr2676-read-and-send-serial-data
- various other forum posts more clearly stating 250,000 as the expected "default baud" (which aligns with the calculations I had by then already done to confirm the chain from a base clock of 16MHz thru divisors in the generated CAPT_BSP.c and CAPT_Interface.c fiels)
I still cannot see any traffic on the (Device Manager listed) "MSP Application UART1" (presently COM6), or for that matter on the "MSP Debug Interface" (COM5), when connecting with either off-the-shelf serial monitors or custom serial tooling, although COM5 at least denies access when CCS is in debug mode. This is true irrespective of whether I attempt to listen in on the default/generated Design Center UART configuration using I presume the payloads per https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPWare/2_40_00_37/exports/MSPWare_2_40_00_37/captivate/docs/users_guide/html/ch_lib.html#ch_lib_communications_protocol_sensorpacket or when I adjust the generated project of my own Design Center designs per the Backdoor_UART sample (including the undisclosed tweaks e.g. setting UART__ENABLE=true as a MSP430 Compiler options -> Predefined Symbol) and try to listen for the simplified user-generated data at 9600 baud.
I am unsure if https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/CapTIvate_Design_Center/latest/exports/docs/users_guide/html/CapTIvate_Technology_Guide_html/markdown/ch_evm_CAPT_PGMR.html#using-the-hid-bridge is telling me anything relevant to this scenario, e.g. that it _should_ work but only if I use some other tooling to set the HID operating mode to UART pass-thru? but I have tried both with and without Design Center being Connected (and successfully displaying inputs & data streams), and DC is the only off-the-shelf tool even obliquely mentioned with the ability to communicate directly to the HID layer (which I must experimentally assume is how it's getting all the sensor data without anything showing up on UART1).
All I want to do is verify that I can receive sensor data, in any format, to my own external apps, over a channel less industrial than I2C or raw PCM pins. My next step, I think, is going to need to be soldering the necessary headers directly to the CAPTIVATE-FR2633 dev board and seeing if I can tap the TX/RX lines with a standalone serial dongle, but this seems like a needlessly complex route when UART communication is advertised at every level of the board & programmer docs.
Am I missing something, and if so, what?
