Configuring RT1062 BOOT_MODE and BT_CFG for Flash Boot

The panel or programming fixture shows the board entering the wrong boot path, failing to present the serial downloader, or booting unpredictably between power cycles. Start here: measure BOOT_MODE and every used BT_CFG input during reset. A floating boot input is not a valid manufacturing strategy for the RT1062.

Reject floating boot inputs first

Do not leave BOOT_MODE or BT_CFG floating. An undriven input can cross its switching threshold because of leakage, contamination, probe loading, supply ramp behavior, or coupled noise. The result may change with temperature, board population, fixture connection, or power-cycle timing.

Check each boot-related net with the board unpowered and powered:

• With power removed, verify that every input has a defined pull path rather than an open circuit.
• During power-up and reset release, measure the input against the logic rail and ground.
• Confirm that the measured level remains outside the input threshold region throughout the sampling interval.
• Compare the intended state with the RT1062 reference-manual boot-mode table.

Separate strap selection from fuse selection

Your manufacturing sequence has two distinct configurations. The first must select the serial downloader on an unfused board. The second must select fuse-controlled boot and point that path at the populated flash device.

Do not treat BOOT_MODE and BT_CFG as interchangeable. BOOT_MODE selects the broad boot path. The configuration inputs or their fuse equivalents supply details used by that path. Determine the required combination from the RT1062 reference manual before drawing the strap network.

The decisive reading is the actual logic state at the processor pin during reset, not the schematic label or the unloaded resistance. If the measured states select the serial downloader, continue to communication testing. If they select another path, correct the pull network or fixture drive before changing software.

Prove the serial downloader path

Connect the manufacturing fixture with the permanent flash still unprogrammed. Command a full power cycle; a warm reset may not reproduce the same boot sampling conditions.

1. Drive or strap BOOT_MODE and the required BT_CFG inputs to the serial-downloader combination listed in the RT1062 reference manual.
2. Capture the supply ramp, reset signal, and boot-input voltages on the same acquisition.
3. Release reset and confirm that the host detects the serial downloader.
4. Repeat several cold starts with the fixture connected and disconnected as the production process requires.
5. Stop if downloader entry changes between identical starts. Fix the electrical state before downloading an application or programming fuses.

Changing the application image, rebuilding the binary, or repeatedly reconnecting the host wastes time when the processor never entered the downloader. Prove boot-path selection first, then diagnose the host link.

Validate flash before burning fuses

Download the initial application through the confirmed serial-downloader path and program the external flash. Do not burn the final boot fuses immediately.

1. Read back the programmed flash and compare it with the intended binary.
2. Check that the image is located where the selected flash-boot configuration expects it.
3. Verify the flash electrical interface, pin routing, and required configuration against the processor and memory documentation.
4. Use a reversible strap configuration to select flash boot, if the board design provides one.
5. Cold-cycle the board and confirm that the application starts from flash without assistance from the downloader.

If reversible flash boot fails, fuse programming will not repair the flash interface or image layout. Return to the flash readback, boot configuration, and reset-time measurements.

Program fuses only after a readback review

Fuse programming is the irreversible branch. Build the fuse image from the RT1062 reference-manual fields, then review it independently against the populated flash and intended boot path. Record both the planned values and the pre-programming readback for each board.

1. Keep the processor in the stable serial-downloader configuration.
2. Program and verify the application in flash.
3. Read the current fuse state; do not assume a blank or uniform factory value.
4. Compare the planned fuse changes bit by bit with the approved manufacturing record.
5. Burn only the fields required to select the intended fuse-controlled flash boot.
6. Read the fuses back before removing downloader access or changing fixture straps.

Do not copy fuse values from a different processor, board revision, or flash population. Do not use a failed flash boot as the trigger to burn more bits. Diagnose the existing state first.

Verify the final production state

Move BOOT_MODE to the fuse-controlled boot selection specified by the RT1062 reference manual. Keep all sampled pins at defined electrical levels even when their settings are no longer intended to control the normal boot path.

1. Remove the serial-downloader override from the fixture.
2. Perform a complete power removal and cold start.
3. Confirm application execution from flash using an application-specific observable output.
4. Read back the programmed fuse fields and store them with the unit record.
5. Repeat the cold-start test across the supply and temperature conditions required by the product.
6. Confirm that the production fixture can still select the approved recovery path, if recovery is part of the design.

A debugger-attached start is not final verification. Debug hardware may alter reset timing, pin loading, or execution control. Judge the result from an unaided cold start.

FAQ