Petitboot, yet another bootloader based on KEXEC

everlasting
Posts: 46
Joined: Thu Mar 28, 2019 7:10 am
languages_spoken: english
ODROIDs: N2
Has thanked: 7 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by everlasting » Fri Jun 21, 2019 9:18 am

thanks, it was able to save after i took my emmc out, before i had it in. it seems 1 second is the lowest, as you cant enter a decimal and if i do 05 it just becomes 5 seconds. 1 second is fine. if i set it to 0 it wont give me a chance to input anyting since it boots the emmc immediately.

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 21, 2019 11:07 am

:roll: i`m confused i flashed the sd-card and put the new file on the card
booted it up with the selector into sd-card select...
it came up with the petitboot menu...
it seems to have make no difference with my ssd drive also connected..

i could not save any entries..is it supposed to be able to save data entered into the petitboot -sd-card memory..
i cannot get it to save ...
maybe i dont need the upgrade it did not come up with flashing the petitboot chip...so i am still confused..
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 21, 2019 12:04 pm

phaseshifter wrote:
Fri Jun 21, 2019 11:07 am
:roll: i`m confused i flashed the sd-card and put the new file on the card
booted it up with the selector into sd-card select...
it came up with the petitboot menu...
it seems to have make no difference with my ssd drive also connected..

i could not save any entries..is it supposed to be able to save data entered into the petitboot -sd-card memory..
i cannot get it to save ...
maybe i dont need the upgrade it did not come up with flashing the petitboot chip...so i am still confused..
What's the version of Petitboot you see on the display?
The boot selector switch must be toggled to "SPI".

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 21, 2019 4:31 pm

i see dev.20190417
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 21, 2019 4:32 pm

i dont know what i am supposed to do exactly...??
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 21, 2019 4:39 pm

phaseshifter wrote:
Fri Jun 21, 2019 4:32 pm
i dont know what i am supposed to do exactly...??
Did you copy the my recent binary RC3 to your SD card as spiboot.img and reboot it? Once rebooted, nothing happening in the display?

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 21, 2019 4:50 pm

so i have to rename the 8mb file to spiboot.img correct
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 21, 2019 4:58 pm

phaseshifter wrote:
Fri Jun 21, 2019 4:50 pm
so i have to rename the 8mb file to spiboot.img correct
Yes, the Petitboot in SPI flash memory will read it to upgrade.
These users thanked the author tobetter for the post:
phaseshifter (Fri Jun 21, 2019 5:43 pm)

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 21, 2019 5:43 pm

got it going cool modd very nice
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

copyer
Posts: 5
Joined: Fri Apr 26, 2019 2:20 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by copyer » Fri Jun 21, 2019 7:14 pm

Hi, do i need this booloader upgrade too? i make use of the N2 with Coreelec..

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Fri Jun 21, 2019 7:30 pm

Not unless you boot from spi.
These users thanked the author mad_ady for the post:
copyer (Fri Jun 21, 2019 10:00 pm)

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Fri Jun 21, 2019 10:41 pm

@tobetter: I finally made time and tested RC3. I had to flash it with the recovery SD, because my previous SPI was flashed incompletely (uboot would start but could not load the kernel).
Anyway - it boots, but display still has no signal during petitboot. After a short while the first option is booted automatically (so kudos for that!).
Here are some (I hope) relevant information. I only have an emmc with Ubuntu Mate on it connected to the N2.

My boot.ini: http://paste.ubuntu.com/p/ZhD83WwfBG/
Display autodetection works for my display - it's put in 1280x1024. It works on emmc boot, or when the OS starts via petitboot, but not within petitboot.

I also changed my boot.ini to the following settings: http://paste.ubuntu.com/p/gHfR7ftK2Y/, basically turning off autodetection and setting the correct resolution and display mode. It works the same way - no image in petitboot, but fine after the target system starts.

Here is the boot log (the petitboot part), if it helps (ran with the modified boot.ini settings):

Code: Select all

G12B:BL:6e7c85:7898ac;FEAT:E0F83180:2000;POC:B;RCY:0;SPINOR:0;0.4
                                                                 bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:04000000
B2:00002000
B1:e0f83180

TE: 58480

BL2 Built : 10:47:19, Jan 14 2019. g12b g152d217 - guotai.shen@droid11-sz

Board ID = 3
Set A53 clk to 24M
Set A73 clk to 24M
Set clk81 to 24M
A53 clk: 1200 MHz
A73 clk: 1200 MHz
CLK81: 166.6M
smccc: 00012ca9
DDR driver_vesion: LPDDR4_PHY_V_0_1_11 build time: Jan 14 2019 10:47:15
board id: 3
Load FIP HDR from SPI, src: 0x00010000, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from SPI, src: 0x00030000, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from SPI, src: 0x0002c000, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
ddr clk to 1320MHz
Load ddrfw from SPI, src: 0x00014000, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from SPI, src: 0x00020000, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

R0_RxClkDly_Margin==82 ps 7
R0_TxDqDly_Margi==94 ps 8


R1_RxClkDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0

 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001

 ddr scramble enable
2D training succeed
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00600024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass
 pre test  bdlr_100_average==479 bdlr_100_min==479 bdlr_100_max==479 bdlr_100_cur==479
 aft test  bdlr_100_average==479 bdlr_100_min==479 bdlr_100_max==479 bdlr_100_cur==479
100bdlr_step_size ps== 485
result report
boot times 2Enable ddr reg access
Load FIP HDR from SPI, src: 0x00010000, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from SPI, src: 0x0003c000, des: 0x0172c000, size: 0x00098000, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0
E30HDR
MVN_1=0x00000000
MVN_2=0x00000000
[Image: g12b_v1.1.3375-8f9c8a7 2019-01-24 10:44:46 guotai.shen@droid11-sz]
OPS=0x40
ring efuse init
chipver efuse init
29 0a 40 00 01 18 1a 00 00 19 34 37 57 4e 4b 50
[3.715954 Inits done]
secure task start!
high task start!
low task start!
run into bl31
NOTICE:  BL31: v1.3(release):ab8811b
NOTICE:  BL31: Built : 15:03:31, Feb 12 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01 (Jun 18 2019 - 18:12:22)

DRAM:  3.5 GiB
Relocation Offset is: d6ef3000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f84b10
MMC:   aml_priv->desc_buf = 0x00000000d3ee37c0
aml_priv->desc_buf = 0x00000000d3ee5b00
SDIO Port C: 0, SDIO Port B: 1
spifc_probe: reg=00000000ffd14000, mem_map=00000000f6000000
SF: Detected MX25U6435F with page size 256 Bytes, erase size 64 KiB, total 8 MiB
In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 9
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x29
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
** Bad device specification mmc -1 **
** Bad device specification mmc -1 **
movi: not registered partition name, logo
movi - Read/write command from/to SD/MMC for ODROID board

Usage:
movi <read|write> <partition|sector> <offset> <address> [<length>]
    - <read|write>  the command to access the storage
    - <offset>  the offset from the start of given partiton in lba
    - <address>  the memory address to load/store from/to the storage device
    - [<length>]  the size of the block to read/write in bytes
    - all parameters must be hexa-decimal only

