Petitboot, yet another bootloader based on KEXEC

tobetter · Post by **tobetter** » Tue Jun 30, 2020 12:16 pm

@Sholander, I've tested the recent Android version and I am also having an issue to boot Android from the Petitboot. This is because of supporting DTB overlay on Android which is not acknowledged by the Petitboot yet. I was working on this, but not ready to release yet. Please let me have a several days to finish up. Sorry about that.

Sholander · Post by **Sholander** » Tue Jun 30, 2020 5:56 pm

tobetter wrote: ↑
Tue Jun 30, 2020 12:16 pm
@Sholander, I've tested the recent Android version and I am also having an issue to boot Android from the Petitboot. This is because of supporting DTB overlay on Android which is not acknowledged by the Petitboot yet. I was working on this, but not ready to release yet. Please let me have a several days to finish up. Sorry about that.

No problem, and no hurry at my side. I'm going on a 3 weeks vacation and will not use my N2 until I return home

Just wandered if it only happens to me, since nobody else reported it...

loznic89 · Post by **loznic89** » Thu Jul 09, 2020 5:03 pm

I still use version 05/07/19 of petitboot and everything continues to work even with new images. thnks for petitboot

gezmond · Post by **gezmond** » Thu Jul 09, 2020 8:18 pm

Today I updated to Android to 64bit on the EMMC module and I also flashed the up to date Petitboot image via the Coreelec SD card to the N2. When the N2 is switched to EMMC Android boots up fine. When switched to SPI petitboot loads only after the plug has been pulled and I can boot Coreelec from SD card fine but when I select Android the N2 appears to boot but my TV says there is no signal? The lights on the N2 appear to suggest that Android is running though. The only way I can get Android to run is by pulling the plug and then switching to EMMC and vice versa for Coreelec. Is this a known issue?

tobetter · Post by **tobetter** » Thu Jul 09, 2020 8:25 pm

gezmond wrote: ↑
Thu Jul 09, 2020 8:18 pm
Today I updated to Android to 64bit on the EMMC module and I also flashed the up to date Petitboot image via the Coreelec SD card to the N2. When the N2 is switched to EMMC Android boots up fine. When switched to SPI petitboot loads only after the plug has been pulled and I can boot Coreelec from SD card fine but when I select Android the N2 appears to boot but my TV says there is no signal? The lights on the N2 appear to suggest that Android is running though. The only way I can get Android to run is by pulling the plug and then switching to EMMC and vice versa for Coreelec. Is this a known issue?

This is known issue with the very last Android release and I am trying to fix the Petitboot issue. Please let me have several days to figure out.

tobetter · Post by **tobetter** » Thu Jul 16, 2020 5:36 am

20200715

Please welcome new version of the Petitboot, It's been long to have this update since the last Petitboot is failed to boot the recent version of Android and appreciate to the Petitboot users to wait for this version. In order to update, you can download the update firmware spiboot-20200715.img and copy it to your uSD as spiboot.img as usual. Or you can also update the latest version using the script pb-update in the Petitboot itself, this script will update the SPI flash memory after downloading the firmware file through the network.

What's improved:

Android/LineageOS booting failure is fixed
The problem was that the Petitboot was not able to handle the device tree overlay which is supporting since Android 20200618. This issue has been reported by a couple of users thankfully and now the Petitboot can apply the distributed device tree overlays.

Due to the lack of space, internal firmware is changed a lot
No comment...

Supporting ODROID-N2Plus
ODROID-N2Plus is new version of ODROID-N2 and it also has the SPI flash memory. Using the same firmware update, ODROID-N2 and ODROID-N2Plus can be supported.

Known issues:
Your uSD would not be recognizable if you reboot from the OS after booting from the Petitboot. This is new issue that discovered once the Petitboot and HK stock Linux kernel is updated with the latest BSP that supported ODROID-C4 and ODROID-N2Plus. The fix would be applied to the OS running, not the Petitboot, the fix is being prepared to be released.

