Petitboot, yet another bootloader based on KEXEC

Post Reply
User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

CoolGames wrote:
Sun Aug 30, 2020 12:04 am
tobetter wrote:
Sat Aug 29, 2020 11:25 pm
rod20 wrote:
Sat Aug 29, 2020 9:43 pm
Another question is if you have plans for CEC or LIRC support?
Thanks for your great work.
Due to the lack of SPI memory size, LIRC won't be supported and CEC needs more effort to support it. Out of curiosity, what's the model of the brand of your remote?
I continue to offer my energy and curiosity to get CEC to work as I struggle with it constantly and I want to under stand it.
I moved the Nvidia Shield TV to HDMI on Denon and Panasonic home system and I control and view all the capabilities.
I can ADB into the Nvidia and run any Android app or command to interogate the CEC protocol like I did with the IRC from Hardkernel earlier.
I am also looking at MIDI controllers so just need a way to sniff CEC dialog.

What can I do to help more ?

Code: Select all

leetdavy@cooldroidn2:~$ cec-client 
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect: FAILED
leetdavy@cooldroidn2:~$ cec-client -l
libCEC version: 4.0.4, compiled on Linux-4.4.0-176-generic ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC
Found devices: NONE
leetdavy@cooldroidn2:~$ 

leetdavy@cooldroidn2:~$ sudo get-edid | parse-edid 
[sudo] password for leetdavy: 
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
1 potential busses found: 2
256-byte EDID successfully retrieved from i2c bus 2
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
	Identifier "NS-22D420NA18�"
	ModelName "NS-22D420NA18�"
	VendorName "BBY"
	# Monitor Manufactured week 10 of 2016
	# EDID version 1.3
	# Digital Display
	DisplaySize 480 270
	Gamma 2.20
	Option "DPMS" "false"
	Horizsync 32-68
	VertRefresh 56-75
	# Maximum pixel clock is 170MHz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x800, 60Hz
	#Not giving standard mode: 1280x800, 75Hz
	#Not giving standard mode: 1280x960, 60Hz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1440x900, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz

	#Extension block found. Parsing...
	Modeline 	"Mode 14" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync 
	Modeline 	"Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync -vsync 
	Modeline 	"Mode 1" 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync 
	Modeline 	"Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 3" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
	Modeline 	"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
	Modeline 	"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
	Modeline 	"Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 8" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
	Modeline 	"Mode 9" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 10" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 11" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
	Modeline 	"Mode 12" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
	Modeline 	"Mode 13" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
	Modeline 	"Mode 15" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace
	Modeline 	"Mode 16" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync 
	Modeline 	"Mode 17" 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync 
	Option "PreferredMode" "Mode 14"
EndSection

If you have a CEC issue with a certain OS, please elevate it in another thread or share the link if already created. My previous comment was about the Petitboot and the Petitboot only has less than 400kB available in the current version, that's not sufficient to add a library for CEC or LIRC.
These users thanked the author tobetter for the post:
CoolGames (Sun Aug 30, 2020 1:47 am)

rod20
Posts: 2
Joined: Sat Aug 29, 2020 9:26 pm
languages_spoken: english
ODROIDs: C2,N2
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by rod20 »

tobetter wrote:
Sat Aug 29, 2020 11:25 pm
rod20 wrote:
Sat Aug 29, 2020 9:43 pm
Hi tobetter, is it possible (or would it be in future releases) to somehow edit the boot order from an OS that already booted?
I used to do that with an older release editing the petitboot.cfg in the uSD card. But now I had to update petitboot because of the fix for last CoreELEC ‘boot.ini’. And newer versions no longer save the config in uSD, so petitboot.cfg is ignored in my tests.
Another question is if you have plans for CEC or LIRC support?
Thanks for your great work.
The Petitboot configuration is now storing in the SPI flash memory itself, no longer store it to 'petitboot.cfg' since......sorry, I don't remember the version but it's been long. You can change the boot order in System configuration. Due to the lack of SPI memory size, LIRC won't be supported and CEC needs more effort to support it. Out of curiosity, what's the model of the brand of your remote?
It's a vizio XRT500.

chris555
Posts: 4
Joined: Fri Aug 28, 2020 4:54 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by chris555 »

I seem to have a compatibility issue with my USB stick - a Samsung Bar Plus 128GB. When I boot with it in one of the rear USB ports Petitboot loads and then after about a second resets. Interestingly if I plug the drive in once Petitboot has loaded it works fine and there is no reset.

It works as expect when connected at boot through the front USB2 port.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

chris555 wrote:
Sun Aug 30, 2020 4:30 am
I seem to have a compatibility issue with my USB stick - a Samsung Bar Plus 128GB. When I boot with it in one of the rear USB ports Petitboot loads and then after about a second resets. Interestingly if I plug the drive in once Petitboot has loaded it works fine and there is no reset.

It works as expect when connected at boot through the front USB2 port.
I use the same models (32GB and 64GB) mostly for OS booting testing but did not have the issue so far. Have you tried another USB 3.0 port?