[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=5760, height=2160
[OSD]wait_vsync_wakeup exit
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1312]
rx version is 1.4 or below  div=10
Net:   dwmac.ff3f0000
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1bf2800
emmc/sd response timeout, cmd55, status=0x1bf2800
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x1, tx-dly 0, clock 40000000
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x172000
[mmc_startup] mmc refix success
[mmc_init] mmc init success
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
SF: Detected MX25U6435F with page size 256 Bytes, erase size 64 KiB, total 8 MiB
SF: 3932160 bytes @ 0x120000 Read: OK
SF: 3276800 bytes @ 0x4e0000 Read: OK
SF: 131072 bytes @ 0x100000 Read: OK
card out
** Bad device mmc 1 **
card out
** Bad device mmc 1 **
edid extension block number : 1
Dump EDID Rawdata
00000000000000004eae950500000000310f010380261e78eacb05a3584c9b25
135054bfef0081808190718601010101010101010101302a009851002a403070
1300782d11000014000000fd00384b1f510e000a202020202020000000fc0058
37323032410a202020202020000000ff00303534395042303934320a2020001f
No header found - count 0
hdmitx: read edid fails.. retry..
edid extension block number : 1
Dump EDID Rawdata
00ffffffffffff004eae950500000000310f010380261e78eacb05a3584c9b25
135054bfef0081808190718601010101010101010101302a009851002a403070
1300782d11000014000000fd00384b1f510e000a202020202020000000fc0058
37323032410a202020202020000000ff00303534395042303934320a2020001f
no available storage to save debug file
Manufacturer: SUN Model 595 Serial Number 0
EDID version: 1.3
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
Standard timings supported:
  1280x1024@60Hz
  1280x1024@76Hz
  1152x921@66Hz
Detailed mode (1) : Clock 108 MHz, 376 mm x 301 mm
               1280 1328 1440 1688 hborder 0
               1024 1025 1028 1066 vborder 0
               -hsync +vsync digital composite
Monitor ranges (GTF): 56-75Hz V, 31-81kHz H, max dotclock 140MHz
Monitor name: X7202A
Serial number: 0549PB0942
Checksum: 0x1f (valid)
bestmode is custombuilt, IEEEOUI 0x000000
DVI Mode
no available storage to save debug file
[OSD]load fb addr from dts:/meson-fb
[OSD]fb_addr for logo: 0x7f800000
[OSD]load fb addr from dts:/meson-fb
[OSD]fb_addr for logo: 0x7f800000
[OSD]VPP_OFIFO_SIZE:0xfff01000
[CANVAS]addr=0x7f800000 width=5760, height=2160
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1312]
rx version is 1.4 or below  div=10
ee_gate_off ...
## Booting kernel from Legacy Image at 04000000 ...
   Image Name:
   Image Type:   AArch64 Linux Kernel Image (gzip compressed)
   Data Size:    3878911 Bytes = 3.7 MiB
   Load Address: 01080000
   Entry Point:  01080000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03080000 ...
   Image Name:
   Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
   Data Size:    2903325 Bytes = 2.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
libfdt fdt_path_offset() returned FDT_ERR_BADPATH
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x01994808
   Loading Ramdisk to 3d53b000, end 3d7ffd1d ... OK
   Loading Device Tree to 000000001ffec000, end 000000001ffffad2 ... OK
fdt_fixup_memory_banks, reg:0000000000000000

Starting kernel ...

uboot time: 9359484 us
Booting Linux on physical CPU 0x0
Linux version 4.9.180 (odroid@9a59640043b5) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #1 SMP PREEMPT Tue Jun 18 14:22:25 UTC 2019
Boot CPU: AArch64 Processor [410fd034]
Machine model: Hardkernel ODROID-N2
OF: reserved mem: __reserved_mem_alloc_size, start:0x0000000005000000, end:0x0000000005400000, len:4 MiB
Reserved memory: created CMA memory pool at 0x0000000005000000, size 4 MiB
OF: reserved mem: initialized node linux,secmon, compatible id shared-dma-pool
OF: reserved mem: __reserved_mem_alloc_size, start:0x000000007f800000, end:0x0000000080000000, len:8 MiB
Reserved memory: created CMA memory pool at 0x000000007f800000, size 8 MiB
OF: reserved mem: initialized node linux,meson-fb, compatible id shared-dma-pool
Reserved memory: created CMA memory pool at 0x00000000e5800000, size 128 MiB
OF: reserved mem: initialized node linux,ion-dev, compatible id shared-dma-pool
Reserved memory: created CMA memory pool at 0x00000000e3000000, size 40 MiB
OF: reserved mem: initialized node linux,di_cma, compatible id shared-dma-pool
Reserved memory: created DMA memory pool at 0x00000000e3000000, size 0 MiB
OF: reserved mem: initialized node linux,ppmgr, compatible id shared-dma-pool
Reserved memory: created CMA memory pool at 0x00000000cfc00000, size 308 MiB
OF: reserved mem: initialized node linux,codec_mm_cma, compatible id shared-dma-pool
OF: reserved mem: initialized node linux,codec_mm_reserved, compatible id amlogic, codec-mm-reserved
cma: Reserved 8 MiB at 0x00000000cf400000
psci: probing for conduit method from DT.
psci: PSCIv1.0 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
psci: MIGRATE_INFO_TYPE not supported.
psci: SMC Calling Convention v1.1
percpu: Embedded 19 pages/cpu s47064 r0 d30760 u77824
Detected VIPT I-cache on CPU0
CPU features: enabling workaround for ARM erratum 845719
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 957600
Kernel command line: rootfstype=ramfs init=/init console=ttyS0,115200n8 no_console_suspend earlyprintk=aml-uart,0xff803000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 console=tty0 logo=osd0,loaded,0x3d800000 osd_reverse=0 video_reverse=0 vout=custombuilt hdmimode=custombuilt voutmode=dvi modeline=1280,1024,108000,63981,60,1280,1328,1440,1688,1024,1025,1028,1066,0,1,1 customwidth=1280 customheight=1024 petitboot,write?=true petitboot,autoboot=true petitboot,bootdevs= petitboot,console=ttyS0,115200n8 petitboot,interface=eth0 petitboot,timeout=10
fb: osd0
fb: loaded
fb: 0x3d800000
vpp_axis_reverse: bootargs is 0
vout: get hdmimode: custombuilt
hdmitx: voutmode : 2
fmt_para.timing
   - pixel_freq 108000, frac_freq 108000
   - h_freq 63981, v_freq 60000
   - hsync_polarity 0, vsync_polarity 1
   - h_active 1280, h_total 1688
   - h_blank 408, h_front 48, h_sync 112, h_back 248
   - v_active 1024, v_total 1066
   - v_blank 42, v_front 1, v_sync 3, v_back 38
   - v_sync_ln 1
fmt_para.hdmitx_vinfo
   - name custombuilt, mode 0
   - width 1280, height 1024, field_height 1024
   - aspect_ratio_num 16, aspect_ratio_den 9
   - video_clk 108000000
   - htotal 1688, vtotal 1066
   - viu_color_fmt 2, viu_mux 2