Please try and share your experiences.

: Screenshot from 2020-07-16 05-36-02.png (202.27 KiB) Viewed 3819 times

rooted · Post by **rooted** » Thu Jul 16, 2020 5:42 am

I can't leave a thanks on Tapatalk any longer, so I will just say it. Thank you

tobetter · Post by **tobetter** » Thu Jul 16, 2020 5:55 am

rooted wrote: ↑
Thu Jul 16, 2020 5:42 am
I can't leave a thanks on Tapatalk any longer, so I will just say it. Thank you

Thanks...and sleepy...

CoolGames · Post by **CoolGames** » Thu Jul 16, 2020 7:03 am

tobetter wrote: ↑
Thu Jul 16, 2020 5:55 am

rooted wrote: ↑
Thu Jul 16, 2020 5:42 am
I can't leave a thanks on Tapatalk any longer, so I will just say it. Thank you
Thanks...and sleepy...

Large thanks for effort getting things working and go ahead and rest.

I did the

Code: Select all

pb-update

to 20200715 or what ever.

Code: Select all

leetdavy@cooldroidn2:~$ uname -a
Linux cooldroidn2 5.7.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.7.8-202007151852~focal (2020-07-15) aarch64 aarch64 aarch64 GNU/Linux
leetdavy@cooldroidn2:~$ aplay -l
aplay: device_list:274: no soundcards found...

: Coming and going - Getting used to the beta testing process.; Lost after upgrade - Screenshot at 2020-07-15 17-00-16.png (43.84 KiB) Viewed 3814 times

Petitboot Odroid N2 froze Odroid Ubuntu 20.04 netboot install on eMMC with SPI switch so went back to switch eMMC and update / upgrade and sound is gone but not any rush for you after all else you have been doing.

mad_ady · Post by **mad_ady** » Thu Jul 16, 2020 10:45 am

The lack of soundcard is due to kernel 5.7, not petitboot, as far as I know.

tobetter · Post by **tobetter** » Thu Jul 16, 2020 3:04 pm

@CoolGames, the sound issue is not relative to the Petitboot at all and just found that the problem occurs once Linux kernel v5.7.6 is merged. So I am building the Linux package with v5.7.6 with N2Plus patches and 5.7.8 packages are dropped from my repository server. Sorry about the problem.

CoolGames · Post by **CoolGames** » Fri Jul 17, 2020 7:40 am

tobetter wrote: ↑
Thu Jul 16, 2020 3:04 pm
@CoolGames, the sound issue is not relative to the Petitboot at all and just found that the problem occurs once Linux kernel v5.7.6 is merged. So I am building the Linux package with v5.7.6 with N2Plus patches and 5.7.8 packages are dropped from my repository server. Sorry about the problem.

I knew the audio issue was not due to upgrade but was revealed after the upgrade.
Again, thanks for rapid response.
As I keep saying...
After 7 months of increased performance and continuous testing I find my birthday gift of Odroid N2 a dream machine.
The Odroid N2Plus is icing and candles on the cake !
It maybe next purchase when needing another workhorse !

: Odroid N2Plus - Next generation with speedier CPU than current !; N2pluscoolingfanxh.png (192.87 KiB) Viewed 3765 times

Lee

jusue · Post by **jusue** » Sat Jul 18, 2020 2:56 am

Hi,
the link for new petitboot does not work..

Neither the script runs.

Could you fix or upload it again?

Thanks for your great job

tobetter · Post by **tobetter** » Sat Jul 18, 2020 6:39 am

jusue wrote: ↑
Sat Jul 18, 2020 2:56 am
Hi,
the link for new petitboot does not work..
Neither the script runs.

Could you fix or upload it again?

Thanks for your great job