chris555
Posts: 4
Joined: Fri Aug 28, 2020 4:54 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by chris555 »

tobetter wrote:
Sun Aug 30, 2020 4:36 am
I use the same models (32GB and 64GB) mostly for OS booting testing but did not have the issue so far. Have you tried another USB 3.0 port?
Apologies. I have done more testing and this isn't a Petitboot issue.

I also have a Bluetooth dongle and a dongle for my wireless keyboard connected. If I move them and the USB stick around I can get the USB stick to work but then the others won't work, or will only work on an intermittent basis. I have left it with the USB stick connected to the front port. Performance for what I'm using it for isn't really an issue.

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

Hello,

I have petitboot-20200816 installed in my SPI, 1st-edition ODROID-N2.

Is there any way to get this bootloader to remember its settings over resets? Everytime I power up, the settings revert to their defaults.
I have a eMMC installed if it matters.

I have not been able to find specific documentation, but I have seen some references this should work.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Mon Aug 31, 2020 6:41 am
Hello,

I have petitboot-20200816 installed in my SPI, 1st-edition ODROID-N2.

Is there any way to get this bootloader to remember its settings over resets? Everytime I power up, the settings revert to their defaults.
I have a eMMC installed if it matters.

I have not been able to find specific documentation, but I have seen some references this should work.
Did you change the boot order or settings in "System configuration" ?

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

I can change boot order, autoboot, etc. settings in Configuration screen.

My problem is these changes are gone when the power is turned off.

I tried reinstalling petitboot from scratch (recovery) but this did not resolve my issue.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Mon Aug 31, 2020 10:57 am
I can change boot order, autoboot, etc. settings in Configuration screen.

My problem is these changes are gone when the power is turned off.

I tried reinstalling petitboot from scratch (recovery) but this did not resolve my issue.
It must be stored when you select "OK" after changing the System configuration.
Can you please try again and record the screen how you made the change?

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

I also had the same behavior as @martyg, selected boot order and disabling autostart did not survive power off, did not check this on latest version...

Edit: Checking again with latest Petitboot version from 18.08.2020 everything works as it should.
Last edited by Sholander on Mon Sep 07, 2020 2:30 am, edited 3 times in total.

yuhmuhduh
Posts: 5
Joined: Fri Aug 14, 2020 2:42 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by yuhmuhduh »

yuhmuhduh wrote:
Fri Aug 14, 2020 2:50 am
I'm still unable to get CoreELEC (on uSD) or the Lineage Android v16 (on eMMC) to boot via SPI when loading through petitboot. I've tried it over the past few months on several versions. I used the pb-update from the July version to the latest last night (which worked great) and it's the same thing. For CoreELEC, it'll just load a black screen. I can see the heartbeat blue light going after loading, but nothing on the screen at all. Any ideas?

Like another poster mentioned in this thread, would be easiest if MMC boot defaulted to uSD instead of eMMC...would be simple just to take out and put in the uSD when wanting to boot a different OS, but I think that's another discussion.

4GB N2, CoreELEC 9.2.3 on uSD, LineageOS 16.0 on eMMC. Latest version of petitboot 20200806. Using a 1080p TV.
still not able to get CoreELEC on the uSD to boot from SPI with petitboot 20200816. drops me into a black screen (even with the eMMC with LineageOS 16 removed). any tips or pointers would be appreciated.

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

yuhmuhduh wrote:
Fri Aug 14, 2020 2:50 am
Like another poster mentioned in this thread, would be easiest if MMC boot defaulted to uSD instead of eMMC...would be simple just to take out and put in the uSD when wanting to boot a different OS, but I think that's another discussion.
To reinforce this point, consider my current failure mode:

0. Working system, can dual-boot uSD and eMMC
1. Somehow corrupted eMMC so it doesn't boot (Failed to launch petitboot, dropping to shell; sh: can't access tty; job control tuned off)
2. Now cannot boot uSD in either SPI/MMC boot mode -- Even after switching to MMC and power-cycling I just get a black screen
3. End result - unbootable N2 unless I disconnect the eMMC module

IMHO having the ability to set the uSD card to boot first, no matter what, is essential.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Thu Sep 03, 2020 9:44 am
yuhmuhduh wrote:
Fri Aug 14, 2020 2:50 am
Like another poster mentioned in this thread, would be easiest if MMC boot defaulted to uSD instead of eMMC...would be simple just to take out and put in the uSD when wanting to boot a different OS, but I think that's another discussion.
To reinforce this point, consider my current failure mode:

0. Working system, can dual-boot uSD and eMMC
1. Somehow corrupted eMMC so it doesn't boot (Failed to launch petitboot, dropping to shell; sh: can't access tty; job control tuned off)
2. Now cannot boot uSD in either SPI/MMC boot mode -- Even after switching to MMC and power-cycling I just get a black screen
3. End result - unbootable N2 unless I disconnect the eMMC module

IMHO having the ability to set the uSD card to boot first, no matter what, is essential.
Do you use Hardkernel's genuine eMMC?