log_buf_len individual max cpu contribution: 4096 bytes
log_buf_len total cpu_extra contributions: 20480 bytes
log_buf_len min size: 32768 bytes
log_buf_len: 65536 bytes
early log buf free: 27888(85%)
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 3300972K/3891200K available (5822K kernel code, 786K rwdata, 1196K rodata, 1472K init, 530K bss, 82324K reserved, 507904K cma-reserved)
Virtual kernel memory layout:
    modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)
    vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)
      .text : 0xffffff8009080000 - 0xffffff8009630000   (  5824 KB)
    .rodata : 0xffffff8009630000 - 0xffffff8009760000   (  1216 KB)
      .init : 0xffffff8009760000 - 0xffffff80098d0000   (  1472 KB)
      .data : 0xffffff80098d0000 - 0xffffff8009994808   (   787 KB)
       .bss : 0xffffff8009994808 - 0xffffff8009a19304   (   531 KB)
    fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)
    PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)
    vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)
              0xffffffbf00000000 - 0xffffffbf03b60000   (    59 MB actual)
    memory  : 0xffffffc000000000 - 0xffffffc0ed800000   (  3800 MB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
Preemptible hierarchical RCU implementation.
        Build-time adjustment of leaf fanout to 64.
        RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=6
NR_IRQS:64 nr_irqs:64 0
GPIO-INTC: support to detect double-edge trigger signal
g12a_aoclkc_init: register ao clk ok!
Meson chip version = RevA (29:A - 40:0)
meson_g12a_sdemmc_init: register amlogic sdemmc clk
meson_g12a_sdemmc_init: register amlogic sdemmc clk
meson_g12a_gpu_init: register meson gpu clk
meson_g12a_media_init: register meson media clk
meson_g12a_misc_init: register amlogic g12a misc clks
meson_g12a_misc_init: done.
g12a_clkc_init initialization complete
arm_arch_timer: Architected cp15 timer(s) running at 24.00MHz (phys).
clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
meson_bc_timer: mclk->mux_reg =ffffff800800c190,mclk->reg =ffffff800800e194
Console: colour dummy device 80x25
console [tty0] enabled
Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
pid_max: default: 6144 minimum: 301
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
sched-energy: Sched-energy-costs installed from DT
CPU0: update cpu_capacity 631
ASID allocator initialised with 65536 entries
Detected VIPT I-cache on CPU1
CPU1: update cpu_capacity 631
CPU1: Booted secondary processor [410fd034]
Detected VIPT I-cache on CPU2
CPU2: update cpu_capacity 920
CPU2: Booted secondary processor [410fd092]
Detected VIPT I-cache on CPU3
CPU3: update cpu_capacity 920
CPU3: Booted secondary processor [410fd092]
Detected VIPT I-cache on CPU4
CPU4: update cpu_capacity 920
CPU4: Booted secondary processor [410fd092]
Detected VIPT I-cache on CPU5
CPU5: update cpu_capacity 920
CPU5: Booted secondary processor [410fd092]
Brought up 6 CPUs
SMP: Total of 6 processors activated.
CPU features: detected feature: 32-bit EL0 Support
CPU: All CPU(s) started at EL2
alternatives: patching kernel code
devtmpfs: initialized
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
futex hash table entries: 16 (order: -2, 1024 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
schedtune: init normalization constants...
schedtune: CLUSTER[0-1]      min_pwr:     0 max_pwr:    42
schedtune: CPU[0]            min_pwr:     0 max_pwr:   279
schedtune: CPU[1]            min_pwr:     0 max_pwr:   279
schedtune: CLUSTER[2-5]      min_pwr:     0 max_pwr:    64
schedtune: CPU[2]            min_pwr:     0 max_pwr:   759
schedtune: CPU[3]            min_pwr:     0 max_pwr:   759
schedtune: CPU[4]            min_pwr:     0 max_pwr:   759
schedtune: CPU[5]            min_pwr:     0 max_pwr:   759
schedtune: SYSTEM            min_pwr:     0 max_pwr:  3700
schedtune: using normalization constants mul: 459677581 sh1: 1 sh2: 11
schedtune: configured to support 5 boost groups
cpuidle: using governor menu
register canvas platform driver
register rdma platform driver
aml_vdac_init: module init
vdso: 2 pages (1 code @ ffffff8009637000, 1 data @ ffffff80098d5000)
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
DMA: preallocated 2048 KiB pool for atomic allocations
clkmsr: clkmsr: driver init
codec_mm_module_init
media_configs_system_init
aml_iomap: amlogic iomap probe done
vpu: driver version: v20180925(8-g12b)
vpu: load vpu_clk: 666666667Hz(7)
vpu: clktree_init
vpu: vpu_probe OK
clkmsr: msr_clk_reg0=ffffff8008238004,msr_clk_reg2=ffffff800823a00c
clkmsr ffd18004.meson_clk_msr: failed to get msr ring reg0
aml_vdac_probe:probe start.cpu_id:6,name:meson-g12ab-vdac
aml_vdac_probe: ok
canvas_probe reg=00000000ff638000,size=2000
canvas maped reg_base =ffffff800823c000
rdma_probe,ver:0, len:8
rdma_register, rdma_table_addr ffffff8008273000 rdma_table_addr_phy cf600000 reg_buf ffffffc0cab68000
rdma_register success, handle 1 table_size 32768
set_rdma_handle video rdma handle = 1.
codec_mm codec_mm: assigned reserved memory node linux,codec_mm_cma
codec_mm codec_mm: assigned reserved memory node linux,codec_mm_cma
codec_mm_probe ok
cvbs_out: cvbsout_probe, cpu_id:5,name:meson-g12b-cvbsout
cvbs_out: clk_path config null
cvbs_out: error: failed to get vdac_config
vout: vout1: register server: cvbs_vout_server
cvbs_out: register cvbs module server ok
vout: vout2: register server: cvbs_vout2_server
cvbs_out: register cvbs module vout2 server ok
cvbs_out: chrdev devno 264241152 for disp
cvbs_out: create cdev cvbs
cvbs_out: cvbsout_probe OK
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
secmon: reserve_mem_size:0x300000
secmon secmon: assigned reserved memory node linux,secmon
secmon: clear_range:5100000 200000
secmon: get page:ffffffbf00140000, 5000
secmon: share in base: 0xffffffc0050fe000, share out base: 0xffffffc0050ff000
secmon: phy_in_base: 0x50fe000, phy_out_base: 0x50ff000
hdmitx: system: amhdmitx_probe start
hdmitx: system: Ver: 20181019
hdmitx: system: hdmitx_device.chip_type : 11
hdmitx: system: not find product desc
hdmitx: system: not find match pwr-ctl
hdmitx: system: not find drm_amhdmitx
hdmitx: system: hpd irq = 39
hdmitx: system: hdcp22_tx_skp failed to probe
hdmitx: system: hdcp22_tx_esm failed to probe
vout: vout1: register server: hdmitx_vout_server
vout: vout2: register server: hdmitx_vout2_server
hdmitx: hdmitx20: Mapped PHY: 0xffd00000
hdmitx: hdmitx20: Mapped PHY: 0xff634400
hdmitx: hdmitx20: Mapped PHY: 0xff900000
hdmitx: hdmitx20: Mapped PHY: 0xff800000
hdmitx: hdmitx20: Mapped PHY: 0xff63c000
hdmitx: hdmitx20: Mapped PHY: 0xffd00000
hdmitx: hdmitx20: Mapped PHY: 0xff608000
hdmitx: hdmitx20: Mapped PHY: 0xff600000
hdmitx: hdmitx20: Mapped PHY: 0xffe01000
hdmitx: hw: alread display in uboot 0x10
hdmitx: hw: avmute set to 1
hdmitx: system: fmt_attr 444,8bit
hdmitx: system: amhdmitx_probe end
amhdmitx: probe of amhdmitx failed with error 160757136
vout: create vout attribute OK
vout: vout_fops_create OK
vout: vout1: register server: nulldisp_vout_server
hdmitx: hdmitx_set_current_vmode[3455]
hdmitx: system: recalc before custombuilt 60 1
hdmitx: system: recalc after custombuilt 60 1
hdmitx: alread display in uboot
vout: init mode custombuilt set ok
vout: aml_tvout_mode_monitor
vout: aml_vout_probe OK
chip type:0x29
clocksource: Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 32768 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
UDP hash table entries: 2048 (order: 4, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 2832K
perf_event: read sys_cpu_status0_offset failed, ret = -22
armv8-pmu: probe of arm_pmu failed with error 1
workingset: timestamp_bits=62 max_order=20 bucket_order=0
exFAT: Version 1.2.9
Registering sdcardfs 0.1
ntfs: driver 2.1.32 [Flags: R/O].
fuse init (API version 7.26)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
io scheduler noop registered (default)
io scheduler deadline registered
io scheduler cfq registered
meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
meson-pwm ffd1b000.pwm: pwm pinmux : can't get pinctrl
random: fast init done
random: crng init done
gpiomem-aml ff634000.gpiomem: Initialised: Registers at 0xff634000
Unable to detect cache hierarchy for CPU 0
brd: module loaded
loop: module loaded
zram: Added device: zram0
libphy: Fixed MDIO Bus: probed
 REG0:Addr = ffffff8008393540
meson6-dwmac ff3f0000.ethernet: no reset control found
stmmac - user ID: 0x11, Synopsys ID: 0x37
 Ring mode enabled
 DMA HW capability register supported
 Normal descriptors
 RX Checksum Offload Engine supported
        COE Type 2
 TX Checksum insertion supported
 Wake-Up On Lan supported
drivers/amlogic/efuse/efuse_hw64.c:_efuse_read:196: read error!!!
eth%d: device MAC address 00:1e:06:42:66:bd
 Enable RX Mitigation via HW Watchdog Timer
libphy: stmmac: probed
eth%d: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00) active
eth%d: PHY ID 001cc916 at 7 IRQ POLL (stmmac-0:07)
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
md: linear personality registered for level -1
device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
ledtrig-cpu: registered to indicate activity on CPUs
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ashmem: initialized
ff803000.serial: clock gate not found
meson_uart ff803000.serial: ==uart0 reg addr = ffffff80083aa000
ff803000.serial: ttyS0 at MMIO 0xff803000 (irq = 30, base_baud = 1500000) is a meson_uart
meson_uart ff803000.serial: ttyS0 use xtal(24M) 24000000 change 0 to 115200
console [ttyS0] enabled
amlogic-new-usb2-v2 ffe09000.usb2phy: USB2 phy probe:phy_mem:0xffe09000, iomap phy_base:0xffffff80083ac000
amlogic-new-usb3-v2 ffe09080.usb3phy: USB3 phy probe:phy_mem:0xffe09080, iomap phy_base:0xffffff80083e9080
rtc-pcf8563 3-0051: rtc core: registered rtc-pcf8563 as rtc0
meson-remote: Driver init
meson-remote: remote_probe
meson-remote ff808040.rc: protocol = 0x1
meson-remote ff808040.rc: don't find the node <led_blink>
meson-remote ff808040.rc: led_blink = 0
meson-remote ff808040.rc: don't find the node <led_blink_frq>
meson-remote ff808040.rc: led_blink_frq  = 100
meson-remote ff808040.rc: platform_data irq =38
meson-remote ff808040.rc: custom_number = 4
meson-remote ff808040.rc: ptable->map_size = 50
meson-remote ff808040.rc: ptable->custom_name = amlogic-remote-1
meson-remote ff808040.rc: ptable->custom_code = 0xfb04
meson-remote ff808040.rc: ptable->release_delay = 80
meson-remote ff808040.rc: ptable->map_size = 53
meson-remote ff808040.rc: ptable->custom_name = amlogic-remote-2
meson-remote ff808040.rc: ptable->custom_code = 0xfe01
meson-remote ff808040.rc: ptable->release_delay = 80
meson-remote ff808040.rc: ptable->map_size = 17
meson-remote ff808040.rc: ptable->custom_name = amlogic-remote-3
meson-remote ff808040.rc: ptable->custom_code = 0xbd02
meson-remote ff808040.rc: ptable->release_delay = 80
meson-remote ff808040.rc: ptable->map_size = 12
meson-remote ff808040.rc: ptable->custom_name = hardkernel-remote
meson-remote ff808040.rc: ptable->custom_code = 0x4db2
meson-remote ff808040.rc: ptable->release_delay = 80
meson-remote ff808040.rc: default protocol = 0x1 and id = 0
meson-remote ff808040.rc: reg=0x0, val=0x1f40190
meson-remote ff808040.rc: reg=0x4, val=0x12c00c8
meson-remote ff808040.rc: reg=0x8, val=0x960050
meson-remote ff808040.rc: reg=0xc, val=0x480028
meson-remote ff808040.rc: reg=0x10, val=0x70fa0013
meson-remote ff808040.rc: reg=0x18, val=0x8616800
meson-remote ff808040.rc: reg=0x1c, val=0x9f00
meson-remote ff808040.rc: reg=0x20, val=0x0
meson-remote ff808040.rc: reg=0x24, val=0x0
meson-remote ff808040.rc: reg=0x28, val=0x0
input: aml_keypad as /devices/platform/ff808040.rc/input/input0
meson-remote: IR XMP protocol handler initialized
efuse efuse:  open efuse clk gate error!!
efusekeynum: 1
efusekeyname:            uuid   offset:     0   size:    32
efuse efuse: probe OK!
ion_dev soc:ion_dev: assigned reserved memory node linux,ion-dev
ge2d: ge2d_init_module
ge2d: ge2d_dev major:237
ge2d: clock source clk_ge2d_gate ffffffc0c94c4380
ge2d: clock clk_ge2d source ffffffc0c94c4400
ge2d: clock source clk_vapb_0 ffffffc0c94c4480
ge2d: ge2d init clock is 500000000 HZ, VPU clock is 666666656 HZ
ge2d: ge2d clock is 499 MHZ
ge2d: find address resource
ge2d: map io source 0x00000000ff940000,size=65536 to 0xffffff8008510000
ge2d: ge2d: pdev=ffffffc0cab1f000, irq=42, clk=ffffffc0c94c4380
ge2d: ge2d start monitor
ge2d: ge2d workqueue monitor start
amvideom vsync irq: 43
fb: osd_init_module
fb: viu vsync irq: 43
fb: viu2 vsync irq: 52
0x000000d8:Y=d8,U=0,V=0
0x000000d9:Y=d9,U=0,V=0
0x000000da:Y=da,U=0,V=0
0x000000db:Y=db,U=0,V=0
fb: osd_rdma_init: rdma_table p=0xcf608000,op=0xcf608000 , v=0xffffff80083f7000
rdma_register, rdma_table_addr ffffff80083f9000 rdma_table_addr_phy cf609000 reg_buf ffffffc0c9482000
rdma_register success, handle 2 table_size 4096
fb: osd_rdma_init:osd rdma handle = 2.
fb: mem_size: 0x800000
fb: mem_size: 0x4b80000
fb: mem_size: 0x100000
fb: mem_size: 0x100000
fb: mem_size: 0x800000
meson-fb meson-fb: assigned reserved memory node linux,meson-fb
fb: reserved memory base:0x000000007f800000, size:800000
fb: fb def : 1280 1024 1280 2048 32
fb: init fbdev bpp is:32
fb: malloc_osd_memory, cma:ffffff80099b14d0
fb: malloc_osd_memory, 1269, base:0x000000007f800000, size:8388608
fb: use ion buffer for fb memory, fb_index=0
meson-fb meson-fb: create ion_client ffffffc0c9454a80, handle=ffffffc0c9450d80
meson-fb meson-fb: ion memory(0): created fb at 0x00000000e5800000, size 75 MiB
fb: Frame buffer memory assigned at
fb:  0, phy: 0x00000000e5800000, vir:0xffffff8009a1f000, size=77312K

fb: logo_index=0,fb_index=0
fb: ---------------clear fb0 memory ffffff8009a1f000
fb: osd[0] canvas.idx =0x40
fb: osd[0] canvas.addr=0xe5800000
fb: osd[0] canvas.width=5120
fb: osd[0] canvas.height=2048
fb: osd[0] frame.width=1280
fb: osd[0] frame.height=1024
fb: osd[0] out_addr_id =0x1
Console: switching to colour frame buffer device 160x64
fb: osd[0] enable: 1 (swapper/0)
fb: set osd0 reverse as NONE
fb: osd probe OK
hdmitx: hdcp: hdmitx_hdcp_init
vout: vout2: create vout2 attribute OK
vout: vout2: vout2_fops_create OK
vout: vout2: register server: nulldisp_vout2_server
vout: vout2: init mode null set ok
vout: vout2: clktree_init
vout: vout2: aml_vout2_probe OK
DI: di_module_init ok.
DI: di_module_init: major 511
deinterlace deinterlace: assigned reserved memory node linux,di_cma
DI: CMA size 0x2800000.
pre_irq:67
post_irq:68
DI: di_probe allocate rdma channel 0.
di_get_vpu_clkb: get clk vpu error.
DI: vpu clkb <334000000, 667000000>
DI:enable vpu clkb.
0x000000dc:Y=dc,U=0,V=0
0x000000dd:Y=dd,U=0,V=0
0x000000de:Y=de,U=0,V=0
0x000000df:Y=df,U=0,V=0
0x000000e0:Y=e0,U=0,V=0
0x000000e1:Y=e1,U=0,V=0
0x000000e2:Y=e2,U=0,V=0
0x000000e3:Y=e3,U=0,V=0
0x000000f0:Y=f0,U=0,V=0
0x000000f1:Y=f1,U=0,V=0
0x000000f2:Y=f2,U=0,V=0
0x000000f3:Y=f3,U=0,V=0
0x000000f4:Y=f4,U=0,V=0
0x000000f5:Y=f5,U=0,V=0
0x000000f6:Y=f6,U=0,V=0
0x000000f7:Y=f7,U=0,V=0
0x000000f8:Y=f8,U=0,V=0
0x000000f9:Y=f9,U=0,V=0
0x000000fa:Y=fa,U=0,V=0
0x000000fb:Y=fb,U=0,V=0
0x000000fc:Y=fc,U=0,V=0
0x000000fd:Y=fd,U=0,V=0
0x000000fe:Y=fe,U=0,V=0
DI: support post write back 254.
DI: di_probe:Di use HRTIMER
di_probe:ok
aml_vecm_init:module init

 VECM probe start
Can't find  wb_sel.
hdr:Can't find  cfg_en_osd_100.
Can't find  tx_op_color_primary.
Can't find  vlock_en.
Can't find  vlock_mode.
Can't find  vlock_pll_m_limit.
Can't find  vlock_line_limit.
aml_vecm_probe: ok
meson-mmc: mmc driver version: 3.02, 2017-05-15: New Emmc Host Controller
meson-mmc: >>>>>>>>hostbase ffffff800850b000, dmode
meson-mmc: meson_mmc_probe() : success!
meson-mmc: >>>>>>>>hostbase ffffff8008525000, dmode
meson-mmc: gpio_cd = 1ca
meson-mmc: meson_mmc_probe() : success!
unifykey: storage in base: 0xffffffc005000000
unifykey: storage out base: 0xffffffc005040000
unifykey: storage block base: 0xffffffc005080000
unifykey: probe done!
unifykey: aml_unifykeys_init done!
sysled: module init
meson_wdt ffd0f0d0.watchdog: creat work queue for watch dog
meson_wdt ffd0f0d0.watchdog: AML Watchdog Timer probed done
dmc_monitor_probe
NET: Registered protocol family 17
Registered swp emulation handler
Registered cp15_barrier emulation handler
Registered setend emulation handler
dwc3 ff500000.dwc3: Configuration mismatch. dr_mode forced to host
meson-aml-mmc ffe07000.emmc: divider requested rate 200000000 != actual rate 199999997: ret=0
meson-mmc: Data 1 aligned delay is 0
meson-mmc: emmc: clk 199999997 tuning start
meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac
meson-mmc: emmc: rx_tuning_result[1] = 40
meson-mmc: emmc: rx_tuning_result[2] = 40
meson-mmc: emmc: rx_tuning_result[3] = 40
meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac
meson-mmc: emmc: best_win_start =1, best_win_size =3
meson-mmc: emmc: sd_emmc_regs->gclock=0x10000345,sd_emmc_regs->gadjust=0x22000
emmc: new HS200 MMC card at address 0001
emmc: clock 199999997, 8-bit-bus-width
 mmcblk0: emmc:0001 SDW32G 29.1 GiB
mmcblk0boot0: emmc:0001 SDW32G partition 1 4.00 MiB
mmcblk0boot1: emmc:0001 SDW32G partition 2 4.00 MiB
mmcblk0rpmb: emmc:0001 SDW32G partition 3 4.00 MiB
 mmcblk0: p1 p2
xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
xhci-hcd xhci-hcd.0.auto: hcc params 0x0228fe6c hci version 0x110 quirks 0x20010010
xhci-hcd xhci-hcd.0.auto: irq 22, io mem 0xff500000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
rtc-pcf8563 3-0051: setting system clock to 2019-06-21 13:32:49 UTC (1561123969)
dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: ffe09000, ctrl: 0
dwc_otg: Core Release: 3.30a
dwc_otg: Setting default values for core params
dwc_otg: curmode: 0, host_only: 0
dwc_otg: Using Buffer DMA mode
dwc_otg: OTG VER PARAM: 1, OTG VER FLAG: 1
dwc_otg: Working on port type = SLAVE
dwc_otg: Dedicated Tx FIFOs mode
gxbb_pm: enter meson_pm_probe!
gxbb_pm: meson_pm_probe done
Freeing unused kernel memory: 1472K

Although I see that the correct parameters have been passed (aparently from autodetection) to the kernel and modules, the screen remains in sleep mode until the first choice is booted. Hope I'm not ruining your weekend :). Let me know if you need more info.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 21, 2019 11:00 pm

@mad_ady, thank you for the info, very informative.
You are worried about my weekend not to ruin, thank you...but you already did.... :)
Let me look into more carefully later since it's Drawing Friday. Yay!!

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Fri Jun 21, 2019 11:03 pm

tobetter wrote:
Fri Jun 21, 2019 2:13 am
Thank you for your try and interesting if EmuELEC can work with Petitboot.

I now realized that the file name must be spiboot.img, not spiupdate.img. It's my bad, sorry about it. Could you please do rename it to spiboot.img again?
no probs, i will give it another go tonight :-)
These users thanked the author binhex for the post:
andy5macht (Sat Jun 22, 2019 5:01 am)

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Sat Jun 22, 2019 1:38 am