Sorry, looks like my server is down for some reason in the last 6 hours. Instead, you can download the latest image from the link. Copy the file to the first partition of your SD card as 'spiboot.img' and boot after ensuring the boot select switch is placed at "SPI".
https://drive.google.com/file/d/1Yfi42g ... sp=sharing

istanbulls · Post by **istanbulls** » Sat Jul 18, 2020 6:44 am

"http://ppa.linuxfactory.or.kr/dists/focal/InRelease" doesn't work, I think it's the same problem.

tobetter · Post by **tobetter** » Sat Jul 18, 2020 6:56 am

istanbulls wrote: ↑
Sat Jul 18, 2020 6:44 am
"http://ppa.linuxfactory.or.kr/dists/focal/InRelease" doesn't work, I think it's the same problem.

Yes, looks like 'ppa.linuxfactory.or.kr' is down.

istanbulls · Post by **istanbulls** » Sat Jul 18, 2020 7:19 am

With the new version, I cannot change the petitboot screen resolution.
I want to make 720p or 560p but it doesn't.
Is this a known issue?

Code: Select all

# spimmc.sh
# fw_setenv hdmimode 720p60hz

tobetter · Post by **tobetter** » Sat Jul 18, 2020 7:48 am

istanbulls wrote: ↑
Sat Jul 18, 2020 7:19 am
With the new version, I cannot change the petitboot screen resolution.
I want to make 720p or 560p but it doesn't.
Is this a known issue?
Code: Select all
# spimmc.sh
# fw_setenv hdmimode 720p60hz

Indeed, my bad in the latest.

Alternatively, please create a file petitboot.cfg with this in the first partition of your SD card.

Code: Select all

[u-boot]
hdmimode=720p60hz

istanbulls · Post by **istanbulls** » Sat Jul 18, 2020 7:27 pm

tobetter wrote: ↑
Sat Jul 18, 2020 7:48 am
istanbulls wrote: ↑
Sat Jul 18, 2020 7:19 am
With the new version, I cannot change the petitboot screen resolution.
I want to make 720p or 560p but it doesn't.
Is this a known issue?
Code: Select all
# spimmc.sh
# fw_setenv hdmimode 720p60hz
Indeed, my bad in the latest.
Alternatively, please create a file petitboot.cfg with this in the first partition of your SD card.
Code: Select all
[u-boot]
hdmimode=720p60hz

This doesn't work, but I'm not in a hurry. Other important problems should be your priority.

loznic89 · Post by **loznic89** » Sun Jul 19, 2020 1:10 am

tobetter wrote: ↑
Sat Jul 18, 2020 6:39 am

jusue wrote: ↑
Sat Jul 18, 2020 2:56 am
Hi,
the link for new petitboot does not work..
Neither the script runs.

Could you fix or upload it again?

Thanks for your great job
Sorry, looks like my server is down for some reason in the last 6 hours. Instead, you can download the latest image from the link. Copy the file to the first partition of your SD card as 'spiboot.img' and boot after ensuring the boot select switch is placed at "SPI".
https://drive.google.com/file/d/1Yfi42g ... sp=sharing

hi, i have petitboot 201911 - rc2. Any problem to update this latest version? thanks

loznic89 · Post by **loznic89** » Sun Jul 19, 2020 3:05 am

tobetter wrote: ↑
Thu Jul 16, 2020 5:36 am
20200715

Please welcome new version of the Petitboot, It's been long to have this update since the last Petitboot is failed to boot the recent version of Android and appreciate to the Petitboot users to wait for this version. In order to update, you can download the update firmware spiboot-20200715.img and copy it to your uSD as spiboot.img as usual. Or you can also update the latest version using the script pb-update in the Petitboot itself, this script will update the SPI flash memory after downloading the firmware file through the network.

What's improved:

Android/LineageOS booting failure is fixed
The problem was that the Petitboot was not able to handle the device tree overlay which is supporting since Android 20200618. This issue has been reported by a couple of users thankfully and now the Petitboot can apply the distributed device tree overlays.

