Board Bring-Up
Flux creates a board bring-up plan as a project document. The plan connects firmware and tests to the board's power rails, signals, interfaces, and expected behavior.
Create a bring-up plan
Tell Flux which board to prepare and what equipment or checks your team uses.
Open the Chat panel and ask Flux to prepare the plan from the project. Open Files to read the board bring-up document. The plan can list prerequisites and equipment, visual inspection steps, and each power rail with its expected voltage.
The plan covers critical signals such as reset, boot strap pins, and the crystal. It can include connector tests, programming and debug steps, and expected measurements. Flux organizes the work so you can record results and summarize each test as a pass or fail.
List the test equipment that matches the board, such as a bench supply, meter, serial adapter, debugger, or test fixture. Add the connectors that you want to inspect and the values to measure. Flux can group checks into a sequence from visual inspection to first power-up, programming, and functional tests.
Program and test the board
Tell Flux which interfaces and device behaviors the bring-up plan should cover.
Open Chat and describe the board's programming connector and expected behavior. Flux can write steps to detect the target, read its device ID, flash an image, and read serial output. The plan can include tests for I2C scans, SPI loopback, UART echo, sensors, actuators, ADC inputs, Wi-Fi, and BLE.
Ask Flux to add expected results for each check. For example, include a voltage range for a rail, a response for a serial command, a sensor reading, or an actuator movement. The plan gives you a place to compare measured behavior with the expected result.
Include bus-specific checks such as device discovery on I2C, a known SPI loopback pattern, or a UART echo response. For analog inputs, record the expected ADC range at defined input levels. For wireless checks, name the expected network behavior or BLE response. Each step can state the setup, action, expected result, and measured value.
Keep the plan with firmware
Tell Flux to create firmware or test firmware for the bring-up sequence.
Open Chat to ask Flux for bring-up firmware and tests. Flux can add firmware that exercises board interfaces and records the commands used during testing. Keep the plan, source, and built image together in Files so the test steps refer to the project outputs.
When you change the schematic, ask Flux to update the bring-up plan. It can add or revise rail rows, critical signals, connector tests, and functional checks to match the design. Continue with build and test firmware to create an image and flashing command, or keep firmware in sync with your hardware as the board changes.
Record bring-up results
Tell Flux how to structure measurements and completion results in the plan.
Open Chat after you complete a test and tell Flux the measured value or observed behavior. Select Files in the project view switcher to update the bring-up plan beside the image and firmware source. Ask Flux to summarize the passed checks and the remaining test steps in the document.
Keep the expected result and measured result together. For example, record each rail's expected voltage beside its measured voltage, or record the sensor response after a known stimulus. The pass/fail summary gives your team a clear view of board readiness and helps connect test results to the next design change.