Firmware Prompt Examples

Use prompts that describe the device, the behavior, and the result you want. Add details about the schematic, board, timing, and test output to get a useful firmware project document.

Write firmware

Tell Flux what the firmware should do and which hardware it uses.

Write bare-metal firmware for the STM32F103 in this schematic. Blink PC13 at one hertz and document the clock setup.

Build minimal ESP32 firmware that prints a counter once per second over serial. Include source, image files, and flash and RAM use.

Open Chat and describe the behavior. Include the microcontroller, connected peripherals, timing, and output. Ask Flux to write from the schematic or continue from a public repository, uploaded ZIP, or pasted source. Read the generated firmware starter document in Files.

Set up pins and peripherals

Tell Flux to map schematic connections to firmware configuration.

Create a pin map for this schematic with function, pin, connected net, direction, and notes.

Document I2C addresses, SPI and UART pins, clock setup, power modes, and boot strap signals.

Open Chat with the schematic in the project and ask for the pin map. Include bus addresses, clock requirements, and boot behavior. Open Files to read the updated table, then ask Flux to compare it with the firmware source.

Build and test

Tell Flux to compile the project and run checks that match the firmware behavior.

Build this nRF52840 firmware with two real-time tasks. Report the image files and memory footprint.

Run host unit tests, check memory and undefined behavior, report coverage, and analyze the source.

Open Chat and name the board target. Ask for image files, flash and RAM footprint, largest symbols, and a flashing command for your computer. Flux can run host tests and static analysis, then report the results with the project files.

Prepare board bring-up

Tell Flux to create a project plan with the equipment and measurements for your board.

Create a bring-up plan with visual inspection, expected rail voltages, reset and boot checks, and programming steps.

Add bus scans, loopbacks, sensor and actuator tests, ADC measurements, and wireless checks.

Open Chat and ask Flux to create or update the bring-up plan. Open Files to read the project document and bring-up firmware. Include expected voltage, timing, and functional results so the plan has clear pass and fail outcomes.

Sync firmware with hardware

Tell Flux which schematic or mechanical change should update the firmware.

I connected a new sensor and changed two pins. Update firmware, the pin map, and bring-up tests.

Read the spacer's volume from the mechanical model and use it as an STM32 firmware constant.

Open Chat after you change a peripheral, pin, board connection, or mechanical value. Ask Flux to re-check the pin map against the schematic and update the firmware document and bring-up plan.

Connect code and firmware services

Tell Flux which public repository or connected firmware service to use.

Read this public firmware repository and adapt its sensor driver to the schematic.

Use Memfault crash data to identify failures for the next hardware revision.

Open Chat to share a public repository link. To connect GitHub, GitLab, or Memfault, select AI Integrations in the Chat panel, open the Integrations tab, and choose Firmware & Development.

Design the complete device

Tell Flux how firmware works with the electronics and mechanical design.

Design the sensor board, write firmware for its I2C sensor, and create an enclosure with access to the connector.

Create a robot arm with a motor-control board, firmware for its encoders, and mechanical joints with cable clearance.

Open Chat and describe the device, its functions, and the way its electronics and mechanical parts work together. Ask Flux to create a schematic, mechanical model, firmware, and bring-up plan in the project.

Design a handheld monitor with an enclosure, a sensor board, and firmware that shows status on an OLED.

State the device's functions, the physical parts, and how the electronics connect to them. Add the firmware behavior and tests you need. Ask Flux to keep the schematic, mechanical model, firmware, and bring-up plan in one project.

Last updated on

Was this page helpful?