Due to the lack of space, internal firmware is changed a lot
No comment...

Supporting ODROID-N2Plus
ODROID-N2Plus is new version of ODROID-N2 and it also has the SPI flash memory. Using the same firmware update, ODROID-N2 and ODROID-N2Plus can be supported.

Known issues:
Your uSD would not be recognizable if you reboot from the OS after booting from the Petitboot. This is new issue that discovered once the Petitboot and HK stock Linux kernel is updated with the latest BSP that supported ODROID-C4 and ODROID-N2Plus. The fix would be applied to the OS running, not the Petitboot, the fix is being prepared to be released.

Please try and share your experiences.

Screenshot from 2020-07-16 05-36-02.png

working good with last images android, only IR remote hardkernel not working. thanks I will continue enjoying n2

edit: when reboot n2 dont appear lineage OS in petitboot installed on sd card. android pie on emmc its working in petitboot after reboot

jusue · Post by **jusue** » Sun Jul 19, 2020 7:50 am

I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated

tobetter · Post by **tobetter** » Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated

Are you running the Petitboot 20200715?

jusue · Post by **jusue** » Sun Jul 19, 2020 6:03 pm

tobetter wrote: ↑
Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated
Are you running the Petitboot 20200715?

Yes, the last one that you share from goole drive...

tobetter · Post by **tobetter** » Mon Jul 20, 2020 6:31 pm

jusue wrote: ↑
Sun Jul 19, 2020 6:03 pm

tobetter wrote: ↑
Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated
Are you running the Petitboot 20200715?
Yes, the last one that you share from goole drive...

My server is restored from the hardware problem, please do run pb-update in the command line of the Petitboot and try again.

jusue · Post by **jusue** » Tue Jul 21, 2020 8:26 am

tobetter wrote: ↑
Mon Jul 20, 2020 6:31 pm

jusue wrote: ↑
Sun Jul 19, 2020 6:03 pm

tobetter wrote: ↑
Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated
Are you running the Petitboot 20200715?
Yes, the last one that you share from goole drive...
My server is restored from the hardware problem, please do run pb-update in the command line of the Petitboot and try again.

Unfortunately, re-updating with the script did not fix the problem.
Testing with EmuELEC let me boot correctly, but after a reboot micro sd does not appear in the petitboot menu.

tobetter · Post by **tobetter** » Tue Jul 21, 2020 9:22 am

jusue wrote: ↑
Tue Jul 21, 2020 8:26 am

tobetter wrote: ↑
Mon Jul 20, 2020 6:31 pm

jusue wrote: ↑
Sun Jul 19, 2020 6:03 pm

tobetter wrote: ↑
Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated
Are you running the Petitboot 20200715?
Yes, the last one that you share from goole drive...
My server is restored from the hardware problem, please do run pb-update in the command line of the Petitboot and try again.
Unfortunately, re-updating with the script did not fix the problem.
Testing with EmuELEC let me boot correctly, but after a reboot micro sd does not appear in the petitboot menu.

After updating, still Android does not boot yet? What's the resolution of your TV? Hope it's not 4K. For the issue of SD after rebooting, it's known issue. Some OS needs an update and some OS requires to fix on the Petitboot, I am sorting out this. By the time, if you EmuELEC is sitting on SD, I recommend to attach to USB port using memory card reader.

gezmond · Post by **gezmond** » Tue Jul 21, 2020 9:08 pm

Thanks, i can boot into emmc android again which is great. Looking forward to the fix so that uSD is recognised after a reboot

tobetter · Post by **tobetter** » Tue Jul 21, 2020 9:21 pm

gezmond wrote: ↑
Tue Jul 21, 2020 9:08 pm
Thanks, i can boot into emmc android again which is great. Looking forward to the fix so that uSD is recognised after a reboot

