Petitboot, yet another bootloader based on KEXEC

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Mon Feb 03, 2020 11:13 pm

baalho wrote:
tobetter wrote:
Mon Feb 03, 2020 9:12 am
baalho wrote:
Mon Feb 03, 2020 5:02 am
I was not even testing the Samsung card for this particular problem.
I am sorry, I do not understand your instructions. I have few different SD card, and I can load any OS you would like me to test.

So basically, after flashing the latest Petitboot, i am stuck at u-boot. Feels like Irrespective of what boot media i am using, this issue is different.

I can use Etcher to flash SD card with any OS you want me to try. I can take emmc out and boot said SD card, with BOOT switch on eMMC.
Can you grab the logs from U-boot?
I need to connect via UART to get U-boot logs right? Will have to buy a USB-UART Module for it, i dont current own one.
roterdrachen wrote:I´ve got these 3 uSD. The 128 GB Sandisk is brand-new ~ 3 days old. With the 8GB Sandisk I only make Petitboot updates. I use the 128GB Sandisk and 32GB Samsung to test. I don´t think that they both are faulty because I can flash every single one and boot up e.g. Android without problems with eMMC switch enabled (without eMMC inserted). I just can´t boot the same sd cards with Petitboot enabled (with switch set to SPI) That´s the one problem with Petitboot + sd cards.
The other problem is that if I flash e.g. Android to eMMC, SPI=Petitboot=enabled, I also can´t boot up. But I can boot up the eMMC Android image with eMMC switch=enabled. Perhaps I have a different firmware or hardware revision? (I need a...) Is there a full image with "factory reset" and stable working Petitboot?
When you boot the Android from eMMC by the Petitboot, did you attach the SD card? If so, can you please test without it?

"Tapatalk wishes you to have fun with ODROID"


roterdrachen
Posts: 10
Joined: Fri Jan 31, 2020 10:32 pm
languages_spoken: english deutsch
ODROIDs: N2
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by roterdrachen » Tue Feb 04, 2020 1:21 am

@Sholander
Yes, the Android version "Android PIE-R.06 4GB image from secuflag" starts normaly with only uSD card inserted and SPI switch=eMMC.

@tobetter
I flashed with Etcher the Android version "Android PIE-R.06 4GB image from secuflag" 4GB_arm64_PIE-R.06_selfinstall-odroidn2.img.xz.
I can boot this image from eMMC with switch=eMMC, no sdcard inserted.
During the next steps SPI=always on
I can´t boot this same Android image with clean install of Petitboot 20191127, no sdcard inserted.
During booting the TV went black, then no signal, after a while I saw the Hardkernel Logo.
Then I saw the attached error screen. (No Petitboot screen)
Now I can´t get to the Petitboot screen anymore.
If I power cycle it (with SPI=on) I always get this error screen.
I must make a "factory reset" and wipe the data.
Then I´m able to go back to the Petitboot screen.
Attachments
IMG_20200203_170124.jpg
IMG_20200203_170124.jpg (282.46 KiB) Viewed 3381 times
IMG_20200203_170100.jpg
IMG_20200203_170100.jpg (291.15 KiB) Viewed 3381 times
IMG_20200203_170016.jpg
IMG_20200203_170016.jpg (201.59 KiB) Viewed 3381 times

c9v87kh2
Posts: 5
Joined: Sat Jan 11, 2020 12:50 am
languages_spoken: french,english
ODROIDs: Odroid-N2
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by c9v87kh2 » Tue Feb 04, 2020 1:53 am

tobetter wrote:
Tue Feb 19, 2019 3:25 pm
[...] [...]
Hello @tobetter,