@mad_ady check your power supply....
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Sat Jun 22, 2019 1:44 am

phaseshifter wrote:@mad_ady check your power supply....
Why? What's wrong with it? The N2 doesn't show signs of unstable power, just a less than standard display.

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Sat Jun 22, 2019 1:58 am

sozz my bad..um i also had issues when i chose other display modes trying to get it to boot at 800x480 it would not get passed petitboot and i had to edit my hdd on my win box..so i dont know what is going on there..!!
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Sat Jun 22, 2019 4:00 am

Most likely the script that parses the kernel command line arguments doesn't apply the settings correctly in the amlogic hdmi driver. Though I do see correct output over serial. I'm sure @tobetter knows more than we about the internal init process. If I had more time I would have looked more at the init scripts...

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sat Jun 22, 2019 5:21 am

mad_ady wrote:
Sat Jun 22, 2019 4:00 am
Most likely the script that parses the kernel command line arguments doesn't apply the settings correctly in the amlogic hdmi driver. Though I do see correct output over serial. I'm sure @tobetter knows more than we about the internal init process. If I had more time I would have looked more at the init scripts...
@mad_ady, I have two patches which are to rebuild the boot args and DTB when real OS is started. This is because of that the boot.ini parser in Petitboot does not execute the script like U-boot, but gather the booting information to start OS. I am expecting to release it in RC4 maybe by the end of next week with U-boot update hopefully.

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Sat Jun 22, 2019 12:47 pm