Glad to know your Android is back, thank your for update. What OS do you have in your SD card? If it's not Android and you are not having a problem to attach it to USB port using a memory card reader, I believe it will work.

gezmond · Post by **gezmond** » Tue Jul 21, 2020 10:03 pm

Coreelec is on the uSD, i don't have a usb memory card reader so will have to wait for the fix

jusue · Post by **jusue** » Tue Jul 21, 2020 11:40 pm

tobetter wrote: ↑
Tue Jul 21, 2020 9:22 am

jusue wrote: ↑
Tue Jul 21, 2020 8:26 am

tobetter wrote: ↑
Mon Jul 20, 2020 6:31 pm

jusue wrote: ↑
Sun Jul 19, 2020 6:03 pm

tobetter wrote: ↑
Sun Jul 19, 2020 8:55 am

jusue wrote: ↑
Sun Jul 19, 2020 7:50 am
I am also having issues:

When power on the N2 with petitboot, if I select Android in sd card, the HK logo freeze and android doest not start.

If I choose coreelec it boots correctly, but after rebooting, Android in sd card does not appear, just COREELEC in emmc is an available option.

Only when the emmc is removed, I can run Android. When it happens, my Samsung tv full hd shows "not compatible mode". I have to launch Android in other monitor (also 1920x1080), and then "force" this resolution. After that, I can boot Android in my tv.

Any ideas to solve my launching issues would be appreciated
Are you running the Petitboot 20200715?
Yes, the last one that you share from goole drive...
My server is restored from the hardware problem, please do run pb-update in the command line of the Petitboot and try again.
Unfortunately, re-updating with the script did not fix the problem.
Testing with EmuELEC let me boot correctly, but after a reboot micro sd does not appear in the petitboot menu.
After updating, still Android does not boot yet? What's the resolution of your TV? Hope it's not 4K. For the issue of SD after rebooting, it's known issue. Some OS needs an update and some OS requires to fix on the Petitboot, I am sorting out this. By the time, if you EmuELEC is sitting on SD, I recommend to attach to USB port using memory card reader.

Thanks, but not.
With petitboot, if emmc is inserted Android does not boot from sd card. Only if emmc is removed I can boot Android directly.
My tv is full hd, but I have to run Android in my pc monitor (also full hd) and then force there the 1920x1080p resolution.

tobetter · Post by **tobetter** » Tue Jul 21, 2020 11:51 pm

jusue wrote: ↑
Tue Jul 21, 2020 11:40 pm

tobetter wrote: ↑
Tue Jul 21, 2020 9:22 am
After updating, still Android does not boot yet? What's the resolution of your TV? Hope it's not 4K. For the issue of SD after rebooting, it's known issue. Some OS needs an update and some OS requires to fix on the Petitboot, I am sorting out this. By the time, if you EmuELEC is sitting on SD, I recommend to attach to USB port using memory card reader.
Thanks, but not.
With petitboot, if emmc is inserted Android does not boot from sd card. Only if emmc is removed I can boot Android directly.
My tv is full hd, but I have to run Android in my pc monitor (also full hd) and then force there the 1920x1080p resolution.

Can you let me know the version of CoreELEC and Android?
For your SD card, do you see EmuELEC in the boot menu if you reinsert the memory card after reboot?

jusue · Post by **jusue** » Wed Jul 22, 2020 3:08 am

Sure, coreelec in emmc is last stable 9.2.3, and Android in sd is the last one published in July.

I am pretty sure that emuelec does not appear when it is reinserted after reboot, but I will check again when I arrive home

tobetter · Post by **tobetter** » Wed Jul 22, 2020 5:05 am

20200721

Update version from 20200715 is uploaded, this version fixes the minor issues reported and improved to prevent the SD card issue after rebooting. In order to update, you can download the update firmware spiboot-20200721.img and copy it to your uSD as spiboot.img as usual. Or you can also update the latest version using the script pb-update in the Petitboot itself, this script will update the SPI flash memory after downloading the firmware file through the network.