The way how you can make boot from uSD instead of eMMC when eMMC is flashed with a certain OS is to remove the boot loader from it. In order to perform this, get into the command shell from the Petitboot while eMMC is connected and run this command.

Code: Select all

dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=1 conv=fsync
Then next boot when the boot select switch is at MMC, uSD will start to boot first. But this won't make eMMC boot itself.

Do you have USB-to-serial debugging board?

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

tobetter wrote:
Thu Sep 03, 2020 9:56 am
Do you use Hardkernel's genuine eMMC?

The way how you can make boot from uSD instead of eMMC when eMMC is flashed with a certain OS is to remove the boot loader from it. In order to perform this, get into the command shell from the Petitboot while eMMC is connected and run this command.

Code: Select all

dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=1 conv=fsync
Then next boot when the boot select switch is at MMC, uSD will start to boot first. But this won't make eMMC boot itself.

Do you have USB-to-serial debugging board?
I purchased my eMMC from AmeriDroid. What is special about the HK version? I'm going to overwrite it anyway...

As I said earlier, impossible to fix eMMC without removing it from the N2 hardware.
I would not need to risk breaking my card if I had the ability to force N2 bootloader to look ay uSD before eMMC, use uSD as rescue disk

I have a serial-USB kit, but never used it on N2 (Works on my other platforms)

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Thu Sep 03, 2020 10:29 am
tobetter wrote:
Thu Sep 03, 2020 9:56 am
Do you use Hardkernel's genuine eMMC?

The way how you can make boot from uSD instead of eMMC when eMMC is flashed with a certain OS is to remove the boot loader from it. In order to perform this, get into the command shell from the Petitboot while eMMC is connected and run this command.

Code: Select all

dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=1 conv=fsync
Then next boot when the boot select switch is at MMC, uSD will start to boot first. But this won't make eMMC boot itself.

Do you have USB-to-serial debugging board?
I purchased my eMMC from AmeriDroid. What is special about the HK version? I'm going to overwrite it anyway...

As I said earlier, impossible to fix eMMC without removing it from the N2 hardware.
I would not need to risk breaking my card if I had the ability to force N2 bootloader to look ay uSD before eMMC, use uSD as rescue disk

I have a serial-USB kit, but never used it on N2 (Works on my other platforms)
Then what's colour of eMMC PCB? I am wondering when eMMC is corrupted, which OS is installed to your eMMC?
Even if you follow the command I posted, it does not break your eMMC. It just removes the eMMC such that CPU won't start from eMMC. S922X won't load the bootloader from SD when eMMC has the bootloader, that's the reason I ask you for removing the bootloader from eMMC then it will start SD card. Also later you can recover the bootloader to eMMC.

There is an alternative way to make SD card boot earlier but you need the USB-to-serial debugging board compatible with ODROID.

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

Just to clarify, the eMMC became "corrupted" because I was messing with it -- Not some hardware error.
I can reproduce this issue at will just by manually tweaking the content of my boot volumes. I just wish petitboot recovered more gracefully.

I do not want to make a habit of disconnecting the eMMC from this board. My eyes are old and this connector is very delicate.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Thu Sep 03, 2020 11:37 am
Just to clarify, the eMMC became "corrupted" because I was messing with it -- Not some hardware error.
I can reproduce this issue at will just by manually tweaking the content of my boot volumes. I just wish petitboot recovered more gracefully.

I do not want to make a habit of disconnecting the eMMC from this board. My eyes are old and this connector is very delicate.
As long as you can boot Linux from SPI or SD card, you won't need to detach the eMMC module from ODROID-N2.
Also, it's a bit hard to determine when the Petitboot crashes. If you can share the files in the "BOOT" partition when the Petitboot is crashed, I can debug it.

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

Let's take a step back so I can make best use of your time.
Understanding these few points would really help me along understanding if my configuration is supported:
I have spent quite a bit of time searching for documentation on these topics but have come up mostly empty.
My apologies in advance if I overlooked an important pointer.

1. Functional documentation. Specifically, how filesystems are scanned and what files are checked during boot.

2. Build process. Only reference I found links to a blank page. Can users build their own petitboot images?

3. Where are settings stored on the target so they survive power cycles? Can users see/touch these persistent configuration files? When and how are uSD or eMMC cards touched/updated?

4. How do I disable PXE boot (This is an exotic configuration and should be OFF by default) Any reason to have networking enabled if I just boot from local drives?

5. I expected to be able to tweak the contents of the boot/ramdisk/firmware command line settings in the Edit tab. I can see characters appended when I type, but no cursor or apparent way to delete. Is this functional?

Once I'm clearer on the above, I am sure I can get to the root cause of my issues with little assistance and provide you with an intelligent bug report if needed.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

