Skip to content

Update Pinecil V2

Jump to bottom
river-mochi edited this page Apr 21, 2023 · 50 revisions

🖥️ Install Options

  1. Easiest way to update the V2 is using the premade binaries for each OS; download here  

    .\blisp.exe write -c bl70x --reset .\Pinecilv2_EN.bin # windows

    sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin # macos or linux

    🎯 chmod +x ./blisp # macos, if you get blisp command not found

  2. Detailed Instructions in Pinecil wiki here.

  3. For issues, see 🩺Troubleshooting below and the Pinecil Wiki.

  4. If you want to build Blisp executable from code or have a different need (e.g., ARM architecture), see below.


🐧 Build BLISP Flasher from code

Note: this has been tested for Linux x86-64. The build process also works on aarch64 and armv7, and Pinebook Pro ARM.

This also works on MacOS. (both x86 and M1 MacOS work with premade blisp binary, just chmod +x ./blisp if you get blisp not found).

Build Code

git clone --recursive https://github.com/pine64/blisp.git
cd blisp
mkdir build && cd build
cmake -DBLISP_BUILD_CLI=ON ..
cmake --build .
mkdir tools/blisp/data
mkdir -p tools/blisp/data/bl70x

Note: the blisp command will now be in build/tools/blisp/ folder and could later be run with flags as ./tools/blisp/blisp unless you cd (change) into that folder then you only need ./blisp and do not need to type the full path.

Next steps to use the custom build in Linux

⛔ Do not use the Pinecil DC barrel jack while updating firmware or it may destroy the PC and pinecil. ⛔

  1. Get Pinecil V2 firmware from Github Ralim's IronOS

    a. Download the newest stable firmware release here (go to the bottom of the page, below the Assets section, and get the Pinecilv2.zip file).

    b. Extract Pinecilv2.zip and select a language file (English = Pinecilv2_EN.bin).

    c. Move the Pinecilv2_EN.bin (or selected 2-letter language) into the same folder as the blisp command.

    build/tools/blisp/Pinecilv2_EN.bin

    d. Only the Pinecil_EN.BIN file is needed, it is best to Not copy in the *.dfu or other pinecil files into the blisp folder; if you accidentally flash with the *.dfu file, the Pinecil will not work and have a black screen. Those extra files are just automatically compiled by IronOS since other types of irons use dfu and hex. Could just take the bin file and delete the rest of Pinecilv2.zip, it is not needed.

  2. Connect Pinecil to PC by putting it into flashing mode: press and hold minus [-] button, then insert power cable, hold minus for 10 seconds, release.

    a. screen should be black/empty, if not, repeat connection, or find another cable/port.

    b. Pinecil connects as a serial port (Linux = /dev/ttyACM_x_, Windows = COM_x_).

    c. use dmesg -w if you would like to watch the connection, on Linux, BL706 will connect as Manufacturer: BLIOT, ttyACM device.

  3. If connection fails, see troubleshooting below.

  4. If you are in the folder blisp/build/tools/blisp/ then execute

   sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin

  • If you have an issue with blisp not found, ls- l to check permissions and use chmod +x ./blisp to make the blisp file executable.

  • Check that the blisp and Pinecilv2_EN.bin are in the same folder and you are moved into this same folder before executing the command.

  • try the port argument to directly connect to specific port Pinecil is on (linux = ttyACM, windows = COM).

    .\blisp.exe write -p COM3 -c bl70x --reset .\Pinecilv2_EN.bin

  • Note: if a different language is selected, replace Pinecilv2_EN.bin above with the chosen file name (must be a *.bin file).

  1. Almost done: unplug from the PC and restart V2. Hold down the minus [-] button to see the new version number.

  2. Once the flashing is complete. It is recommended to next go to Advanced > Restore Default Settings details here.

    Simply go to Advanced settings > Restore default settings, confirm using the [+] button, when you see Reset OK just wait a few seconds for Pinecil to reset to the main icons. This sets all menu items to defaults, keeps the same firmware version (does not affect any Boot-up logo art if applicable). By setting defaults on new firmware first before customizing, it avoids unexpected behavior especically if you came from a very old version. IronOS usually does not change your custom settings when updating to new releases and usually it's fine.

  3. Congradulations, enjoy your update and Stay Fluxey, my friends!

🩺 Troubleshooting

  1. For MacOS, if you get blisp command not found, then check the blisp permissions with ls -l and do chmod +x ./blisp to make the command executable. This was reported to solve problem with M1 for macOS.

  2. If the Pinecil V2 fails to connect to the PC, check the dmesg command output.

    a. try different cable or flip it over: usb-C to C or Usb-A to C.

    b. don't use a USB hub, directly connect to the USB port on the back of the PC or laptop.

    c. try different Usb ports. Sometimes the rear ports on a PC are better because they are directly connected to the motherboard.

    d. try a different PC/laptop

  3. It is important to hold down the [-] minus button before plugging in the Usb-c cable, and do not release the button for another 10-15 seconds.

  4. If "device not found" but Windows shows it as a COM port in device manager, then try to use the Port argument which specifies the port blisp uses.

  • Details here on Pinecil Wiki.
  • Linus serial port is ttyACM; Windows is COM
  • Example command if Pinecil is connected to Serial Port COM3 (yours may be different)
.\blisp.exe write -p COM3 -c bl70x --reset .\Pinecilv2_EN.bin

  1. If all else fails, then join one of the live community chat channels here as volunteer Pine64 members might have a hint to get the update working.

  2. Open a new issue ticket in this Github/Blisp flasher at https://github.com/pine64/blisp/issues

  3. See Pinecil Wiki for hardware information.

  4. See Github Ralim's IronOS for firmware/software information. This is only the Flasher that loads the firmware; all Pinecil firmware documents and menu instructions are in IronOS.

Clone this wiki locally