What's improved:

Custom display setting for the Petitboot is fixed.
1080P is the default resolution to draw the Petitboot menus. If your display does not support 1080P or want to change the resolution, you can create a file petitboot.cfg in the uSD card. The Petitboot will read it and apply the resolution in it. For example, if you like to have low resolution and annoying the small characters with 1080P, put this to 'petitboot.cfg'. For example, your display is a monitor, you used to change the value of 'voutmode' to 'dvi' in the boot.ini:

Code: Select all

[u-boot]
hdmimode=480p60hz
voutmode=dvi

OS in uSD is not showing to the Petitboot after rebooting.
Due to the limitation of SD card compatibility, this won't be fixed for all uSD of different vendors. But this version improved a bit and it's worth to try if you had the issue with the previous version 20200715.

Thanks...

alpe · Post by **alpe** » Wed Jul 22, 2020 9:45 am

tobetter wrote: ↑
Wed Jul 22, 2020 5:05 am
Due to the limitation of SD card compatibility, this won't be fixed for all uSD of different vendors. But this version improved a bit and it's worth to try if you had the issue with the previous version 20200715.

Works on my Samsung EVO+ 32gb.

It's a known issue that the option to prevent writes to disk don't stick?

tobetter · Post by **tobetter** » Wed Jul 22, 2020 12:03 pm

alpe wrote: ↑
Wed Jul 22, 2020 9:45 am
It's a known issue that the option to prevent writes to disk don't stick?

Would you please share more what issue is this?

alpe · Post by **alpe** » Wed Jul 22, 2020 7:59 pm

tobetter wrote: ↑
Wed Jul 22, 2020 12:03 pm

alpe wrote: ↑
Wed Jul 22, 2020 9:45 am
It's a known issue that the option to prevent writes to disk don't stick?
Would you please share more what issue is this?

1) Go to "System configuration".
2) On "Disk R/W" select "Prevent all writes to disk".
3) Click "OK" to save.
4) Reboot.
5) Go to "System configuration" to check the option. "Allow bootloader scripts to modify disks" is checked instead of "Prevent all writes to disk".

tobetter · Post by **tobetter** » Wed Jul 22, 2020 8:20 pm

alpe wrote: ↑
Wed Jul 22, 2020 7:59 pm

tobetter wrote: ↑
Wed Jul 22, 2020 12:03 pm

alpe wrote: ↑
Wed Jul 22, 2020 9:45 am
It's a known issue that the option to prevent writes to disk don't stick?
Would you please share more what issue is this?
1) Go to "System configuration".
2) On "Disk R/W" select "Prevent all writes to disk".
3) Click "OK" to save.
4) Reboot.
5) Go to "System configuration" to check the option. "Allow bootloader scripts to modify disks" is checked instead of "Prevent all writes to disk".

Ah, good point. It's a bug that has not been removed for the deprecated feature that stores the configuration to uSD when I didn't find out the solution to access SPI flash memory. Basically, the Petitboot won't change anything on the file system and the partitions are mounted as read-only regardless of the option. Do you think this is a serious or critical issue?

alpe · Post by **alpe** » Wed Jul 22, 2020 8:26 pm

tobetter wrote: ↑
Wed Jul 22, 2020 8:20 pm
Do you think this is a serious or critical issue?

No, not at all. Thanks for the clarification.

thering1975 · Post by **thering1975** » Fri Jul 24, 2020 9:09 pm

N2 original - Updated to the latest version, and both Android on EMMC and CoreElec on SD card show in the menu. However Android shows the bootscreen and once its finished loading the screen is just Black (signal being sent but no image) Same with Coreelec, however i see no boot screen, again signal is there but it is just a black screen. This is on the latest version of coreelec, voodiks 17.1 android and latest petitboot

