Pinecil Firmware - Revision history

Altf4arnold: Adding support for package manager and better doc for Linux/MAC

2024-12-28T18:51:52Z

Adding support for package manager and better doc for Linux/MAC

← Older revision		Revision as of 18:51, 28 December 2024
Line 81:		Line 81:

	'''Option 2: Blisp Flasher''' [https://github.com/pine64/blisp#how-to-update-pinecil-v2 from here]. This is a CLI that runs in a terminal console; get the latest zip file for Linux or Mac. The main page has background info and there are instructions if you want to [https://github.com/pine64/blisp/wiki/Update-Pinecil-V2 build it from code] instead of using the easier premade executable.		'''Option 2: Blisp Flasher''' [https://github.com/pine64/blisp#how-to-update-pinecil-v2 from here]. This is a CLI that runs in a terminal console; get the latest zip file for Linux or Mac. The main page has background info and there are instructions if you want to [https://github.com/pine64/blisp/wiki/Update-Pinecil-V2 build it from code] instead of using the easier premade executable.
	# Extract the Blisp zip, and using a terminal, <code>cd</code> to the blisp folder.		# Extract the Blisp zip, and using a terminal, <code>cd</code> to the blisp folder.BLISP may also be available in your package manager (brew, AUR,...)
	# Download the latest [https://github.com/Ralim/IronOS/releases/ stable Pinecilv2.zip release] (scroll down to the Assets section, get the Pinecilv2.zip).		# Download the latest [https://github.com/Ralim/IronOS/releases/ stable Pinecilv2.zip release] (scroll down to the Assets section, get the Pinecilv2.zip).
	# Extract the zip file and put <code>Pinecilv2_EN.bin</code> (for English) into the Blisp folder (same place as the Blisp executable). Other languages are available, substitute the EN.bin file for the language file desired (use the 2-digit international language code). If you have the Pinecil Zip, the rest could be deleted, only the single BIN file is needed. Select the appropriate two-letter code for your language. If you accidentally flash .dfu file on your Pinecil, it will not boot or work - be sure to only use the BIN file.		# Extract the zip file and put <code>Pinecilv2_EN.bin</code> (for English) into the Blisp folder (same place as the Blisp executable). Other languages are available, substitute the EN.bin file for the language file desired (use the 2-digit international language code). If you have the Pinecil Zip, the rest could be deleted, only the single BIN file is needed. Select the appropriate two-letter code for your language. If you accidentally flash .dfu file on your Pinecil, it will not boot or work - be sure to only use the BIN file.
	# Connect the V2 to the PC and enter Flash mode: hold down the [-] before plugging the cable to the back of Pinecil. See ([[#Flash_Mode\| Flash Mode section for details]]). If you are curious on Linux, it will connect as a serial ''ttyACM'' USB ACM type device.		# Connect the V2 to the PC and enter Flash mode: hold down the [-] before plugging the cable to the back of Pinecil. See ([[#Flash_Mode\| Flash Mode section for details]]). If you are curious on Linux, it will connect as a serial ''ttyACM'' USB ACM type device.
	# Screen on pinecil should be black/empty before proceeding or you are not in Flash mode.		# Screen on pinecil should be black/empty before proceeding or you are not in Flash mode.
	# '''Blisp must have executable permission set.'''		# If BLISP is installed from source :
	# '''<code>cd </code>''' to the Blisp folder and '''<code>ls -l</code>''' to check permissions of blisp.		## '''Blisp must have executable permission set.'''
	# Make blisp executable: '''<code>chmod +x ./blisp</code>'''		## '''<code>cd </code>''' to the Blisp folder and '''<code>ls -l</code>''' to check permissions of blisp.
	# Then execute:		## Make blisp executable: '''<code>chmod +x ./blisp</code>'''
			## Then execute:

	'''sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin'''		'''sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin'''
			# If installed through package manager :
			'''blisp write -c bl70x --reset Pinecilv2_EN.bin'''

	11. After a successful update, unplug and reboot it, then hold down '''<code>[-]</code>''' for ~2 seconds to see the new version.		11. After a successful update, unplug and reboot it, then hold down '''<code>[-]</code>''' for ~2 seconds to see the new version.

Cezary17: Added encountered problem with connecting for the first time while flashing on macOS

2024-07-20T15:47:36Z

Added encountered problem with connecting for the first time while flashing on macOS

← Older revision		Revision as of 15:47, 20 July 2024
Line 129:		Line 129:
	#* Try other ports on the PC/laptop, or a different machine. There have been issues with some laptop USB-C ports not negotiating correctly, but the flashing worked using the USB-A port. Try a different OS if you can access one, some people who had issues on Linux for example were able to flash on Windows. Note that some virtual environments might have an issue with flashing to USB ports.		#* Try other ports on the PC/laptop, or a different machine. There have been issues with some laptop USB-C ports not negotiating correctly, but the flashing worked using the USB-A port. Try a different OS if you can access one, some people who had issues on Linux for example were able to flash on Windows. Note that some virtual environments might have an issue with flashing to USB ports.
	#* Don't use a hub, connect directly to a port, ports on the back of a PC may sometimes be better as they are directly connected to the motherboard. </li>		#* Don't use a hub, connect directly to a port, ports on the back of a PC may sometimes be better as they are directly connected to the motherboard. </li>
			# On macOS when connecting the Pinecil for the first time the OS will prompt you to allow an external device to connect. After allowing unplug the Pinecil and plug it in boot mode again, otherwise the loader may fail to connect (Error: "Failed to receive response")
	# Follow the Flash mode instructions and make sure the [-] button is held down BEFORE plugging in the cable to the back of the Pinecil. And don't release for ~10 seconds.		# Follow the Flash mode instructions and make sure the [-] button is held down BEFORE plugging in the cable to the back of the Pinecil. And don't release for ~10 seconds.
	# If that doesn't work try holding down the <code>[-]</code> the whole time (don't let go of the button).		# If that doesn't work try holding down the <code>[-]</code> the whole time (don't let go of the button).

Weissnix4711: /* Boot Logo Art */ Update details for flashing logos on V2

2023-12-16T16:09:05Z

Boot Logo Art: Update details for flashing logos on V2

← Older revision		Revision as of 16:09, 16 December 2023
Line 189:		Line 189:

	* Boot logo art is art that you custom make or download from [https://github.com/Ralim/IronOS-Meta IronOS Meta]. It displays when you initially power on the Pinecil (boot up).		* Boot logo art is art that you custom make or download from [https://github.com/Ralim/IronOS-Meta IronOS Meta]. It displays when you initially power on the Pinecil (boot up).
	* Currently '''only''' older Pinecil V1 models which use DFU files can flash boot logo art.
	* Download and extract all the premade Boot logo art from this [https://github.com/Ralim/IronOS-Meta/releases pinecil.zip file here].		* Download and extract all the premade Boot logo art from this [https://github.com/Ralim/IronOS-Meta/releases pinecil.zip file here].
	* Note that for Pinecil V1, only the images with filename "dfu" will work, you can delete all other formats from the extracted zip.		* Note that for Pinecil V1, only the images with filename "dfu" will work, you can delete all other formats from the extracted zip.
	* Sample images of [https://github.com/Ralim/IronOS-Meta/tree/main/Bootup%20Logos#logos-preview premade free art].		* Sample images of [https://github.com/Ralim/IronOS-Meta/tree/main/Bootup%20Logos#logos-preview premade free art].
	* To make custom art, [https://github.~~com~~/~~Ralim~~/~~IronOS-Meta~~ follow instructions here].		* To make custom art, [https://ralim.github.io/IronOS/Logo/ follow instructions here].
	* Some art is animated: the very small file size limit for boot logos prevents too many frames from being possible.		* Some art is animated: the very small file size limit for boot logos prevents too many frames from being possible.
	[[File:IronOS.gif]]		[[File:IronOS.gif]]
Line 203:		Line 202:
	=== Pinecil V2 model ===		=== Pinecil V2 model ===

	* Ralim has started work on this ([https://github.com/Ralim/IronOS/issues/1373#issuecomment-1414925011 reference]). Please watch this ticket, give Ralim support and encouragement as this is all volunteer. He is trying to change the Blisp flasher ~~so it allows people~~ to ~~upload~~ art files directly to V2 easily and without needing to do the more complex custom build of the firmware with an embedded art file.		* Blisp flasher is now updated to allow uploading art files directly to V2 easily and without needing to do the more complex custom build of the firmware with an embedded art file.
	** Logo flashing is working ~~in [https://github.com/Ralim/IronOS/releases/tag/v2.22-rc Release Candidate 2~~.22]. Generate the logo with <code>img2logo.py</code> then flash the generated <code>.dfu</code> file using <code>blisp</code> just as you would with firmware		** Logo flashing has been working since release V2.22. Generate the logo with <code>img2logo.py</code> then flash the generated <code>.dfu</code> file using <code>blisp</code> just as you would with firmware

	* If you are not comfortable converting the image file into BIN and building a custom version of IronOS firmware and just want the "IronOS" animated boot logo. Then use the 2.21-animated.zip file in this link made by PowerWiesel to share with the community. Just download the zip, get the Pinecil_EN.BIN (or other language) file from it, and and update Pinecil V2 like normal.
	** [https://github.com/Ralim/IronOS-Meta/issues/32#issuecomment-1517068391 IronOS animated logo zip here]
	** Use [https://github.com/Spagett1/PineFlash#clamp-premade-binaries PineFlash app] or blisp flasher (command line).

	* Custom Art: wbokslag devised a temporary work-around to convert any custom image and embed into IronOS, which is then compiled as a custom build. This is a little advanced, requires some knowledge of Github and comfort with copying code files. wbokslag wrote [https://github.com/Ralim/IronOS-Meta/issues/32#issuecomment-1505172982 detailed steps here].


	[[Category:Pinecil]]		[[Category:Pinecil]]

Pavel: /* Pinecil V2 model */ Add info on logo flashing for 2.22-rc

2023-08-27T23:20:45Z

Pinecil V2 model: Add info on logo flashing for 2.22-rc

← Older revision		Revision as of 23:20, 27 August 2023
Line 204:		Line 204:

	* Ralim has started work on this ([https://github.com/Ralim/IronOS/issues/1373#issuecomment-1414925011 reference]). Please watch this ticket, give Ralim support and encouragement as this is all volunteer. He is trying to change the Blisp flasher so it allows people to upload art files directly to V2 easily and without needing to do the more complex custom build of the firmware with an embedded art file.		* Ralim has started work on this ([https://github.com/Ralim/IronOS/issues/1373#issuecomment-1414925011 reference]). Please watch this ticket, give Ralim support and encouragement as this is all volunteer. He is trying to change the Blisp flasher so it allows people to upload art files directly to V2 easily and without needing to do the more complex custom build of the firmware with an embedded art file.
			** Logo flashing is working in [https://github.com/Ralim/IronOS/releases/tag/v2.22-rc Release Candidate 2.22]. Generate the logo with <code>img2logo.py</code> then flash the generated <code>.dfu</code> file using <code>blisp</code> just as you would with firmware

	* If you are not comfortable converting the image file into BIN and building a custom version of IronOS firmware and just want the "IronOS" animated boot logo. Then use the 2.21-animated.zip file in this link made by PowerWiesel to share with the community. Just download the zip, get the Pinecil_EN.BIN (or other language) file from it, and and update Pinecil V2 like normal.		* If you are not comfortable converting the image file into BIN and building a custom version of IronOS firmware and just want the "IronOS" animated boot logo. Then use the 2.21-animated.zip file in this link made by PowerWiesel to share with the community. Just download the zip, get the Pinecil_EN.BIN (or other language) file from it, and and update Pinecil V2 like normal.
Line 210:		Line 211:

	* Custom Art: wbokslag devised a temporary work-around to convert any custom image and embed into IronOS, which is then compiled as a custom build. This is a little advanced, requires some knowledge of Github and comfort with copying code files. wbokslag wrote [https://github.com/Ralim/IronOS-Meta/issues/32#issuecomment-1505172982 detailed steps here].		* Custom Art: wbokslag devised a temporary work-around to convert any custom image and embed into IronOS, which is then compiled as a custom build. This is a little advanced, requires some knowledge of Github and comfort with copying code files. wbokslag wrote [https://github.com/Ralim/IronOS-Meta/issues/32#issuecomment-1505172982 detailed steps here].




	[[Category:Pinecil]]		[[Category:Pinecil]]

River: /* Boot Logo Art */ add link

2023-06-06T18:56:14Z

Boot Logo Art: add link

← Older revision		Revision as of 18:56, 6 June 2023
Line 188:		Line 188:
	=== Get Art ===		=== Get Art ===

	* Boot logo art is art that you custom make or download from IronOS Meta. It displays when you initially power on the Pinecil (boot up).		* Boot logo art is art that you custom make or download from [https://github.com/Ralim/IronOS-Meta IronOS Meta]. It displays when you initially power on the Pinecil (boot up).
	* Currently '''only''' older Pinecil V1 models which use DFU files can flash boot logo art.		* Currently '''only''' older Pinecil V1 models which use DFU files can flash boot logo art.
	* Download and extract all the premade Boot logo art from this [https://github.com/Ralim/IronOS-Meta/releases pinecil.zip file here].		* Download and extract all the premade Boot logo art from this [https://github.com/Ralim/IronOS-Meta/releases pinecil.zip file here].

River: /* Troubleshoot V2 Flashing */

2023-06-06T18:52:45Z

Troubleshoot V2 Flashing

← Older revision		Revision as of 18:52, 6 June 2023
Line 105:		Line 105:
	# Two different samples work when Command (cmd) terminal is run as administrator. First move into the folder you have both blisp.exe and Pinecil_EN.bin. Then execute one of the following:		# Two different samples work when Command (cmd) terminal is run as administrator. First move into the folder you have both blisp.exe and Pinecil_EN.bin. Then execute one of the following:

	C:\Users\yourName\Downloads\blisp1>blisp.exe write -c bl70x --reset Pinecilv2_EN.bin		C:\Users\yourName\Downloads\blisp1> blisp.exe write -c bl70x --reset Pinecilv2_EN.bin
	C:\Users\yourName\Downloads\blisp1> .\blisp.exe write -c bl70x --reset .\Pinecilv2_EN.bin		C:\Users\yourName\Downloads\blisp1> .\blisp.exe write -c bl70x --reset .\Pinecilv2_EN.bin

River: /* Troubleshoot V2 Flashing */

2023-06-06T18:51:34Z

Troubleshoot V2 Flashing

← Older revision		Revision as of 18:51, 6 June 2023
Line 102:		Line 102:

	# Double check that the command is typed exactly, e.g., in Windows, the dot\slash <code> .\ </code> can not be skipped in Powershell.		# Double check that the command is typed exactly, e.g., in Windows, the dot\slash <code> .\ </code> can not be skipped in Powershell.
	# For Windows, instead of powershell, try '''command''' app (right click, run as administrator) ~~and~~ move ~~into~~ the blisp folder; [https://www3.ntu.edu.sg/home/ehchua/programming/howto/CMD_Survival.html#zz-2.1 example commands to move to folders].		# For Windows, instead of powershell, try '''command''' app (right click, run as administrator). Inside command, move/change to the blisp folder (cd command); [https://www3.ntu.edu.sg/home/ehchua/programming/howto/CMD_Survival.html#zz-2.1 example commands to move to folders].
	# Two different samples work when Command (cmd) terminal is run as administrator. First move into the folder you have both blisp.exe and Pinecil_EN.bin. Then execute one of the following:		# Two different samples work when Command (cmd) terminal is run as administrator. First move into the folder you have both blisp.exe and Pinecil_EN.bin. Then execute one of the following:

River: /* Update V2: Windows */

2023-06-04T19:22:45Z

Update V2: Windows

← Older revision		Revision as of 19:22, 4 June 2023
Line 36:		Line 36:
	'''Option 1: PineFlash''' GUI updater it's an all-in one app that downloads firmware and flashes.		'''Option 1: PineFlash''' GUI updater it's an all-in one app that downloads firmware and flashes.
	# Download the easy premade binary installer [https://github.com/Spagett1/PineFlash for Windows here].		# Download the easy premade binary installer [https://github.com/Spagett1/PineFlash for Windows here].
	# If PineFlash doesn't work, then try blisp terminal app.		# If PineFlash doesn't work, then try [https://github.com/pine64/blisp blisp terminal app].


	'''Option 2: Blisp''', the rest of the instructions below are for Blisp.		'''Option 2: Blisp''', the rest of the instructions below are for [https://github.com/pine64/blisp Blisp].
	# It is a CLI (command line interface or terminal) and needs a tool like Powershell 7 which is already installed on most Windows PCs. For using BLISP only a couple basic terminal commands are needed such as <code>cd</code> to change directories (folders).		# It is a CLI (command line interface or terminal) and needs a tool like Powershell 7 which is already installed on most Windows PCs. For using BLISP only a couple basic terminal commands are needed such as <code>cd</code> to change directories (folders).
	# If you prefer to use "command" terminal over Powershell, see instructions for Command in [[Pinecil_Firmware#Troubleshoot_V2_Flashing\|Troubleshooting and then skip to #8 here]]		# If you prefer to use "command" terminal over Powershell, see instructions for Command in [[Pinecil_Firmware#Troubleshoot_V2_Flashing\|Troubleshooting and then skip to #8 here]]

River: /* Troubleshoot V2 Flashing */

2023-05-27T22:58:39Z

Troubleshoot V2 Flashing

← Older revision		Revision as of 22:58, 27 May 2023
Line 120:		Line 120:


	# <li value="5"> In Windows, view "hidden devices" will show all hidden Ports(COM & LPT) even when pinecil V2 is not connected. This may help as some unknown devices may be claiming COM ports or in conflict. Open Device Manager, click View in the menu bar, and choose “Show hidden devices”. This shows devices/software that are already claiming COM ports but might not be connected presently. You can also watch pinecil V2 connect and disconnect live on Device manager to see the COM it is assigned. The COM number can even be changed in Device manager by going to the Port properties, Port Settings, Advanced. Some devices have issues in windows if they are not connected as a lower ~~range~~, say between COM1 ~~and~~ COM4 ([https://www.virtual-serial-port.org/articles/com-port-on-windows-10/ reference]). You might discover several assigned invisible com ports for devices/software installed long ago.		# <li value="5"> In Windows, view "hidden devices" will show all hidden Ports(COM & LPT) even when pinecil V2 is not connected. This may help as some unknown devices may be claiming COM ports or in conflict. Open Device Manager, click View in the menu bar, and choose “Show hidden devices”. This shows devices/software that are already claiming COM ports but might not be connected presently. You can also watch pinecil V2 connect and disconnect live on Device manager to see the COM it is assigned. The COM number can even be changed in Device manager by going to the Port properties, Port Settings, Advanced. Some devices have issues in windows if they are not connected as a lower COM number, say between COM1 to COM4 ([https://www.virtual-serial-port.org/articles/com-port-on-windows-10/ reference]). You might discover several assigned invisible com ports for devices/software installed long ago.

	[[File:Show-hidden.png \|none\|550px\|left\|thumb\| Windows Device Manager, Show all hidden COMM Ports]]		[[File:Show-hidden.png \|none\|550px\|left\|thumb\| Windows Device Manager, Show all hidden COMM Ports]]

River: /* Troubleshoot V2 Flashing */

2023-05-27T22:56:45Z

Troubleshoot V2 Flashing

← Older revision		Revision as of 22:56, 27 May 2023
Line 120:		Line 120:


	# <li value="5"> In Windows, view "hidden devices" will show all hidden Ports(COM & LPT) even when pinecil V2 is not connected. This may help as some unknown devices may be claiming COM ports or in conflict. Open Device Manager, click View in the menu bar, and choose “Show hidden devices”. This shows devices that are already claiming COM ports but might not ~~even~~ be connected presently. You can also watch pinecil connect and disconnect live on Device manager to see the ~~COMM~~ it is assigned. The COM number can even be changed in Device manager by going to the Port properties, Port Settings, Advanced. Some devices have issues if they are not connected as a lower range, say between COM1 and COM4 ([https://www.virtual-serial-port.org/articles/com-port-on-windows-10/ reference]). You might discover several assigned invisible ~~comm~~ ports for devices/software installed long ago.		# <li value="5"> In Windows, view "hidden devices" will show all hidden Ports(COM & LPT) even when pinecil V2 is not connected. This may help as some unknown devices may be claiming COM ports or in conflict. Open Device Manager, click View in the menu bar, and choose “Show hidden devices”. This shows devices/software that are already claiming COM ports but might not be connected presently. You can also watch pinecil V2 connect and disconnect live on Device manager to see the COM it is assigned. The COM number can even be changed in Device manager by going to the Port properties, Port Settings, Advanced. Some devices have issues in windows if they are not connected as a lower range, say between COM1 and COM4 ([https://www.virtual-serial-port.org/articles/com-port-on-windows-10/ reference]). You might discover several assigned invisible com ports for devices/software installed long ago.

	[[File:Show-hidden.png \|none\|550px\|left\|thumb\| Windows Device Manager, Show all hidden COMM Ports]]		[[File:Show-hidden.png \|none\|550px\|left\|thumb\| Windows Device Manager, Show all hidden COMM Ports]]