martyg wrote:
Fri Sep 04, 2020 2:13 am
Functional documentation. Specifically, how filesystems are scanned and what files are checked during boot.
Petitboot scans the files boot.ini and boot.scr in the root directory or in the /boot directory of each partitions in a storage device and it parse the boot script to get OS boot command.
Where are settings stored on the target so they survive power cycles? Can users see/touch these persistent configuration files? When and how are uSD or eMMC cards touched/updated?
Configurations are stored to SPI flash memory itself, you can get the values with the command fw_printenv | grep petitboot in the Petitboot shell.
How do I disable PXE boot (This is an exotic configuration and should be OFF by default) Any reason to have networking enabled if I just boot from local drives?
PXE boot is not intended to run by default. But it is loaded when the PXE server is discovered by DHCP and DHCP is just enabled, this does not affect boot process or time much.
I expected to be able to tweak the contents of the boot/ramdisk/firmware command line settings in the Edit tab. I can see characters appended when I type, but no cursor or apparent way to delete. Is this functional?
If you need to tweak the contents every boot, you should be better to change it in the boot script.

martyg
Posts: 7
Joined: Wed Aug 26, 2020 10:49 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by martyg »

Summary: ArchLinuxArm boot.ini causes petitboot crash

Setup:
eMMC with working image, bootable through SPI verify system boots without uSD card
Download boot image, (25MB) install on uSD card (gunzip && dd bs=1M)
Insert uSD card in N2 slot. Power cycle to reset (Boot switch set to SPI)

Observed behavior: PB fails to detect any volumes. In particular no eMMC volumes are visible.

Expected behavior: PB should always show all available volumes. If an error occurs, skip over the current volume and scan rest of system
It does not matter is this file or volume is completely corrupt -- The bootloader should never hang like this!

Remove uSD card and observe correct behavior returns

The offending volume on P2 was taken directly from the current ArchLinuxArm boot disk.

User avatar
CoolGames
Posts: 108
Joined: Sun Nov 24, 2019 3:07 am
languages_spoken: english
ODROIDs: Dec 25 N2
Has thanked: 18 times
Been thanked: 14 times
Contact:

CEC alt thread - Re: Petitboot, yet another bootloader based on KEXEC

Post by CoolGames »

I have found CEC is different from EDID and not sure how to explicitly set the modeline for individual consumer televisions.
tobetter wrote:
Sun Aug 30, 2020 12:14 am

If you have a CEC issue with a certain OS, please elevate it in another thread or share the link if already created. My previous comment was about the Petitboot and the Petitboot only has less than 400kB available in the current version, that's not sufficient to add a library for CEC or LIRC.
I have started another thread link for CEC issue which is specific to the Insignia TV I have.

gezmond
Posts: 9
Joined: Sat Jul 04, 2020 4:18 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by gezmond »

Not sure what has happened but after updating to latest coreelec i have lost petitboot. I can boot to android on emmc by selecting emmc. I slide switch to SPI click restart and it still boots to android. Pull plug and boot with SPI selected and it boots to android. Take emmc out, pull plug and it boots directly to coreelec. I have tried update images for PB but nothing happens. This is really frustrating, it seems as though PB has been removed from the system somehow.

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

What happens when you take out eMMC and uSD card, flip the switch to SPI position and then power on your N2?

gezmond
Posts: 9
Joined: Sat Jul 04, 2020 4:18 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by gezmond »

Nothing happens when no card or emmc is available. Just red light no boot

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

gezmond wrote:
Sun Sep 06, 2020 6:02 am
Not sure what has happened but after updating to latest coreelec i have lost petitboot. I can boot to android on emmc by selecting emmc. I slide switch to SPI click restart and it still boots to android. Pull plug and boot with SPI selected and it boots to android. Take emmc out, pull plug and it boots directly to coreelec. I have tried update images for PB but nothing happens. This is really frustrating, it seems as though PB has been removed from the system somehow.
Whenever you change the boot select switch, you must replug the DC power otherwise ODROID-N2 keeps the previous boot selection. Please try and let us know if you can see the Petitboot screen after rebooting.

gezmond
Posts: 9
Joined: Sat Jul 04, 2020 4:18 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by gezmond »

Nothing happens tobetter. I pull the plug and everytime it either just boots straight to uSD (coreelec) or emmc (android) if it is installed. I have to remove the android emmc if i want it to boot into coreelec at all otherwise it always boots into android regardless of what the position of the switch is

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

gezmond wrote:
Sun Sep 06, 2020 4:34 pm
Nothing happens tobetter. I pull the plug and everytime it either just boots straight to uSD (coreelec) or emmc (android) if it is installed. I have to remove the android emmc if i want it to boot into coreelec at all otherwise it always boots into android regardless of what the position of the switch is
In case the Petitboot does not up, it's worth to reinstall the Petitboot with the recovery image. Prepare an SD card and flash the recovery image with Etcher.
https://wiki.odroid.com/odroid-n2/os_im ... ev20200816

IgaBiva
Posts: 115
Joined: Tue May 07, 2019 4:00 pm
languages_spoken: english, deutsch, srpski
ODROIDs: N2
Has thanked: 7 times
Been thanked: 17 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by IgaBiva »

Small tip from my side - when updating SPI memory, remove all USB drives that are attached to N2. Otherwise, update will fail.