No worries. I'll try to test them before I go on vacantion.

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Sat Jun 22, 2019 12:55 pm

sorry guys i`ve been out of the loop and a lot of this stuff goes over my head at times...phase...

but always look forward to upgrades.but.sometimes i have trouble applying them..phase...
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Tue Jun 25, 2019 5:09 am

Hi, so i managed to get around to changing the name of the file so spiboot.img and it worked yay!, i saw the petitboot menu come up, however i have an issues/question:-

1. if i leave the sd-card in the slot with the spiboot.img file then i cannot move around the petitboot menu, none of the usb attached keyboard keys respond. if however i take the sd-card out and let petitboot now off the flashed memory module then i can navigate the petitboot menu, however i then can obviously not boot from the media, is it best to delete the spiboot.img file after its been flashed to eprom (or whatever it is), not sure of the procedure yet.
2. my second issue is rather trivial, but i thought i should mention it, on a 4k tv screen the text is definitely horizontally compressed, as if the resolution is not correct for the text, its readable but definitely present.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Tue Jun 25, 2019 8:40 am

Good to heare you can update the SPI flash memory. Technically the file spiboot.img must be removed once updating is finished otherwise it will start to update again. Somehow it's not removed, so...just remove it.
I also realized the text problem on 4K and have noted to fix it soon.

Thank you for sharing the problems.
Have fun with ODROID.

"Tapatalk wishes you to have fun with ODROID"


binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Tue Jun 25, 2019 6:15 pm

ok so i managed to have a further investigation and can confirm i have a repeatable issue where inserting the micro-sd card with EmuELEC on it with no spiboot.img (or spiupdate.img) present results in the petitboot screen displaying on screen but you cannot select any of the menu options (using wired usb keyboard), the only key that does anything is the return key, and pressing the return key strangely makes all the petitboot menu text scroll up the screen 1 line at a time, if you keep pressing return then you eventually end up with no text showing at all (black screen), at that point the only options are ctrl+alt+del or pull the power.

one thing i did note is that when it gets into this state that there are no bootable device shown at the top of the menu, so it doesn't even display CoreELEC (installed on eMMC) as a bootable option, if i power down and remove the micro-sd card and then boot again then i see the petitboot menu and can select any of the options, including the detected CoreELEC installation as a boot device and it will boot fine. Maybe pietitboot is failing to identify EmuELEC as a bootable device and thus it gets stuck at this point, unable to display other boot options such as CoreELEC and preventing any menu selections.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Tue Jun 25, 2019 10:06 pm

binhex wrote:ok so i managed to have a further investigation and can confirm i have a repeatable issue where inserting the micro-sd card with EmuELEC on it with no spiboot.img (or spiupdate.img) present results in the petitboot screen displaying on screen but you cannot select any of the menu options (using wired usb keyboard), the only key that does anything is the return key, and pressing the return key strangely makes all the petitboot menu text scroll up the screen 1 line at a time, if you keep pressing return then you eventually end up with no text showing at all (black screen), at that point the only options are ctrl+alt+del or pull the power.

one thing i did note is that when it gets into this state that there are no bootable device shown at the top of the menu, so it doesn't even display CoreELEC (installed on eMMC) as a bootable option, if i power down and remove the micro-sd card and then boot again then i see the petitboot menu and can select any of the options, including the detected CoreELEC installation as a boot device and it will boot fine. Maybe pietitboot is failing to identify EmuELEC as a bootable device and thus it gets stuck at this point, unable to display other boot options such as CoreELEC and preventing any menu selections.
Thank you for your investigation, I will look into more it's probably because of an error while parsing a boot script in EmuELEC. Could you let me know where you have download the image and which version you are trying?

"Tapatalk wishes you to have fun with ODROID"


binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Tue Jun 25, 2019 10:45 pm

tobetter wrote:
Tue Jun 25, 2019 10:06 pm
Could you let me know where you have download the image and which version you are trying?

"Tapatalk wishes you to have fun with ODROID"
sure, its the current latest github 'release' link:- https://github.com/shantigilbert/EmuELE ... tag/v2.5.3
its the ng-arm version (obviously for the N2)

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Tue Jun 25, 2019 11:44 pm

binhex wrote:
Tue Jun 25, 2019 10:45 pm
tobetter wrote:
Tue Jun 25, 2019 10:06 pm
Could you let me know where you have download the image and which version you are trying?

"Tapatalk wishes you to have fun with ODROID"
sure, its the current latest github 'release' link:- https://github.com/shantigilbert/EmuELE ... tag/v2.5.3
its the ng-arm version (obviously for the N2)
Thanks, I've attached the file boot.ini which you can replace with. Please do back up the original one and copy the file. I propose the change to CoreELEC and it's accepted but EmuELEC should be updated with the same. It would be nice to let me know if it works for you, I will send the change to the EmuELEC maintainer, @Shanti.

EDIT:
boot.ini
(1.75 KiB) Downloaded 42 times
Last edited by tobetter on Wed Jun 26, 2019 2:46 am, edited 2 times in total.

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Wed Jun 26, 2019 2:04 am

tobetter wrote:
Tue Jun 25, 2019 11:44 pm
Thanks, I've attached the file boot.ini which you can replace with. Please do back up the original one and copy the file. I propose the change to CoreELEC and it's accepted but EmuELEC should be updated with the same. It would be nice to let me know if it works for you, I will send the change to the EmuELEC maintainer, @Shanti.
ok np, i will try and do the change tonight and let you know, thanks for your help.

edit - sorry i must be going blind i cant see the link to the boot.ini

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Wed Jun 26, 2019 2:47 am

binhex wrote:
Wed Jun 26, 2019 2:04 am
tobetter wrote:
Tue Jun 25, 2019 11:44 pm
Thanks, I've attached the file boot.ini which you can replace with. Please do back up the original one and copy the file. I propose the change to CoreELEC and it's accepted but EmuELEC should be updated with the same. It would be nice to let me know if it works for you, I will send the change to the EmuELEC maintainer, @Shanti.
ok np, i will try and do the change tonight and let you know, thanks for your help.

edit - sorry i must be going blind i cant see the link to the boot.ini
It must be my bad, the boot.ini is attached again.

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Wed Jun 26, 2019 6:36 am

tobetter wrote:
binhex wrote:
Wed Jun 26, 2019 2:04 am
tobetter wrote:
Tue Jun 25, 2019 11:44 pm
Thanks, I've attached the file boot.ini which you can replace with. Please do back up the original one and copy the file. I propose the change to CoreELEC and it's accepted but EmuELEC should be updated with the same. It would be nice to let me know if it works for you, I will send the change to the EmuELEC maintainer, @Shanti.
ok np, i will try and do the change tonight and let you know, thanks for your help.

edit - sorry i must be going blind i cant see the link to the boot.ini
It must be my bad, the boot.ini is attached again.
Perfect yes that boot.ini solved the problem and I can now boot either coreelec or emuelec with no issues, awesome job!

Sent from my EML-L29 using Tapatalk


User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Wed Jun 26, 2019 8:40 am

binhex wrote:
Wed Jun 26, 2019 6:36 am
tobetter wrote:
binhex wrote:
Wed Jun 26, 2019 2:04 am
tobetter wrote:
Tue Jun 25, 2019 11:44 pm
Thanks, I've attached the file boot.ini which you can replace with. Please do back up the original one and copy the file. I propose the change to CoreELEC and it's accepted but EmuELEC should be updated with the same. It would be nice to let me know if it works for you, I will send the change to the EmuELEC maintainer, @Shanti.
ok np, i will try and do the change tonight and let you know, thanks for your help.

edit - sorry i must be going blind i cant see the link to the boot.ini
It must be my bad, the boot.ini is attached again.
Perfect yes that boot.ini solved the problem and I can now boot either coreelec or emuelec with no issues, awesome job!

Sent from my EML-L29 using Tapatalk
Thank you for the confirmation, I will ask for update to the maintainer.
Have fun with ODROID.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Thu Jun 27, 2019 1:49 am

201906
I've uploaded new update of Petitboot update, https://drive.google.com/open?id=1Mhsjz ... kNVi4t-jzg. The file must be copied as spiboot.img to the first partition in your SD card, not eMMC. In order to update properly, the boot select switch must be placed to SPI and must do a power cycle, unless ODROID-N2 will keep boot MMC cards.
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

What's improved:
  • Keep having the previous features and fixed minor bugs.
  • Added to parse and update the device tree for OS. Some OS image has the feature to change the device tree on booting phase based on user option. For example, heartbeat blue LED can be permantly off by rebuilding the device tree before Linux kernel start on booting while default is active in the device tree file - *.dtb or dtb.img.
  • Added to pass the display parameter for OS. The previous version passes the display resolution same as Petitboot uses but a user or an OS wants to set a specific display resolution which is set in boot.ini. This requires to pass the resolution through Linux kernel command line and Petitboot reassemble it.
  • CEC wake-up feature is added to Petitboot bootloader but this does not mean every single OS will support CEC features by nature. CEC wake-up only can happen when the OS sets a decent config to the bootloader.
  • Added to scan the boot script the /boot directory as well as / in the first partition, I observed that Armbian image has a single partition and its boot script was in /boot.
.

Known issues:
  • Petitboot UI would be stretched on a 4K display. This is already known issue but not figured out while resolving the display resolution issue in "What's improved". I'd like to make it better and would fix it later if there is some report for the display issue. Since 4K is too much wide to display Petitboot, the actual resolution will be 1080P.
  • Have not been fixed the minor issues of former versions reported by users while improving the booting features. Not having more issues reported after RC3 but will keep in mind to fix such minor issues whenever reported.
  • Remote wake up would not work with some OS
Side note for users waiting for TV CEC on/off:
I understand that there is a huge demand about CEC on/off feature and ODROID still has a problem with it. Recently, I've found the patches in CoreELEC (super thanks to Portish at CoreELEC team!!) and merged into Hardkernel's U-boot. It has been tested with LG Smart TV and Samsung one, not with any other brand yet. Maybe not smooth but works with Hardkernel's Android (WIP by end of this week). CoreELEC also has been tested but nightly build would not work since the currently it has suspend/resume issue. I've submitted the patches to fix the issue today so it would work back soon.

I expected to fix more issues such as network support which might be not required (?). Since I have to allocate myself to some other works, I would not spend my time to Petitboot for a couple of weeks or a month unless no major issue but will keep responding. :)
IMG_20190627_0155308.jpg
IMG_20190627_0155308.jpg (318.34 KiB) Viewed 2608 times
These users thanked the author tobetter for the post (total 2):
XOR (Sat Jun 29, 2019 6:19 am) • 1917 (Sun Jun 30, 2019 1:21 am)

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Thu Jun 27, 2019 3:10 am

giving it a try now.....i think that any update is good.... however i dont run multiple opp sys`s...but i still like to keep things up to date...