3rd link is broken, so how could I build the last stable version (viewtopic.php?f=182&t=33873&start=150#p273785) ?

Thank you

baalho
Posts: 22
Joined: Tue Nov 19, 2019 4:24 am
languages_spoken: english
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by baalho » Tue Feb 04, 2020 2:20 am

tobetter wrote:
Mon Feb 03, 2020 11:11 pm
Yes, I thought you have one since you said you are stuck at U-boot. Can you please test to boot from eMMC after remove the SD card?

"Tapatalk wishes you to have fun with ODROID"
@tobetter,
With Petitboot, 20200118, if the boot select switch is on SPI i get no signal to TV, and N2 has solid Red LED when i have only eMMC. When the switch is on eMMC, N2 boots CoreElec without a problem.
With any older revision of Petitboot, i have no issue at all. When I made this summary before, you said i might be stuck at u-boot.
I am a newbie, so i am not sure if I am infact stuck in u-boot or what the issue is.
The last couple post i have made on the latest revision of Petitboot is unchanged.

For the time being I have reverted back to the last stable release of Petitboot, will try to debug some more if and when I get UART module.
I will not mess with dual booting, just run CoreElec on eMMC.

Regardless, I do want to thank your for your patience and providing insight on what the issue could have been with using the latest "experimental" build.

Samveen
Posts: 4
Joined: Wed Feb 05, 2020 2:28 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Samveen » Wed Feb 05, 2020 4:40 pm

@tobetter I am very interested in getting netboot portion of petitboot to work, so I followed the petitboot source link for Joy's petitboot repo posted in the first post. however I see that it has not been updated for a year, and the same is the case with your fork of Joy's repo . would you point out where you are doing your development, so that I can contribute to getting PXE in petitboot to work? Ideally I am looking for the documentation of the SPI image build process that you are using.

Background: I am working on setting up a 10 N2 cluster (with hopes of expanding it into a cluster of 40). The aim is to create a testbed for Kubernetes in a heterogenous OS environment, with the possibility of changing the OS via network install. I was hoping to port and use a cluster management framework that I use extensively to a new architecture in the hopes of creating a micro Data center. For any starting point for this, the client requirement is such that I need PXE support to be baked into the SPI itself.

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Wed Feb 19, 2020 5:48 am

It's been a year since I've started this thread already and I planned to release yet another improved version for the celebration.
Unfortunately, it's not optimistic but I still have another 18 hours KST. :D

The upcoming feature is:
1. Fixing the display issue for some users who meets the black screen issue.
2. Supporting PXE boot using the Petitboot which I've tried to learn how PXE works on the Petitboot since last Dec/2019, this requires a bit of documentation.
3. Some minor fixes on kernel/U-boot upgrades.

Stay tuned.
These users thanked the author tobetter for the post (total 4):
Sav (Wed Feb 19, 2020 7:46 am) • odroid (Wed Feb 19, 2020 9:22 am) • mad_ady (Wed Feb 19, 2020 1:15 pm) • jgmdev (Thu Feb 20, 2020 1:42 am)

User avatar
mad_ady
Posts: 7579
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 397 times
Been thanked: 302 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Wed Feb 19, 2020 1:16 pm

PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Wed Feb 19, 2020 1:41 pm

mad_ady wrote:
Wed Feb 19, 2020 1:16 pm
PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...
Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.
These users thanked the author tobetter for the post:
mad_ady (Wed Feb 19, 2020 1:49 pm)

User avatar
mad_ady
Posts: 7579
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 397 times
Been thanked: 302 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Wed Feb 19, 2020 1:50 pm

Sounds like a great wiki page and article idea :D

brad
Posts: 1063
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 29 times
Been thanked: 56 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by brad » Wed Feb 19, 2020 3:43 pm

tobetter wrote:
Wed Feb 19, 2020 1:41 pm
Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.
This is a very nice feature (either petitboot or uboot) for PXE on spi meaning we can have diskless N2's booting linux :)

Linux kernel supports 3 remote configurations for remote disk / filesystem

- iSCSI (block device) rootfs
- NFS rootfs (network filesystem)
- CIFS / SMB (experimental feature network rootfs - being integrated into recent mainline versions)

mxmilkb
Posts: 61
Joined: Fri Apr 26, 2019 9:28 am
languages_spoken: English
ODROIDs: N2
Has thanked: 21 times
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mxmilkb » Fri Feb 21, 2020 2:41 am

Aside; when I got this laptop, my previous was dead and I had no free USB stick, so I used the Servers Ultimate Android app to run a PXE server and host netboot.xyz which I booted my laptop with to install Arch Linux from the internet with.
Last edited by mxmilkb on Fri Feb 28, 2020 10:48 pm, edited 1 time in total.

Samveen
Posts: 4
Joined: Wed Feb 05, 2020 2:28 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Samveen » Mon Feb 24, 2020 4:07 pm

tobetter wrote:
Wed Feb 19, 2020 1:41 pm
mad_ady wrote:
Wed Feb 19, 2020 1:16 pm
PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...
Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.
Actually not just dnsmasq, but any combination of a DHCP server that supports the boot-file and next-server opts and a tftp server to host the files (I've had to use udhcpd and in.tftpd via xinetd in a pinch from an Ubuntu Bionic LiveCD (18.04.03) ).

This will make the process of provisioning a whole bunch of N2s so so so so much easier: a huge step towards a true Micro Data-centre ;) 8-) :lol:

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Mon Feb 24, 2020 4:18 pm