Edit - Coreelec stayed on blackscreen from pressing select in the option menu for about 5 minutes, and then the coreelec displayed and opened up after 5minutes, will try that with Android
Edit 2 - repeated CoreElec test and the same thing happens, select entry, black screen for 5 minutes and then it appears at CE boot screen and loads.
Edit 3 - Android same thing, Select Android in option, boot screen does show. Then it is black screen for 3 minutes, and then android home screen loads

OOOPS Edit 4 - Went back and flashed 1105 version, device updated fine and rebooted however now SPI does not work at all. Dead as a dodo, does not appear device stuck on Hardkernel logo. So that will teach me for playing today lol, Luckily EMMC mode still works so this will be single boot Android only from now on, not a biggie as the N2+ arrives Monday so this is relegated to Bedroom tv duties.

CoolGames · Post by **CoolGames** » Fri Jul 24, 2020 9:38 pm

thering1975 wrote: ↑
Fri Jul 24, 2020 9:09 pm
Updated to the latest version, and both Android on EMMC and CoreElec on SD card show in the menu. However Android shows the bootscreen and once its finished loading the screen is just Black (signal being sent but no image) Same with Coreelec, however i see no boot screen, again signal is there but it is just a black screen. This is on the latest version of coreelec, voodiks 17.1 android and latest petitboot

Edit - Coreelec stayed on blackscreen from pressing select in the option menu for about 5 minutes, and then the coreelec displayed and opened up after 5minutes, will try that with Android
Edit 2 - repeated CoreElec test and the same thing happens, select entry, black screen for 5 minutes and then it appears.

I had Ubuntu Updater request so I did it then required reboot so also did sp-update which also succeeded then system wanted DC removed and re-applied.

Code: Select all

$ uname -a
Linux cooldroidn2 5.7.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.7.9-202007221540~focal (2020-07-22) aarch64 aarch64 aarch64 GNU/Linux

I let SPI boot to Ubuntu on consumer HDTV 1080p 60hz and black screen but no "no signal" as before.
I toggled through TV antenna and back to HDMI1 and Ubuntu greeter was showing so all sync except refresh of display is now working.
I will test other CoreELEC and Android from microSD some point as time allows.
Also will try a Mali driver when I have time to backup then reinstall from netboot installer.

I saw this on next update / upgrade cycle.
Not sure what to expect if run.

Code: Select all

$ dpkg -l *grader*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                         Version      Architecture Description
+++-============================-============-============-=================================
ii  ubuntu-release-upgrader-core 1:20.04.23   all          manage release upgrades
ii  ubuntu-release-upgrader-gtk  1:20.04.23   all          manage release upgrades

thering1975 · Post by **thering1975** » Fri Jul 24, 2020 9:55 pm

Cool fair enough what was odd was it had not started booting Core Elec, as the CE boot screen started after 5 mins of black screen, but me SPI is now dead and just updated me post lol, such is life, i should learn to stop playing around with things when they work lol

My Fault not OP just for clarification

tobetter · Post by **tobetter** » Fri Jul 24, 2020 11:08 pm

thering1975 wrote: ↑
Fri Jul 24, 2020 9:55 pm
Cool fair enough what was odd was it had not started booting Core Elec, as the CE boot screen started after 5 mins of black screen, but me SPI is now dead and just updated me post lol, such is life, i should learn to stop playing around with things when they work lol

My Fault not OP just for clarification

So, what's happening now? Still not able to use SPI boot?
Can you let me know what's the version of the Petitboot you have?

thering1975 · Post by **thering1975** » Sat Jul 25, 2020 12:16 am

I upgraded this morning to your latest but faced those weird issues with 5 min black screens.

I attempted to downgrade back to 11th May 1105, it flashed and verified fine and rebooted then nothing no SPI at all

If i leave the switch in SPI position i get Hardkernel logo and that is all does not do anything else.

But as mentioned no drama here i will just use this as a single boot device for the bedroom, as long as android boots it is okay

