dsap Flashing Instructions (production)¶
dsap operator use is Windows-only. For command details and developer
troubleshooting, see dsap Flashing Instructions
(development).
Purpose¶
Use these instructions on an Assembly Laptop to:
- Flash firmware to the MSP430 MCU.
- Upload the device certificate bundle to the SARA module.
- Set the final device parameters during production.
Prerequisites¶
Before starting, confirm the following:
- The Assembly Laptop has completed the dsap Setup Instructions.
- Windows PowerShell is available on the Assembly Laptop.
- The assembled device is ready for firmware flashing.
- The traveler or work order identifies the required firmware tag.
- The traveler or work order identifies the required gel sensing threshold and envelope voltage. [TODO: Need to flesh this out]
- The Assembly Laptop has BioT API access configured as described in the setup instructions.
- The Assembly Laptop has MSP430 Flasher installed under the standard
C:\TI\MSPFlasher_*orC:\TI\MSP430Flasher_*installation directory, or the actual flasher executable path is known for use withdsap mcu --flasher.
Use latest as the firmware tag only when the traveler or work order
explicitly authorizes it. Otherwise, use the exact firmware tag
provided. Use beta or release candidate firmware tags only when the
traveler or work order explicitly lists the exact prerelease tag, such
as v1.0.1-beta.1.
Equipment and Materials¶
Confirm the following equipment and materials are available:
| Quantity | Equipment Number | Description |
|---|---|---|
| 1 | EQT-0001 | Sonogen Assembly Laptop |
| 1 | EQT-0009 | Sonogen Flashing Module |
| 1 | EQT-0010 | Sonogen Flashing Module Cable |
| 1 | EQT-0011 | MSP-FET (Flash Emulation Tool) |
| 1 | EQT-0012 | USB Programming Cable |
| 1 | SON-0901 | Assembled Device |
Flashing Module Switches¶
Use these Sonogen Flashing Module switches for each operation:
| Operation | Switch |
|---|---|
| MCU flashing | U2 |
| Certificate upload | U3 |
| Parameter setting | U4 |
1. Flash the MCU Firmware¶
1.1 Prepare the Hardware¶
- Boot the Sonogen Assembly Laptop into Windows.
- Connect the MSP-FET to the Assembly Laptop.
- Connect the 14-pin connector from the MSP-FET to the Sonogen Flashing Module.
- Connect the Sonogen Flashing Module to the assembled device.
Operator STOP: Before continuing, stop and set flashing module switches
U2,U3, andU4up. Do not continue until all three switches are up.
1.2 Find the MSP-FET COM Port¶
Open Windows PowerShell in the MSP430 Flasher installation directory and run this command:
The command lists connected FET debuggers, checks FET firmware compatibility, and may prompt you to select one. Example output for a FET with up-to-date firmware:
* -----/|------------------------------------------------------------- *
* / |__ *
* /_ / MSP Flasher v1.3.20 *
* | / *
* -----|/------------------------------------------------------------- *
*
* Evaluating triggers...done
* Executing FET detection sweep:
- 1: MSP-FET @ COM7
- Select FET number: 1
* Initializing interface @ COM7...done
* Checking firmware compatibility:
* FET firmware is up to date.
*
* ----------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------
*/
If prompted, enter the number for the MSP-FET. In the example above,
enter 1.
Write down only the COM port number for use in section 1.3. For
example, write down 7 for COM7. This is for local reference during
flashing and is not a traveler record.
1.3 Run dsap mcu¶
Open Windows PowerShell and run this command, replacing <TAG> with the
firmware tag and <PORT> with the MSP-FET COM port number:
Example:
Wait for dsap to report that firmware flashing completed
successfully. Record the firmware version number from this message on
the traveler:
Do not continue until MCU flashing succeeds.
2. Generate the Serial Number and Certificate Bundle¶
Open Windows PowerShell and run:
Follow the prompts to generate the device serial number and record it on
the traveler. dsap serial --create also:
- creates a PDF device label under
C:\Users\<USER>\dsap\labels; - creates the device object in the BioT cloud;
- downloads the certificate bundle and saves it under
C:\Users\<USER>\dsap\certificates.
Example output for model SB01, device code M, date 2026-05-18,
and sequence number 0001:
Device serial number: SB01M2605180001
Device UID: (01)10860013789401(21)SB01M2605180001
Device label created: C:\Users\<USER>\dsap\labels\SB01M2605180001.pdf
Authenticating to BioT ✅
Setting BioT Unique ID ✅
Downloading certificate bundle ✅
Certificate bundle downloaded: C:\Users\<USER>\dsap\certificates\SB01M2605180001.zip
At the end of the run, dsap prints the full certificate bundle path.
Note that path for use in section 3.3. The certificate bundle path and
Device UID shown are not traveler records.
Do not continue until dsap serial --create succeeds.
3. Upload Device Certificates¶
3.1 Prepare the Hardware¶
- Disconnect the 14-pin MSP-FET connector from the Sonogen Flashing Module.
- Connect the USB Programming Cable between the Assembly Laptop and the Sonogen Flashing Module.
Operator STOP: Before continuing, stop and flip certificate upload switch
U3down, press the reset button, then flipU3back up. Do not continue untilU3is back up.
3.2 Find the USB Serial COM Port¶
- Open Device Manager on the Assembly Laptop.
- Expand Ports (COM & LPT).
- Find the COM port assigned to the USB serial connection.
- Note only the number for use in sections 3.3 and 4.2. For example,
note
7forCOM7. This is not a traveler record.
3.3 Run dsap sara¶
Open Windows PowerShell and run this command, replacing <PATH> with
the full certificate bundle path and <PORT> with the USB serial COM
port number:
Example:
Wait for dsap to report:
Do not continue until certificate upload succeeds.
4. Set Device Parameters¶
4.1 Prepare the Hardware¶
- Keep the USB Programming Cable connected between the Assembly Laptop and the Sonogen Flashing Module.
Operator STOP: Before continuing, stop and flip parameter setting switch
U4down, press the reset button, then flipU4back up. Do not continue untilU4is back up.
Use the same USB serial COM port number found in section 3.2.
4.2 Run dsap params¶
Open Windows PowerShell and run this command, replacing <PORT> with
the USB serial COM port number:
Example:
When prompted, enter or confirm the required values:
- Client ID from the certificate bundle, unless the traveler or work order requires a different non-empty value.
- Gel sensing threshold from the traveler or work order. [TODO: Check this]
- Envelope voltage from the traveler or work order. [TODO: Check this]
If the envelope voltage is 0, dsap warns that the device will be a
sham device and asks for confirmation. Continue only when the traveler
or work order requires a sham device.
Wait for dsap to report that all device parameter-setting steps
completed successfully. Do not disconnect the hardware until the port
close stage completes.
5. Final Checks¶
Before releasing the device from this station:
- Confirm MCU flashing completed successfully.
- Confirm certificate upload completed successfully.
- Confirm device parameter setting completed successfully.
- Confirm all required items are recorded on the traveler.
6. Troubleshooting Notes¶
- If
dsap mcufails before flashing, verify the firmware tag and the MSP-FET COM port number. - If
dsap mcureports that the MSP430 flash utility is not found, stop and notify Sonogen Development or the station owner. - If Windows does not recognize the MSP-FET, stop and notify Sonogen Development or the station owner. The station owner should verify MSP430 Flasher and the TI MSP430 FET Drivers were installed as a Windows Administrator.
- If
dsap saraordsap paramscannot open the port, verify the USB serial COM port number in Device Manager. - Enter only the COM port number with
--port. Use--port 7, not--port COM7. - If
dsap serial --createfails, stop and notify Sonogen Development or the station owner. - If the certificate upload fails while staging certificates, verify
that the selected file is the device certificate bundle
.zipfile. - If
dsap paramsshows the wrong client ID, answernand enter the correct non-empty value from the traveler or work order. The Client ID must be no more than 32 characters long.