Skip to content

Commit

Permalink
Update initial_rp2040.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Esoterical authored Aug 3, 2024
1 parent a3e5376 commit cf0caeb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion initial_rp2040.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ cd ~/katapult
make menuconfig
```

You will need to adapt the below instructions so they cover _your_ board's specicific configuration. You can find screenshots of settings for common toolheads in the [Hardware Config](../hardware_config/hardware_config.md) section.
You will need to adapt the below instructions so they cover _your_ board's specicific configuration. You can find screenshots of settings for common toolheads in the [Hardware Config](./hardware_config/hardware_config.md) section.

If your board doesn't exist in the hardware_config folder already, then you want the Processor, Clock Reference, and Application Start offset to be set as per whatever board you are running. Set the "Build Katapult deployment application" (this is really only for updating but doesn't hurt having it enabled at this stage), and make sure "Communication Interface" is set to USB. Also make sure the "Support bootloader entry on rapid double click of reset button" is marked. It makes it so a double press of the reset button will force the board into Katapult mode. Makes re-flashing after a mistake a lot easier. Lastly, setting the Status LED GPIO Pin won't affect how katapult functions, but it will give a nice visual indicator (of an LED flashing on and off once a second) on the toolhead to show the board is sitting in Katapult mode.

Expand Down

0 comments on commit cf0caeb

Please sign in to comment.