Hmmm seems to be working it booted up my ssd ..i guess others will follow..no need for the sd-card for memory any more so it would seem..i duuno sometimes it`s all over my head...

EDIT: if you want your settings to still be saved use the sd-card as backup memory..that is what i found...as i firstly edited the spi configuration it did not save my preferences..so i slotted the sd-card back in..it would seem that you still need the spi selector in the spi mode but sd-card as extra men to save settings...
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Sholander » Thu Jun 27, 2019 11:28 pm

phaseshifter wrote:
Thu Jun 27, 2019 3:10 am
EDIT: if you want your settings to still be saved use the sd-card as backup memory..that is what i found...as i firstly edited the spi configuration it did not save my preferences..so i slotted the sd-card back in..it would seem that you still need the spi selector in the spi mode but sd-card as extra men to save settings...
Hi, what do you have on uSD card when it saves settings?
I have CoreElec on my uSD card, but cannot get the settings I make in Petitboot to be saved...

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Fri Jun 28, 2019 12:39 am

Sholander wrote:
phaseshifter wrote:
Thu Jun 27, 2019 3:10 am
EDIT: if you want your settings to still be saved use the sd-card as backup memory..that is what i found...as i firstly edited the spi configuration it did not save my preferences..so i slotted the sd-card back in..it would seem that you still need the spi selector in the spi mode but sd-card as extra men to save settings...
Hi, what do you have on uSD card when it saves settings?
I have CoreElec on my uSD card, but cannot get the settings I make in Petitboot to be saved...
I can answer this, the settings get stored in a file named petitboot.cfg which will be located in the same partition that you copied spiboot.img to, obviously if you switch micro SD then you will need to copy that file in order to maintain your settings.

Sent from my EML-L29 using Tapatalk


Ozarks
Posts: 7
Joined: Fri Jun 28, 2019 3:47 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Ozarks » Fri Jun 28, 2019 3:50 pm

Can Petitboot manage booting multiple OS's from a single source?

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 28, 2019 3:59 pm

What do you mean by single source? One storage? If so, I would say "Probably Yes if you can manage the source to install multiple OS" .

"Tapatalk wishes you to have fun with ODROID"

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by binhex » Fri Jun 28, 2019 6:17 pm

hi @tobetter, i have a few questions for you, i hope you dont mind:-

1. If i remove the micro-sd card that currently has the petitboot.cfg file what does petitboot do?, does it use the default settings or is the petitboot.cfg somehow copied up to the spi boot flash chip? i have altered the boot timeout to 5 secs and it seems to me like this setting has been retained even if the petitboot.cfg is not present, note i did not power cycle the unit so perhaps its still in memory?.

2. is there any way to hide the ugly loading screen you see before petitboot shows the menu?, if not no worries, its a VERY minor niggle just thought i would ask.

3. with 201906 do we need to modify the coreelec boot.ini?, and if it is required and not done then what 'hardware features' will be missing?, coreelec seems to boot fine for me with this build so im not sure what features (if any) i am missing.

"For CE users:
I indicated that CE team has custom U-boot change which improves the hardware features and boot config is a bit different from HK's one. In order to make CE boot.ini boot by Petitboot, it has to be modified to be recognized and this is my change for the reference. I would communicate with CE team how this change can be applied without features regression."

on another topic, PXE boot (as in network boot) would be pretty awesome, i saw you did mention this so i thought i would just add a +1 to this and hope you get time to work on it, thank you for your awesome work so far, petitboot has def increased the value i am getting from my N2 :-)

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Fri Jun 28, 2019 8:33 pm

binhex wrote:
Fri Jun 28, 2019 6:17 pm
hi @tobetter, i have a few questions for you, i hope you dont mind:-
I will try to respond if I can unless you don't abuse me. :)
1. If i remove the micro-sd card that currently has the petitboot.cfg file what does petitboot do?, does it use the default settings or is the petitboot.cfg somehow copied up to the spi boot flash chip? i have altered the boot timeout to 5 secs and it seems to me like this setting has been retained even if the petitboot.cfg is not present, note i did not power cycle the unit so perhaps its still in memory?.
The current version uses the default value which is in U-boot if petitboot.cfg is missing. I was thinking to save it when petitboot.cfg is discovered and remove it, but I was not able to remove 'petitboot.cfg'. Hmmmm....
2. is there any way to hide the ugly loading screen you see before petitboot shows the menu?, if not no worries, its a VERY minor niggle just thought i would ask.
This is one thing what I expected to figure out before the last version to display a logo. Due to the less space of SPI flash memory, I couldn't. For sure, I also hate not to show anything on booting.
3. with 201906 do we need to modify the coreelec boot.ini?, and if it is required and not done then what 'hardware features' will be missing?, coreelec seems to boot fine for me with this build so im not sure what features (if any) i am missing.
I've asked CE team to change the default boot.ini in their release and gratefully they accept it. So further release you never need to change the boot.ini. Even EmulELEC will be the same since both *ELEC uses the same build system. I have no idea about other OS maintainers if they change U-boot or not, but I've found CE team made their custom feature for remote and CEC features on top of HK implementation and they could not be compatible between HK's U-boot and CE's U-boot. Recently, I've patched CEC features from CE U-boot which was not supported in HK U-boot and they work. So one hardware feature is resolved, the current missing custom feature is remote what CE team made...so wake up with remote won't work if you turn off from CE but it will work if you turn off from HK's Ubuntu or Android. This is thing what I mean the hardware features could be missing after using Petitboot.
"For CE users:
I indicated that CE team has custom U-boot change which improves the hardware features and boot config is a bit different from HK's one. In order to make CE boot.ini boot by Petitboot, it has to be modified to be recognized and this is my change for the reference. I would communicate with CE team how this change can be applied without features regression."

on another topic, PXE boot (as in network boot) would be pretty awesome, i saw you did mention this so i thought i would just add a +1 to this and hope you get time to work on it, thank you for your awesome work so far, petitboot has def increased the value i am getting from my N2 :-)
Actually, PXE boot is already supported in U-boot but it's way better to do so with UI. Earlier I and Joy had struggled to reduce the kernel size and that time network protocol also had been removed in the kernel, then later we made to add IPv4 to Linux kernel instead of removing another kernel features not necessary at all for a boot manager. The thing is that I do not know how Petitboot works for PXE like what I struggled to support the boot entries and autoboot. I may need some time to study the code from time to time, for personal interesting and the vision of SBC what I wish, PXE and network support is the mandatory feature.

Thank you for your great interesting and let me keep doing some improvement, but maybe slowly.
These users thanked the author tobetter for the post:
binhex (Fri Jun 28, 2019 9:19 pm)

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by Sholander » Fri Jun 28, 2019 9:54 pm

binhex wrote:
Fri Jun 28, 2019 12:39 am
I can answer this, the settings get stored in a file named petitboot.cfg which will be located in the same partition that you copied spiboot.img to, obviously if you switch micro SD then you will need to copy that file in order to maintain your settings.
Tnx, silly me how I missed that :)

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Fri Jun 28, 2019 10:22 pm

does anybody foresee the future having the nand chip size adjustment ...16Mb perhaps in a later release N-2 rev board...this would solve many issues ...??

perhaps this is not the correct place for this post @odroid pls move if need be.....
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

XOR
Posts: 4
Joined: Wed May 22, 2019 12:30 am
languages_spoken: english
ODROIDs: N2
Has thanked: 20 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by XOR » Sat Jun 29, 2019 8:52 pm

#Armbian #boot.ini #USB

@tobetter thank you very much for this update! I can now run Armbian from USB without any SD or MMC, yay!

I had to move boot.ini from `/boot` to `/` and update its content based on boot.ini you shared here, thanks for that too! – attaching it for others to use.

One funky thing thought, as soon as system starts to boot, screen gets blank until reconnected (I solve it by switching screen to other input and then back). It's 4k screen. To disable screen autodetect didn't help. It doesn't bother me, it's just FYI.

Love the autoboot from USB!
Attachments
boot.ini
(4.37 KiB) Downloaded 46 times

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sat Jun 29, 2019 9:04 pm

XOR wrote:
Sat Jun 29, 2019 8:52 pm
#Armbian #boot.ini #USB

@tobetter thank you very much for this update! I can now run Armbian from USB without any SD or MMC, yay!

I had to move boot.ini from `/boot` to `/` and update its content based on boot.ini you shared here, thanks for that too! – attaching it for others to use.

One funky thing thought, as soon as system starts to boot, screen gets blank until reconnected (I solve it by switching screen to other input and then back). It's 4k screen. To disable screen autodetect didn't help. It doesn't bother me, it's just FYI.

Love the autoboot from USB!
Thank you for sharing your experience, since I've observed that Armbian image put the boot.ini to /boot so I've added Petitboot can scan /boot/boot.ini when /boot.ini is missing...but still does not work? Did you make any change of the boot.ini attached?

phaseshifter
Posts: 3493
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 39 times
Been thanked: 42 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by phaseshifter » Sat Jun 29, 2019 11:42 pm

@XOR
screen gets blank until reconnected (I solve it by switching screen to other input and then back). It's 4k screen
this i have seen soo many times now and there are several threads concerning this issue...i even have the issue..with one of my screens ..but not a 4k screen...

have a look trough the topics...i cannot say weather it is the odroid at fault or the screen...i guess it must be the screen by default but yet the board works fine on my other screen...

i have 2 screens both much the same same brand and size..my odriod works as it should on the newer screen but the older screen i have to flip the signal switch for it to work..
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

1917
Posts: 11
Joined: Wed May 01, 2019 3:51 pm
languages_spoken: english, russian
ODROIDs: N2 4Gb
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by 1917 » Sun Jun 30, 2019 1:48 am

@tobetter
Thank you, I can now successfully boot from an SSD attached via a SATA-USB3 enclosure with the updated Petitboot. No extra setup was needed, the stock boot.ini did the trick.

Regarding the inability to access the SPI flash while using eMMC -- I wonder whether that SPI/eMMC bus multiplexing is a one-time only change or not. I mean, is it controlled by some sort of a lockable register which cannot be written afterwards?
Basically, Petitboot's settings are very small in size and thus can be flashed to the SPI flash almost immediately. So, if we can switch SPI/eMMC bus usage more than once then we could possibly temporarily switch the bus back to SPI, flash the tiny bit of Pettiboot's settings data, and then switch the bus to eMMC -- while holding the system monopolized during this sequence. Any chance to control the SPI/eMMC bus multiplexing on post-boot stages?
These users thanked the author 1917 for the post:
mad_ady (Sun Jun 30, 2019 3:35 am)

1917
Posts: 11
Joined: Wed May 01, 2019 3:51 pm
languages_spoken: english, russian
ODROIDs: N2 4Gb
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by 1917 » Sun Jun 30, 2019 2:18 am

According to the datasheet and schematics, this multiplexing is controlled by GPIO-like pins (Boot_X), their related registers seems to be RW...

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

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by mad_ady » Sun Jun 30, 2019 3:36 am

+1 for investigating if one can store petitboot settings in spi or emmc. I don't plan on using sd.
Last edited by mad_ady on Sun Jun 30, 2019 3:36 am, edited 1 time in total.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sun Jun 30, 2019 2:11 pm

1917 wrote:
Sun Jun 30, 2019 2:18 am
According to the datasheet and schematics, this multiplexing is controlled by GPIO-like pins (Boot_X), their related registers seems to be RW...
Technically the signals for SPI and eMMC can be multiplexed and which is been tested in U-boot. After booting Linux, the problem is that both drivers cannot be loaded and run simultaneously, the prior device must be shut down in order to run another one if my understanding of Linux device driver model is correct. Maybe I am overthinking, Petitboot is running on top of Linux, it cannot break the way how the device and file system must work. Also must consider how the device tree needs to be changed for two devices which share the hardware bus, even I don't want to add the code to access SPI flash memory to eMMC driver which is tricky and it also brings another problem.

Actually, I already have a plan for saving Petitboot config to SPI flash memory. Which is to fork the kernel branch for Petitboot apart from the generic Linux and will make eMMC and SPI driver as a module such that mainly eMMC driver will upon booting and removed temporarily when Petitboot saves the config. There are other things to resolve for saving config after this but the rest is simple relatively.

wdehoog
Posts: 11
Joined: Wed Jun 19, 2019 5:24 am
languages_spoken: english
ODROIDs: n2
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by wdehoog » Sun Jun 30, 2019 7:12 pm

@tobetter For me the the 201906 version is not working.

1. It does not show my armbian bootable device but when I create a link in / to /boot/boot.ini it lists two bootable partitions.
2. Every key I press on my keyboard makes petitiboot jump to shell or reboots the N2. I am using a Logitech K400 USB wireless keyboard.
( The shell is also fishy. It looks like the end-of-line characters are missing or wrong)

Reflashing rc3 makes it work again.

User avatar
tobetter
Posts: 4024
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: 43 times
Been thanked: 177 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Unread post by tobetter » Sun Jun 30, 2019 7:22 pm

wdehoog wrote:
Sun Jun 30, 2019 7:12 pm
@tobetter For me the the 201906 version is not working.

1. It does not show my armbian bootable device but when I create a link in / to /boot/boot.ini it lists two bootable partitions.
2. Every key I press on my keyboard makes petitiboot jump to shell or reboots the N2. I am using a Logitech K400 USB wireless keyboard.
( The shell is also fishy. It looks like the end-of-line characters are missing or wrong)

Reflashing rc3 makes it work again.
I experienced but with another OS image, maybe I would try the same one what you tried.
Could you let me know the exact file name of your Armbian?

Post Reply

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 1 guest