Documentation/Flashing/Pinecil V2.md
In the development of this firmware, there are three types of firmware released. These are the "Main" stable releases, which generally have high confidence in being bug free. Release candidates are released slightly more often, and these are generally perfectly fine for everyday use. These are released early to allow for translation checking and for wonderful people to help spot bugs and regressions. Finally, there are the "mainline" builds, which are built from the main git branch. These are built on every change and can be found on the Actions tab (see below).
Main releases are made to the releases page.
Download the zip file that matches your model of soldering iron and extract it.
Select the appropriate file type for your unit, in general Miniware devices need .hex, Pinecil V1 needs .dfu, and Pinecil V2 needs .bin.
Flash according to details below.
For the latest code, you need to download the zip file from the artifacts page for the build that you want.
Head to the Actions page and then select the run for the appropriate branch and beta you would like.
In general you probably want master.
Once you click on a run, scroll down to the "Artifacts" section and then click on your device model name to download a zip file. Then this works the same as a production release (use the correct file).
If you are running into issues such as timeouts during the programming or bootloader errors, the BL702 has a not-amazing USB PHY built in. This can cause problems on cheap cables (especially "thin" ones that tend not to have shielding). One of the authors (Ralim) has found this especially common on the cables supplied with Apple chargers when used with newer Ryzen processor ports.
It is strongly reccomended to use a good quality cable, ideally short. Also try other USB ports, as on some devices they can use different hub's or lengths of signalling, and this can fix the issue.
By the PinecilV2's design, by default some of the internal buses are exposed on the USB3 pins, to enable hacking/debugging/mods. This is suspected it may play poorly on some chipsets. Try using a USB2.0 cable. Others have had luck with chaining USB-C->USB-A->USB-C. This may be due to this, as a lot of these adaptors are USB2 or only USB3 5gbps (half USB3 pins).
Another workaround is to put a USB hub somewhere in the chain, as these will re-form the signal and can work around the issue.
Finally, some users have reported issues under Windows that were fixed by changing OS (Typically to a Linux live cd).