Samveen wrote:
Mon Feb 24, 2020 4:07 pm
tobetter wrote:
Wed Feb 19, 2020 1:41 pm
mad_ady wrote:
Wed Feb 19, 2020 1:16 pm
PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...
Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.
Actually not just dnsmasq, but any combination of a DHCP server that supports the boot-file and next-server opts and a tftp server to host the files (I've had to use udhcpd and in.tftpd via xinetd in a pinch from an Ubuntu Bionic LiveCD (18.04.03) ).

This will make the process of provisioning a whole bunch of N2s so so so so much easier: a huge step towards a true Micro Data-centre ;) 8-) :lol:
True.
FYI, I've set up the example PXE server for Debian/Ubuntu Netboot installer and it works, I am going to upload the working version here today or tomorrow.
http://ppa.linuxfactory.or.kr/installer ... ODROID-N2/
These users thanked the author tobetter for the post:
odroid (Mon Feb 24, 2020 4:44 pm)

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Mon Feb 24, 2020 11:11 pm

20200224

Let me introduce a new version of the year 2020, please click spiboot-20200224.img to download and copy the file to your uSD card as spiboot.img or you can update with pb-update command in shell of the Petitboot if you have the version after 20191127
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

What's improved:
  • Blank screen issue on 4K TV is improved.
Many users using 4K TV had an issue that nothing shows after Petitboot due to a bug, that's been fixed but need more test with various TV vendors.[/list]
  • UHS (Ultra High Speed) is off by default.
Some users with a certain micro SD card had a booting issue, specifically Samsung EVO, and this issue could be resolved after disabling UHS support since version 20200118. But more users start to use the same memory cards and due to the difficulty to set the flag, it's been disabled by default. Please visit the link for more detail, viewtopic.php?f=182&t=33873&hilit=20200 ... 00#p278201
  • PXE support is enabled.
PXE is the very new feature that can support network booting if you have DHCP and TFTP/HTTP server. This is not necessary feature for a regular user but very helpful for a system with multiple N2.

Running PXE
I've set up the example PXE server at http://ppa.linuxfactory.or.kr/installer ... ODROID-N2/, N2 will display multiple boot entries of Debian/Ubuntu Netboot installers like this.
IMG_20200224_2236216.jpg
IMG_20200224_2236216.jpg (304.31 KiB) Viewed 2557 times
In order to run PXE, you need to set up DHCP server by default and TFTP or HTTP server is required. I've done using Apache for HTTP server and dnsmasq for DHCP server. In order to make DHCP server to fetch the PXE configuration, DHCP configuration needs to be modified and this is my change for dnsmasq. Most important change for PXE in the change is the lines that start with dhcp-option-force= and these two lines offers the server where to fetch the PXE menus when Petitboot establish the dynamic IP address by the same DHCP server.

Code: Select all

--- dnsmasq.conf.orig   2020-02-15 03:43:46.828796708 +0900
+++ dnsmasq.conf        2020-02-22 00:18:47.845256410 +0900
@@ -64,6 +64,8 @@
 # Add other name servers here, with domain specs if they are for
 # non-public domains.
 #server=/localnet/192.168.0.1
+server=8.8.8.8
+server=8.8.4.4
 
 # Example of routing PTR queries to nameservers: this will send all
 # address->name queries for 192.168.3/24 to nameserver 10.1.2.3
