Pin and Peripheral Setup
Keep the firmware and the board in agreement, so each pin does what the schematic says.
Flux maps firmware configuration to the connections in your schematic. A clear pin map helps you connect firmware behavior to the signals, buses, clocks, and power settings of the board.
Create a pin map
Tell Flux to make a pin map from the current schematic. Include any names used by your firmware or test plan.
Open the Chat panel and ask Flux to create or update the pin map. Open Files to read the table in the firmware starter document. The map includes each signal's function, pin, connected net, direction, and notes.
Function | Pin | Connected to | Direction | Notes |
|---|---|---|---|---|
Sensor data | MCU pin |
| Input | Add voltage and timing details |
Status LED | MCU pin |
| Output | Record active level |
Bus clock | MCU pin |
| Bidirectional | Record bus speed |
Flux names pin definitions after schematic nets. This keeps source labels connected to the schematic and makes later updates easier to follow.
Set up buses and clocks
Tell Flux which peripherals use each bus and what configuration the device needs.
Open Chat and describe the required bus speed, device addresses, serial format, or clock target. Flux can map I2C, SPI, UART, and RS-485 connections and list addresses for connected devices. It can document the oscillator and PLL configuration so firmware timing follows the board clock.
The pin map also records power and boot configuration. Ask Flux to include regulator modes, required voltage rails, boot strap pins, reset signals, and the expected state of each signal during startup. These details connect firmware initialization to the power and boot design.
Resolve pin conflicts
Tell Flux to compare the firmware configuration with the schematic and identify conflicting assignments.
Open Chat with the schematic and firmware document in the project. Ask Flux to compare each pin and bus assignment with the schematic nets. Flux can check for a pin used by multiple functions, a peripheral mapped to the wrong net, and a bus connection that conflicts with another assignment.
When you change a pin or connect a peripheral, ask Flux to update the table and firmware defines. It can keep the function, pin, connected net, direction, and notes together. Read the updated table in Files, then continue with writing firmware or keeping firmware in sync with your hardware.
Record power and startup details
Tell Flux which power and boot conditions to include in the firmware setup.
Open Chat with the schematic and firmware document in the project. Ask Flux to include regulator modes, power rails, reset behavior, and boot strap pins in the configuration notes. Select Files in the project view switcher to read the updated details beside the pin map.
Clock and startup details connect the board to the firmware timing. Include oscillator frequency, PLL configuration, and the clocks used by each peripheral. Record the required state of boot pins and reset during startup. Flux can use these values when it generates initialization and build notes.
Keep this configuration in the firmware starter document. When a schematic change affects a rail, clock, reset, or boot pin, ask Flux to update the notes and compare the pin map again. Continue with build and test firmware to create an image for the configured target.