I have lost hours before I have realized this.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

IgaBiva wrote:
Mon Sep 07, 2020 3:57 am
Small tip from my side - when updating SPI memory, remove all USB drives that are attached to N2. Otherwise, update will fail.

I have lost hours before I have realized this.
Out of curiosity, which USB devices are connected and which USB ports are being used with your N2?

SirZevo
Posts: 20
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 5 times
Been thanked: 1 time

Re: Petitboot, yet another bootloader based on KEXEC

Post by SirZevo »

Petitboot (dev.20200816)

Petiboot Failed to launch petiboot, dropping to a shell - sh: can't access tty: job control turned off

This is after burning Ubuntu Focal from Armbian for N2 to a SanDisk card and then installing to eMMC with

Code: Select all

sudo armbian-config -> Choosing System -> Install (install boot loader) -> eMMC
Rebooting makes Petiboot fail and the only way to boot the system is by having the switch between petiboot and eMMC to the right (eMMC).

In Petiboot, running pb-update gives error: E: Invalid update info from http://ppa.linuxfactoru.or.kr/images/pe ... dn2/latest. I can't upgrade with the same version by spiboot.img either, so recovery mode seems to be the only option it.

Update
I removed the eMMC, downloaded and burned the dev.20200816 recovery image and rebooted into a perfectly working petiboot. Then switched off the N2, inserted the eMMC and removed the SD. And now I'm back to the error with Petiboot Failed to launch petiboot, dropping to a shell - sh: can't access tty: job control turned off... tobetter, it might be of relevance to ping the folks over at Armbian about this. At least try to reproduce the issue. try to disable low-level messages in Armbian-config -> System when booting the SD before install to eMMC.
Last edited by SirZevo on Tue Sep 15, 2020 11:05 pm, edited 1 time in total.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

SirZevo wrote:
Tue Sep 15, 2020 10:44 pm
Petitboot (dev.20200816)

Petiboot Failed to launch petiboot, dropping to a shell - sh: can't access tty: job control turned off

This is after burning Ubuntu Focal from Armbian for N2 to a SanDisk card and then installing to eMMC with

Code: Select all

sudo armbian-config -> Choosing System -> Install (install boot loader) -> eMMC
Rebooting makes Petiboot fail and the only way to boot the system is by having the switch between petiboot and eMMC to the right (eMMC).

In Petiboot, running pb-update gives error: E: Invalid update info from http://ppa.linuxfactoru.or.kr/images/pe ... dn2/latest. I can't upgrade with the same version by spiboot.img either, so recovery mode seems to be the only option it.

Update
I removed the eMMC, downloaded and burned the dev.20200816 recovery image and rebooting into a perfectly working petiboot. Then switched off the N2, inserted the eMMC and removed the SD. And now I'm back to the error with Petiboot Failed to launch petiboot, dropping to a shell - sh: can't access tty: job control turned off... tobetter, it might be of relevance to ping the folks over at Armbian about this. At least try to reproduce the issue.
Can you share the link or OS image file name you flashed to eMMC?

SirZevo
Posts: 20
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 5 times
Been thanked: 1 time

Re: Petitboot, yet another bootloader based on KEXEC

Post by SirZevo »

Sure, I started with the latest Armbian_20.08.1_Odroidn2_focal_current_5.8.5.img.xz, but after reading about complications with kernel 5.8.5, I'm now using Armbian_20.08_Odroidn2_focal_current_5.7.15. I think I had issues with both of them, but you can start with Armbian_20.08_Odroidn2_focal_current_5.7.15 given it's considered more stable than the other.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

SirZevo wrote:
Tue Sep 15, 2020 11:09 pm
Sure, I started with the latest Armbian_20.08.1_Odroidn2_focal_current_5.8.5.img.xz, but after reading about complications with kernel 5.8.5, I'm now using Armbian_20.08_Odroidn2_focal_current_5.7.15. I think I had issues with both of them, but you can start with Armbian_20.08_Odroidn2_focal_current_5.7.15 given it's considered more stable than the other.
Are the links correct? Image for 5.7.15 is not able to be downloaded and 5.8.5 keeps failing to download.

Code: Select all

wget https://archive.armbian.com/odroidn2/archive/Armbian_20.08_Odroidn2_focal_current_5.7.15.img.xz
--2020-09-15 23:16:21--  https://archive.armbian.com/odroidn2/archive/Armbian_20.08_Odroidn2_focal_current_5.7.15.img.xz
Resolving archive.armbian.com (archive.armbian.com)... 93.103.15.56
Connecting to archive.armbian.com (archive.armbian.com)|93.103.15.56|:443... failed: No route to host.
Can you please share the file boot.scr or boot.ini in your eMMC?

EDIT: I finally have downloaded 5.8 image whilist 5.7 image is not.

EDIT: I am able to boot 5.8 image and not having the error.

SirZevo
Posts: 20
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 5 times
Been thanked: 1 time

Re: Petitboot, yet another bootloader based on KEXEC

Post by SirZevo »