@@ -141,7 +143,7 @@
 # 2) Sets the "domain" DHCP option thereby potentially setting the
 #    domain of all systems configured by DHCP
 # 3) Provides the domain part for "expand-hosts"
-#domain=thekelleys.org.uk
+domain=linuxfactory.or.kr
 
 # Set a different domain for a particular subnet
 #domain=wireless.thekelleys.org.uk,192.168.2.0/24
@@ -160,7 +162,7 @@
 # is needed for networks we reach the dnsmasq DHCP server via a relay
 # agent. If you don't know what a DHCP relay agent is, you probably
 # don't need to worry about this.
-#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
+dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
 
 # This is an example of a DHCP range which sets a tag, so that
 # some DHCP options may be set only for this network.
@@ -328,7 +340,8 @@
 
 # Override the default route supplied by dnsmasq, which assumes the
 # router is the same machine as the one running dnsmasq.
-#dhcp-option=3,1.2.3.4
+dhcp-option=3,192.168.0.1
+dhcp-option=6,192.168.0.2
 
 # Do the same thing, but using the option name
 #dhcp-option=option:router,1.2.3.4
@@ -429,9 +442,9 @@
 # Magic number - needed before anything else is recognised
 #dhcp-option-force=208,f1:00:74:7e
 # Configuration file name
-#dhcp-option-force=209,configs/common
+dhcp-option-force=209,pxeboot/ODROID-N2/default
 # Path prefix
-#dhcp-option-force=210,/tftpboot/pxelinux/files/
+dhcp-option-force=210,http://ppa.linuxfactory.or.kr/installer/
 # Reboot time. (Note 'i' to send 32-bit value)
 #dhcp-option-force=211,30i
In order to achieve the same result or for quick testing, you can run this command in the shell prompt of the Petitboot and this command will fetch the PXE config file from my server directly without DHCP server setup.

Code: Select all

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default
I have not tested to use TFTP instead of HTTP, but it will work for sure and if you have NFS server and set up the command line properly Linux kernel can mount a directory in the NFS server, this will make diskless ODROID-N2 system. Maybe PXE support is necessary to be forked to other threads?

Please keep sharing your experience with the Petitboot.
These users thanked the author tobetter for the post (total 4):
mad_ady (Mon Feb 24, 2020 11:15 pm) • brad (Mon Feb 24, 2020 11:41 pm) • Sav (Tue Feb 25, 2020 2:09 am) • odroid (Tue Feb 25, 2020 9:46 am)

minoccio
Posts: 26
Joined: Thu Sep 12, 2019 3:20 pm
languages_spoken: Italian
ODROIDs: N2
Has thanked: 11 times
Been thanked: 3 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by minoccio » Thu Feb 27, 2020 4:23 pm

does the uhs-unable feature reduce the speed of uSD during the normal use?

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Thu Feb 27, 2020 4:31 pm

minoccio wrote:
Thu Feb 27, 2020 4:23 pm
does the uhs-unable feature reduce the speed of uSD during the normal use?
The feature only affects the Petitboot, normal OS will initiate the uSD speed when its own kernel starts.
These users thanked the author tobetter for the post:
minoccio (Fri Feb 28, 2020 4:09 pm)

joschi
Posts: 2
Joined: Fri Feb 28, 2020 10:10 pm
languages_spoken: english
ODROIDs: ODROID-N2
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by joschi » Fri Feb 28, 2020 10:31 pm

I've been trying to get petitboot running on my ODROID-N2 and it's working strictly speaking, but it never shows anything on the display.
For the whole boot process it only shows a blank screen until the OS (CoreELEC 9.2.1) from the SD card has been booted.

I've tried with petitboot 20191127 and with petitboot 20200224, both with the same result: Only a blank (black) screen while booting until CoreELEC/Kodi comes up.

I think this has to do with the fact that the display (an old Toshiba TV) is "lying" about the display resolutions it supports.
The display advertises 1080i50hz as preferred resolution, but only supports up to 720p60hz.

Is there a way to force petitboot to use a specific display resolution?

Here are some details about the display, please let me know if you need anything else.

Code: Select all

# cat /sys/class/amhdmitx/amhdmitx0/disp_cap
480i60hz
576i50hz
480p60hz
576p50hz
720p60hz
1080i60hz
720p50hz
1080i50hz*