thering1975 · Post by **thering1975** » Sat Jul 25, 2020 5:00 am

Yeah it looks like my board or part of it is dead now. Cant boot android succesfully any more either. Core Elec on SD boots and works perfectly, but anything on EMMC is a no no. Just tried 2 different EMMC Modules with a fresh install of voodiks 17.1 and Odroids stock latest, and just get black screens, bootloops or reboots does no longer make it to desktop.

However good excuse for some shopping tomorrow

Edited - Android has booted but dare not do anything at the mo until me board arrives lol need me tv fix.

But SPI is definitely gone, vanished so to speak, no boot at all in SPI mode no way to update or flash SPI again just hangs at HK logo

Sholander · Post by **Sholander** » Sun Jul 26, 2020 4:08 am

Did you try to fix Petitboot via Recovery image (https://dn.odroid.com/S922X/ODROID-N2/S ... 408+85.img)
First burn the image to uSD card, then replace burned spiboot.img on the uSD card with latest version (or any of your choice).

Then unplug N2 then TAKE OUT eMMC CARD MODULE, insert prepared uSD card, put the SPI switch to MMC position and power on N2. This process should restore corrupted Petitboot:
https://wiki.odroid.com/odroid-n2/os_images/petitboot

thering1975 · Post by **thering1975** » Sun Jul 26, 2020 4:36 am

Hi

Indeed i tried, however i did not get round to replacing the spiboot in the img file with the latest just yet as need to unpack image /enlarge partition etc as the latest spiboot does not fit on current burnt image on emmc think its partition is set at about 21mb or so, was going to play with that tomorrow, as my head was busy compiling some Android and time has just passed by a bit to quick.

Sholander · Post by **Sholander** » Sun Jul 26, 2020 4:53 am

thering1975 wrote: ↑
Sun Jul 26, 2020 4:36 am
i did not get round to replacing the spiboot in the img file with the latest just yet as need to unpack image /enlarge partition etc as the latest spiboot does not fit on current burnt image on emmc think its partition is set at about 21mb or so

??? I think you got something wrong, spiboot.img has nothing to do on/with eMMC! It is updated or repaired only via uSD card! It installs to and runs only from 8Mb onboard flash memory, and runs only when SPI switch is in SPI position.

thering1975 · Post by **thering1975** » Sun Jul 26, 2020 4:59 am

Sholander wrote: ↑
Sun Jul 26, 2020 4:53 am

thering1975 wrote: ↑
Sun Jul 26, 2020 4:36 am
i did not get round to replacing the spiboot in the img file with the latest just yet as need to unpack image /enlarge partition etc as the latest spiboot does not fit on current burnt image on emmc think its partition is set at about 21mb or so
??? I think you got something wrong, spiboot.img has nothing to do on/with eMMC! It is updated or repaired only via uSD card! It installs to and runs only from 8Mb onboard flash memory, and runs only when SPI switch is in SPI position.

Apologies for the confusion , i don't have a spare sd card so im using my spare emmc and emmc sd card adaptor but as mentioned when you flash the recover image it sets the partion at circa 21mb so when you try and place a newer version on it, it pops up with not enough space, i have just however extended the partition so will try again in a minute

Sholander · Post by **Sholander** » Sun Jul 26, 2020 7:56 am

thering1975 wrote: ↑
Sun Jul 26, 2020 4:59 am
Apologies for the confusion , i don't have a spare sd card so im using my spare emmc and emmc sd card adaptor but as mentioned when you flash the recover image it sets the partion at circa 21mb so when you try and place a newer version on it, it pops up with not enough space,

?????? You only replace the written spiboot.img that was put by recovery.img, dated sometime in 2019 with latest image dated 2020 07 21. All images are 8 Mb in size, so why are you talking about resizing? What resizing is needed if you delete an 8 Mb file and then write a new one same 8 Mb size ???