Strange. All the links worked for me. You can find the 5.7 version over at https://archive.armbian.com/odroidn2/archive and then search for Armbian_20.08_Odroidn2_focal_current_5.7.15.img.xz.
boot.ini
(5.41 KiB) Downloaded 13 times
Just to be clear about the procedure. You have burned Armbian 5.8 to a SanDisk card, ran armbian-config -> install to eMMC and then rebooted with SPI option enabled with success?

Update:
Unplugging the eMMC and inserting the SanDisk card I used to install to eMMC make Petiboot work again. So Petiboot is actually not demaged, but something with the eMMC installation breaks Petiboot when eMMC is inserted.
Attachments
boot.scr.tar
boot.scr tared since I can't upload files with .scr extension
(2 KiB) Downloaded 5 times
Last edited by SirZevo on Wed Sep 16, 2020 12:05 am, edited 1 time in total.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

SirZevo wrote:
Tue Sep 15, 2020 11:59 pm
Strange. All the links worked for me. You can find the 5.7 version over at https://archive.armbian.com/odroidn2/archive and then search for Armbian_20.08_Odroidn2_focal_current_5.7.15.img.xz.

boot.ini

Just to be clear about the procedure. You have burned Armbian 5.8 to a SanDisk card, ran armbian-config and install to eMMC and then rebooted with SPI option enabled with success?

Update:
Unplugging the eMMC and inserting the SanDisk card I used to install to eMMC make Petiboot work again. So Petiboot is actually not demaged, but something with the eMMC installation breaks Petiboot when eMMC is inserted.
Don't know, new link works now.
I am a bit confused, you rurned 5.8 to SD card and booted from SD card...right? Then what I supposed to do with armbian-config? Do you copy whole OS image from SD to eMMC or what?

SirZevo
Posts: 20
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 5 times
Been thanked: 1 time

Re: Petitboot, yet another bootloader based on KEXEC

Post by SirZevo »

Yes, I booted from the SD card. Then run armbian-config and select "System" -> "Install Install to/update boot loader" -> "Install/Update the booloader on eMMC" -> eMMC -> Follow instructions and reboot.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

SirZevo wrote:
Wed Sep 16, 2020 12:07 am
Yes, I booted from the SD card. Then run armbian-config and select "System" -> "Install Install to/update boot loader" -> "Install/Update the booloader on eMMC" -> eMMC -> Follow instructions and reboot.
Sorry, I am not familiar with Armbian. I don't get why installation the boot loader is necessary if you are going to use the Petitboot and why not directly burn the Armbian OS to eMMC? I have tested Armbian image with eMMC only.

SirZevo
Posts: 20
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 5 times
Been thanked: 1 time

Re: Petitboot, yet another bootloader based on KEXEC

Post by SirZevo »

I see, so updating the boot loader in the process of the eMMC install in the script is not compatible with Petiboot. I've burned Armbian to eMMC directly earlier, but I've had some issues. Hence I've started to use Armbian's install to eMMC script instead. From your experience, should one write zeroes to the whole eMMC before re-installing or just the boot loader (0 to 1024)? And which parameters do you recoomend using with dd? I need it to be reliable to prevent issues with new builds.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

SirZevo wrote:
Wed Sep 16, 2020 1:30 am
I see, so updating the boot loader in the process of the eMMC install in the script is not compatible with Petiboot. I've burned Armbian to eMMC directly earlier, but I've had some issues. Hence I've started to use Armbian's install to eMMC script instead. From your experience, should one write zeroes to the whole eMMC before re-installing or just the boot loader (0 to 1024)? And which parameters do you recoomend using with dd? I need it to be reliable to prevent issues with new builds.
I don't have an issue to flash any OS to eMMC using dd or Etcher without writing zeros before flashing. But it's my experience, writing zeros would be fine if your time permits. So now you do not have an issue to install Armbian to eMMC and boot from the Petitboot? Still I have not idea what Armbian script does, not interesting at all, the Petitboot is intended to boot from OS that can be flashed and booted to/from a memory card. If you encounter the problem once you flash OS image to eMMC and not booting by the Petitboot, please let me know.

yuhmuhduh
Posts: 5
Joined: Fri Aug 14, 2020 2:42 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by yuhmuhduh »

yuhmuhduh wrote:
Thu Sep 03, 2020 2:49 am
yuhmuhduh wrote:
Fri Aug 14, 2020 2:50 am
I'm still unable to get CoreELEC (on uSD) or the Lineage Android v16 (on eMMC) to boot via SPI when loading through petitboot. I've tried it over the past few months on several versions. I used the pb-update from the July version to the latest last night (which worked great) and it's the same thing. For CoreELEC, it'll just load a black screen. I can see the heartbeat blue light going after loading, but nothing on the screen at all. Any ideas?

Like another poster mentioned in this thread, would be easiest if MMC boot defaulted to uSD instead of eMMC...would be simple just to take out and put in the uSD when wanting to boot a different OS, but I think that's another discussion.