Code: Select all

# cat /sys/class/amhdmitx/amhdmitx0/edid
Rx Manufacturer Name: TSB
Rx Product Code: 0106
Rx Serial Number: 01010101
Rx Product Name: TOSHIBA-TV
Manufacture Week: 255
Manufacture Year: 2008
Physcial size(cm): 105 x 59
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x97
Source Physical Address[a.b.c.d]: 2.0.0.0
native Mode 71, VIC (native 20):
ColorDeepSupport 0
20 19 18 22 17 21 5 4 3 7 2 6 1
Audio {format, channel, freq, cce}
{1, 1, 7, 7}
Speaker Allocation: 0
Vendor: 0xc03 ( HDMI device)
MaxTMDSClock1 80 MHz
vLatency:  Invalid/Unknown
aLatency:  Invalid/Unknown
i_vLatency:  Invalid/Unknown
i_aLatency:  Invalid/Unknown
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0

checkvalue: 0x97260000

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Feb 28, 2020 10:52 pm

@joschi, you mean that you have never seen the face of the Petitboot but CoreELEC boots?
There are two ways to select different display resolutions.
1. Create a file petitboot.cfg in the root directory of a uSD, for example, if you like to use 720p60hz instead of 1080p60hz which is the default resolution. You can try multiple times to find out the best resolution supported by your TV. This method won't store the resolution, so if you remove the uSD, the default display resolution will be applied.

Code: Select all

[petitboot]
hdmimode=720p60hz
2. In the shell of the Petitboot, you can store the display resolution to SPI flash memory. This method is good after looking for the best resolution with petitboot.cfg.

Code: Select all

# spimmc.sh
# fw_setenv hdmimode 720p60hz
These users thanked the author tobetter for the post:
joschi (Fri Feb 28, 2020 10:59 pm)

joschi
Posts: 2
Joined: Fri Feb 28, 2020 10:10 pm
languages_spoken: english
ODROIDs: ODROID-N2
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by joschi » Fri Feb 28, 2020 11:01 pm

tobetter wrote:
Fri Feb 28, 2020 10:52 pm
@joschi, you mean that you have never seen the face of the Petitboot but CoreELEC boots?
Yes, exactly.
tobetter wrote:
Fri Feb 28, 2020 10:52 pm
1. Create a file petitboot.cfg in the root directory of a uSD, for example, if you like to use 720p60hz instead of 1080p60hz which is the default resolution. You can try multiple times to find out the best resolution supported by your TV. This method won't store the resolution, so if you remove the uSD, the default display resolution will be applied.

Code: Select all

[petitboot]
hdmimode=720p60hz
This works like a charm, thank you so much!

After creating the configuration file at /flash/petitboot.cfg (where the first partition of the SD card is mounted) and rebooting, I can finally see the petitboot screen.

Bubblefish0815
Posts: 5
Joined: Tue Dec 31, 2019 3:54 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Bubblefish0815 » Sun Mar 15, 2020 12:52 am

So , I tested the new petitboot (20022020) - always the same

I see the Hardkernel logo , switch between
* Core elec
* Emuelec
* Ubunto
select one ... enter .. black screen , but all systems are booting and I see the screen after switch off/on the LCD


( I tested also the older petitboot - booting from petitboot is fine - but then black screen )
4 K LCD

any hints ?

Sav
Posts: 182
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 31 times
Been thanked: 13 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Sav » Sun Mar 15, 2020 1:00 am

Maybe you have to manual set the screen resolution editing the boot.ini files. You also have to set to false the aitodetect variable.

Inviato dal mio GM1913 utilizzando Tapatalk


brad
Posts: 1063
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 29 times
Been thanked: 56 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by brad » Sun Mar 15, 2020 9:22 am

Hi @tobetter,
I notice new patch series coming for mainline linux to support SPIFC - https://patchwork.kernel.org/project/li ... ies=255937

By default it would be off but with device tree changes it could be enabled along side emmc (emmc downgraded from 8 bit to 4 bit in this case). May be helpful for petiboot to flash new images or accessing emmc during SPI boot process.

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sun Mar 15, 2020 9:08 pm