4GB N2, CoreELEC 9.2.3 on uSD, LineageOS 16.0 on eMMC. Latest version of petitboot 20200806. Using a 1080p TV.
still not able to get CoreELEC on the uSD to boot from SPI with petitboot 20200816. drops me into a black screen (even with the eMMC with LineageOS 16 removed). any tips or pointers would be appreciated.
last shot in checking on this. still on 20200816. no eMMC installed. latest version of CoreELEC (9.2.4.2) on eMMC still goes into a black screen after booting from SPI/petitboot. black screen on tv, solid red light, and blue heart beat light flashing.

will probably end up just installing android on another uSD and swap them out as needed.

thanks, tobetter. this is a cool project, and i'm glad it's around for the N2.
These users thanked the author yuhmuhduh for the post:
tobetter (Wed Sep 23, 2020 6:43 am)

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

yuhmuhduh wrote:
Wed Sep 23, 2020 2:37 am
yuhmuhduh wrote:
Thu Sep 03, 2020 2:49 am
yuhmuhduh wrote:
Fri Aug 14, 2020 2:50 am
I'm still unable to get CoreELEC (on uSD) or the Lineage Android v16 (on eMMC) to boot via SPI when loading through petitboot. I've tried it over the past few months on several versions. I used the pb-update from the July version to the latest last night (which worked great) and it's the same thing. For CoreELEC, it'll just load a black screen. I can see the heartbeat blue light going after loading, but nothing on the screen at all. Any ideas?

Like another poster mentioned in this thread, would be easiest if MMC boot defaulted to uSD instead of eMMC...would be simple just to take out and put in the uSD when wanting to boot a different OS, but I think that's another discussion.

4GB N2, CoreELEC 9.2.3 on uSD, LineageOS 16.0 on eMMC. Latest version of petitboot 20200806. Using a 1080p TV.
still not able to get CoreELEC on the uSD to boot from SPI with petitboot 20200816. drops me into a black screen (even with the eMMC with LineageOS 16 removed). any tips or pointers would be appreciated.
last shot in checking on this. still on 20200816. no eMMC installed. latest version of CoreELEC (9.2.4.2) on eMMC still goes into a black screen after booting from SPI/petitboot. black screen on tv, solid red light, and blue heart beat light flashing.

will probably end up just installing android on another uSD and swap them out as needed.

thanks, tobetter. this is a cool project, and i'm glad it's around for the N2.
Can you let me know the model of yout TV?
If the blue LED is heartbeating, then CoreELEC is up and running...so do you hear any sound effect when you click a button?
Would you be able to sshing to CE and run cat /proc/cmdline and share the output with me?
These users thanked the author tobetter for the post:
yuhmuhduh (Wed Sep 23, 2020 11:51 pm)

yuhmuhduh
Posts: 5
Joined: Fri Aug 14, 2020 2:42 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by yuhmuhduh »

tobetter wrote:
Wed Sep 23, 2020 6:47 am
Can you let me know the model of yout TV?
If the blue LED is heartbeating, then CoreELEC is up and running...so do you hear any sound effect when you click a button?
Would you be able to sshing to CE and run cat /proc/cmdline and share the output with me?
thanks for the follow up. the TV is the LG 39LN5300 (from ~2013).

CoreELEC:~ # cat /proc/cmdline
BOOT_IMAGE=kernel.img boot=UUID=2911-4504 disk=UUID=d64f1eca-7a63-4904-9030-3446e096b23b console=ttyS0,115200 console=tty0 no_console_suspend remotewakeup=0xfa053e01 decode_type=0 remotewakeupmask=0xffffffff hdmimode=1080p60hz logo=osd0,loaded,0x3d800000 vout=1080p60hz,enable frac_rate_policy=0 native_4k_gui=0 quiet systemd.show_status=auto

when booting from SPI into coreelec and waiting a minute, i'm not able to hear any sounds when moving the selector in coreelec (or pressing back, selecting items, etc).

thanks again for the help.

DragonQ
Posts: 1
Joined: Fri Oct 02, 2020 10:35 pm
languages_spoken: english
ODROIDs: ODROID-N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by DragonQ »

Hi all, I just received a brand new ODROID-N2+ but it had a very old petitboot version. I updated it by following the procedure here, and it seemed to update, but since then it's just been stuck at the pink HARDKERNEL startup screen for about 15 minutes. Should I pull the power and restart it?

User avatar
istanbulls
Posts: 297
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID-N2, ODROID C4
Location: Istanbul-Turkey
Has thanked: 189 times
Been thanked: 39 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by istanbulls »

DragonQ wrote:
Fri Oct 02, 2020 11:10 pm
Hi all, I just received a brand new ODROID-N2+ but it had a very old petitboot version. I updated it by following the procedure here, and it seemed to update, but since then it's just been stuck at the pink HARDKERNEL startup screen for about 15 minutes. Should I pull the power and restart it?
yes

stmmuc
Posts: 1
Joined: Wed Oct 14, 2020 1:56 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by stmmuc »