brad wrote:
Sun Mar 15, 2020 9:22 am
Hi @tobetter,
I notice new patch series coming for mainline linux to support SPIFC - https://patchwork.kernel.org/project/li ... ies=255937

By default it would be off but with device tree changes it could be enabled along side emmc (emmc downgraded from 8 bit to 4 bit in this case). May be helpful for petiboot to flash new images or accessing emmc during SPI boot process.
Thank you for pointing me out the patches. I've tried a similar approach with Linux 4.9 earlier but no luck and not spent much time to figure out since it could reduce the performance of eMMC. Instead, I've made the drivers for SPI and eMMC as a kernel module so that they can switch one to another by loading and unloading the module accordingly. I would try sometime later... :)

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sun Mar 15, 2020 9:14 pm

Bubblefish0815 wrote:
Sun Mar 15, 2020 12:52 am
So , I tested the new petitboot (20022020) - always the same

I see the Hardkernel logo , switch between
* Core elec
* Emuelec
* Ubunto
select one ... enter .. black screen , but all systems are booting and I see the screen after switch off/on the LCD


( I tested also the older petitboot - booting from petitboot is fine - but then black screen )
4 K LCD

any hints ?
Are you running this version? Since I never had released any Petitboot in the year 2002.
viewtopic.php?f=182&t=33873&p=286050#p282985

And like @Sav mentioned, can you try to edit boot.ini to set display_autodetect as false? in the Ubuntu image and can you let me know the output with the command cat /proc/cmdline?
Let me know the branch and model of your TV if possible?

Bubblefish0815
Posts: 5
Joined: Tue Dec 31, 2019 3:54 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Bubblefish0815 » Thu Mar 19, 2020 2:52 am

So,
Sorry , yes I run the latest Version.

I change the boot.ini testing in Ubunto / flash boot.ini coreelec - ( display autodetect and resulution ).
SPI right mmc - corelec boots fine also emuelec
SPI left petitboot - petitboot logo / screen with coreelec/emuelec /ubunto

I tested all 3 , all are booting but the screen of my LCD is black - power switch off/on my LCD - all are working , tested on different HDMI inputs and No Switch or Receiver between N2 / LCD
( plugoff / plugin HDMI cable -- no effect )

Tested on Thosiba 4K (55') , Medion 4K (65') , Samsung 4K(55')

Hmm,unfortunately I have no more ideas

PS: Today I take the N2 and tested on a Philips 55' 1080p - working perfectly !

Problem are 4K panels

User avatar
tobetter
Posts: 4674
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 89 times
Been thanked: 338 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Thu Mar 19, 2020 3:16 am

Bubblefish0815 wrote:
Thu Mar 19, 2020 2:52 am
So,
Sorry , yes I run the latest Version.

I change the boot.ini testing in Ubunto / flash boot.ini coreelec - ( display autodetect and resulution ).
SPI right mmc - corelec boots fine also emuelec
SPI left petitboot - petitboot logo / screen with coreelec/emuelec /ubunto

I tested all 3 , all are booting but the screen of my LCD is black - power switch off/on my LCD - all are working , tested on different HDMI inputs and No Switch or Receiver between N2 / LCD
( plugoff / plugin HDMI cable -- no effect )

Tested on Thosiba 4K (55') , Medion 4K (65') , Samsung 4K(55')

Hmm,unfortunately I have no more ideas

PS: Today I take the N2 and tested on a Philips 55' 1080p - working perfectly !

Problem are 4K panels
For your 4K TV, can you try one of these for hdmimode in your boot.ini? So like, instead of setenv hdmimode 1080p60hz, use setenv hdmimode 2160p30hz or so.
# "2160p60hz" | 3840x2160 Progressive 60Hz
# "2160p50hz" | 3840x2160 Progressive 50Hz
# "2160p30hz" | 3840x2160 Progressive 30Hz
# "2160p25hz" | 3840x2160 Progressive 25Hz
# "2160p24hz" | 3840x2160 Progressive 24Hz
Also, please let me know the output with cat /proc/cmdline once you have booted with any OS if you can connect through SSH or when screen comes after off/on your TV.

Post Reply

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 5 guests