yuhmuhduh wrote:
Thu Sep 03, 2020 2:49 am
still not able to get CoreELEC on the uSD to boot from SPI with petitboot 20200816. drops me into a black screen (even with the eMMC with LineageOS 16 removed). any tips or pointers would be appreciated.
Had the same problem trying to boot CoreELEC and EmuELEC from eMMC on my TV. Only got a black screen from both. CoreELEC was booting normally with the switch set to eMMC. But I noticed that the keyboard was working. So I thougth at least some part of the Kernel was loaded. To test the theory I configured CoreELEC to turn off the blue heartbeat LED. And when booting via petitboot I again got a black screen, but the LED turned off. So i figured the problem must have something to do with the video-output. I connected the N2+ to my computer monitor and both CoreELEC and EmuELEC were working just fine.

So I have not quite figured out the exact reason for the problem, but at least it is a start. Hope that helps.

thering1975
Posts: 81
Joined: Sat Apr 18, 2020 12:39 am
languages_spoken: english
Has thanked: 13 times
Been thanked: 12 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by thering1975 »

Just a question reference the black screen

Running latest Petitboot on both of my N2's. However on the N2+ if i reboot from within android, it will load the petitboot menu okay. If i select CoreElec that boots okay. However if i select Android again it goes to boot, then i get a black screen, and no signal input from the TV. The LED's are blinking but no output. I have to pull the power from the device and plug back in. From Cold boot if i select Android it boots fine. However if i reboot from within Android, i get the black screen again.

Firstly this only happens on the N2+ NOT the older N2

Have tested both Secuflags latest AOSP and Voodiks latest ATV 16 Lineage OS, both do the same thing with the loss of signal

Setup of N2 and N2+ teh same and Both set to 2160p 60fps

N2+ is on the first lower overclock, tried both ondemand and performance scehdulers.

thering1975
Posts: 81
Joined: Sat Apr 18, 2020 12:39 am
languages_spoken: english
Has thanked: 13 times
Been thanked: 12 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by thering1975 »

As requested in Android Thread

Find attached output as requested

You will see various incidents of the signal loss, however i let it go longer and it did come back

https://youtu.be/iVXhnG0dnVo

For info it does this only on the N2+ and on both Lineage Atv and Secuflag Standard AOSP. It does not however do it on the older N2

Update

For info i put the SDcard back in for dual boot mode and it now hangs on No Signal and it does not boot Android after a short wait like the video, i will get a second screengrab to see if it is any different from the first attachment

Same output in cmdline. as before.
Attachments
20201014_153338.jpg
20201014_153338.jpg (76.83 KiB) Viewed 534 times

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

20201020

Update version from 20201020 is uploaded. The firmware can be updated in the Petitboot itself by running the command 'pb-update', or you can download firmware file from spiboot-20201020.img and copy it to your SD card as spiboot.img.

What's improved:
  • HDMI black issue is improved for certain display devices, internal bug of the Petitboot is fixed.
  • Boot failure when a certain USB storage is attached is improved.
  • SD card boot failure is fixed after rebooting on ODROID-N2Plus.
In case the Petitboot does not start after updating?
A couple of users had experienced that their ODROID-N2/Plus does not boot after updating which seems SPI flash update is failed. In such case, please do use the recovery image in order to complete reflash the SPI flash memory. As long as the SPI flash memory defects, the Petitboot can be installed.
For detail, please refer to the link - https://wiki.odroid.com/odroid-n2/os_im ... overy_mode

Let me share the download count of the previous version 20200816, it hits almost 1000 again. Thanks a lot. :)
Petitboot_20200816.png
Petitboot_20200816.png (101.57 KiB) Viewed 326 times
These users thanked the author tobetter for the post (total 8):
Rmiino (Fri Oct 23, 2020 7:41 am) • alphahere (Fri Oct 23, 2020 12:43 pm) • odroid (Fri Oct 23, 2020 2:21 pm) • minoccio (Fri Oct 23, 2020 6:28 pm) • istanbulls (Fri Oct 23, 2020 7:47 pm) • thering1975 (Sun Oct 25, 2020 8:40 pm) • jgmdev (Mon Oct 26, 2020 4:38 am) • superpowter77 (Mon Oct 26, 2020 8:41 am)

thering1975
Posts: 81
Joined: Sat Apr 18, 2020 12:39 am
languages_spoken: english
Has thanked: 13 times
Been thanked: 12 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by thering1975 »

Sheel update went smooth, tried several reboots and so far the black screen issue etc has been resolved, so many thanks for the update.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

thering1975 wrote:
Sun Oct 25, 2020 10:55 pm
Sheel update went smooth, tried several reboots and so far the black screen issue etc has been resolved, so many thanks for the update.
Glad to hear the black screen issue is resolved for you. I also appreciate to all who tested the previous versions with valuable feedbacks, that helps me to improve the features and make it more reliable. :)
These users thanked the author tobetter for the post (total 2):
jgmdev (Mon Oct 26, 2020 4:38 am) • thering1975 (Tue Oct 27, 2020 1:56 am)

Post Reply

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 1 guest