Petitboot, yet another bootloader based on KEXEC

[xabolcs]

Petitboot is running on Linux, so it does not care of it. As long as partions are accessible by Linux kernel you will see them. FYI, probably GPT would work as well if I remember correctly.

"Tapatalk wishes you to have fun with ODROID"

I was able to test it! Works like charm!

Code: Select all

 Petitboot (dev.20191104)                                  Hardkernel ODROID-N2
 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
  [Disk: mmcblk0p5 / BA12-21EE]        
    Debian GNU/Linux 10 (Buster, eMMC, mainline)
  [Disk: mmcblk0p1 / 5DAF-525D]
    Android Pie (32Bit, eMMC)

  System information
  System configuration
 *System status log                                                        
  Language
  Rescan devices
  Retrieve config from URL
  Plugins (0)
  Exit to shell






 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
 Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
 

[istanbulls]

Can you share the kernel log when Ubuntu Mate is starting?

is it possible?

Code: Select all

[    5.164685] asoc-aml-card auge_sound: dit-hifi <-> SPDIF-B mapping ok
[    5.171052] set mclk:12288000, mpll:24576000, get mclk:12287994, mpll:24575987
[    5.171055] aml_dai_set_tdm_slot(), txmask(0x3), rxmask(0x3)
[    5.171056] 	lanes_out_cnt(1), lanes_in_cnt(1)
[    5.171057] 	lanes_oe_out_cnt(0), lanes_oe_in_cnt(0)
[    5.171058] 	lanes_lb_cnt(0)
[    5.171059] 	slots(2), slot_width(32)
[    5.171064] asoc aml_dai_set_tdm_fmt, 0x4011, ffffffc0ca377718, id(2), clksel(2)
[    5.171067] master_mode(1), binv(1), finv(1) out_skew(2), in_skew(3)
[    5.177767] asoc-aml-card auge_sound: T9015-audio-hifi <-> TDM-C mapping ok
[    5.184642] set normal 512 fs /4 fs
[    5.184653] 	 set spdifout clk:6144000, mpll:24576000
[    5.184655] 	 get spdifout clk:6143997, mpll:24575987
[    5.184656] aml_dai_set_spdif_fmt , fmt 0x4010
[    5.184687] aml_spdif_new spdif_a, clk continuous:1
[    5.184688] spdifout_play_with_zerodata_free, spdif id:0
[    5.184816] asoc-aml-card auge_sound: dit-hifi <-> SPDIF mapping ok
[    5.191515] snd_card_add_kcontrols card:ffffffc0c9dfc818
[    5.196516] effect_v2 is not init
[    5.199980] Not init vad
[    5.199981] Failed to add VAD controls
[    5.203886] eq/drc v1 function enable
[    5.235469] add line-out mute controls
[    5.235783] dwc3 ff500000.dwc3: Configuration mismatch. dr_mode forced to host
[    5.243724] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    5.246754] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    5.254560] usb: xhci: determined sg_tablesize: 4294967295
[    5.260177] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228fe6c hci version 0x110 quirks 0x20010010
[    5.268878] xhci-hcd xhci-hcd.0.auto: irq 23, io mem 0xff500000
[    5.274979] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.281856] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.289219] usb usb1: Product: xHCI Host Controller
[    5.294247] usb usb1: Manufacturer: Linux 4.9.196-63 xhci-hcd
[    5.300138] usb usb1: SerialNumber: xhci-hcd.0.auto
[    5.305370] hub 1-0:1.0: USB hub found
[    5.309078] hub 1-0:1.0: 2 ports detected
[    5.313359] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    5.318863] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    5.326660] usb: xhci: determined sg_tablesize: 4294967295
[    5.332140] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.340387] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    5.347286] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.354654] usb usb2: Product: xHCI Host Controller
[    5.359679] usb usb2: Manufacturer: Linux 4.9.196-63 xhci-hcd
[    5.365571] usb usb2: SerialNumber: xhci-hcd.0.auto
[    5.370764] hub 2-0:1.0: USB hub found
[    5.374509] hub 2-0:1.0: 1 port detected
[    5.378801] hctosys: unable to open rtc device (rtc0)
[    5.383938] dwc_otg ff400000.dwc2_a: dwc_otg_driver_probe(ffffffc0ca212c00)
[    5.383950] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: ffe09000, ctrl: 0
[    5.392443] dwc_otg ff400000.dwc2_a: base=0xffffff8008d00000
[    5.392446] dwc_otg ff400000.dwc2_a: dwc_otg_device=0xffffffc003197400
[    5.492554] dwc_otg: Core Release: 3.30a
[    5.492570] dwc_otg: Setting default values for core params
[    5.496730] dwc_otg: curmode: 0, host_only: 0
[    5.501239] dwc_otg ff400000.dwc2_a: DMA config: BURST_DEFAULT
[    5.513366] dwc_otg: Using Buffer DMA mode
[    5.513383] dwc_otg: OTG VER PARAM: 1, OTG VER FLAG: 1
[    5.517281] dwc_otg: Working on port type = SLAVE
[    5.522157] dwc_otg: Dedicated Tx FIFOs mode
[    5.527428] meson_cdev probe
[    5.529626] meson_cdev index: 0
[    5.532962] meson_cdev index: 1
[    5.536222] thermal: no cluster id, cpucore as one cooldev
[    5.541822] meson_cdev index: 2
[    5.545104] cpucore_cooling_register, max_cpu_core_num:6
[    5.550562] cpucore_cooling_register, clutser[1] core num:4
[    5.556281] cpucore_cooling_register, clutser[0] core num:2
[    5.562053] meson_cdev index: 3
[    5.565307] meson_cdev index: 4
[    5.568612] find tzd id: 0
[    5.571546] find tzd id: 0
[    5.574381] find tzd id: 0
[    5.577212] meson_cdev probe done
[    5.580705] gxbb_pm: enter meson_pm_probe!
[    5.584915] amlogic-new-usb2-v2 ffe09000.usb2phy: ---Set port(0) tuning for host cf(xhci_hub_control)--
[    5.594540] gxbb_pm: meson_pm_probe done
[    5.598687] ALSA device list:
[    5.601612]   #0: AML-AUGESOUND
[    5.604974] meson_uart ff803000.serial: ttyS0 use xtal(24M) 24000000 change 115200 to 115200
[    5.643435] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    5.715427] prepare_namespace() wait 79
[    5.716391] EXT4-fs (mmcblk1p2): couldn't mount as ext3 due to feature incompatibilities
[    5.738674] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    5.741310] VFS: Mounted root (ext4 filesystem) on device 179:130.
[    5.755688] devtmpfs: mounted
[    5.756969] Freeing unused kernel memory: 4864K
[    5.785771] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610
[    5.786994] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.794295] usb 1-1: Product: USB2.1 Hub
[    5.798352] usb 1-1: Manufacturer: GenesysLogic
[    5.812358] hub 1-1:1.0: USB hub found
[    5.812606] hub 1-1:1.0: 4 ports detected
[    5.903543] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[    5.926022] usb 2-1: New USB device found, idVendor=05e3, idProduct=0620
[    5.927246] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.934551] usb 2-1: Product: USB3.1 Hub
[    5.938604] usb 2-1: Manufacturer: GenesysLogic
[    5.956331] hub 2-1:1.0: USB hub found
[    5.956638] hub 2-1:1.0: 4 ports detected
[    6.155437] usb 1-1.1: new full-speed USB device number 3 using xhci-hcd
[    6.281574] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c534
[    6.282972] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.290436] usb 1-1.1: Product: USB Receiver
[    6.294868] usb 1-1.1: Manufacturer: Logitech
[    6.318942] systemd[1]: System time before build time, advancing clock.
[    6.325887] input: Logitech USB Receiver as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C534.0001/input/input2
[    6.363491] usb 2-1.3: new SuperSpeed USB device number 3 using xhci-hcd
[    6.384369] usb 2-1.3: New USB device found, idVendor=0080, idProduct=a001
[    6.385765] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.393609] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-xhci-hcd.0.auto-1.1/input0
[    6.405981] usb 2-1.3: Product: External USB 3.0
[    6.411557] input: Logitech USB Receiver as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.1/1-1.1:1.1/0003:046D:C534.0002/input/input3
[    6.424257] usb 2-1.3: Manufacturer: TOSHIBA
[    6.428670] usb 2-1.3: SerialNumber: 201503310007F
[    6.436720] scsi host0: uas
[    6.441528] scsi 0:0:0:0: Direct-Access     TO Exter nal USB 3.0      0204 PQ: 0 ANSI: 6
[    6.471767] hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-xhci-hcd.0.auto-1.1/input1
[    6.488118] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    6.488319] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[    6.488849] NET: Registered protocol family 10
[    6.500311] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    6.500820] ip_tables: (C) 2000-2006 Netfilter Core Team
[    6.506844] cgroup: cgroup2: unknown option "nsdelegate"
[    6.517098] sd 0:0:0:0: [sda] Write Protect is off
[    6.521443] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[    6.521767] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    6.530756] xhci-hcd xhci-hcd.0.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[    6.540313] xhci-hcd xhci-hcd.0.auto: @00000000cf612c40 00000000 00000000 1b000000 04078001
[    6.549118] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[    6.561545]  sda:
[    6.563289] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.583434] usb 1-1.2: new full-speed USB device number 4 using xhci-hcd
[    6.583521] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    6.584092] systemd[1]: Detected architecture arm64.
[    6.640386] systemd[1]: Set hostname to <odroid>.
[    6.745205] usb 1-1.2: New USB device found, idVendor=0c40, idProduct=7a1c
[    6.746604] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.754079] usb 1-1.2: Product: 2.4G Air Mouse
[    6.758658] usb 1-1.2: Manufacturer: Qualsense
[    6.763247] usb 1-1.2: SerialNumber: SmartMouse
[    6.842460] input: Qualsense 2.4G Air Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.2/0003:0C40:7A1C.0003/input/input4
[    6.907751] hid-generic 0003:0C40:7A1C.0003: input,hidraw2: USB HID v1.01 Keyboard [Qualsense 2.4G Air Mouse] on usb-xhci-hcd.0.auto-1.2/input2
[    6.917312] input: Qualsense 2.4G Air Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.3/0003:0C40:7A1C.0004/input/input5
[    6.929113] hid-generic 0003:0C40:7A1C.0004: input,hidraw3: USB HID v1.01 Mouse [Qualsense 2.4G Air Mouse] on usb-xhci-hcd.0.auto-1.2/input3
[    7.210178] systemd[1]: File /lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    7.221870] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    7.513065] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.535548] systemd[1]: Reached target Swap.
[    7.547533] systemd[1]: Reached target User and Group Name Lookups.
[    7.564116] systemd[1]: Created slice System Slice.
[    7.579850] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.854808] register clk_set_setting cpu[41]
[    7.858849] Registered firmware driver success.
[    7.859477] Try to load video/h264_multi.bin  ...
[    7.867545] firmware_codec firmware_vdec: Direct firmware load for video/h264_multi.bin failed with error -2
[    7.873144] Error : -2 can't load the video/h264_multi.bin.
[    7.878868] get data from fsys fail.
[    7.882574] invaild file type.
[    7.886103] Try to load video/h264.bin  ...
[    7.890187] firmware_codec firmware_vdec: Direct firmware load for video/h264.bin failed with error -2
[    7.899583] Error : -2 can't load the video/h264.bin.
[    7.904756] get data from fsys fail.
[    7.908483] invaild file type.
[    7.911975] Try to load video/h265.bin  ...
[    7.916058] firmware_codec firmware_vdec: Direct firmware load for video/h265.bin failed with error -2
[    7.925489] Error : -2 can't load the video/h265.bin.
[    7.930672] get data from fsys fail.
[    7.934401] invaild file type.
[    7.934644] Try to load video/h264_enc.bin  ...
[    7.939337] load firmware size : 76288, Name : video/h264_enc.bin.
[    7.939345] start to parse fw package.
[    7.939348] the package has 0 fws totally.
[    7.939350] the fw pack ver v0.0.0 is too lower.
[    7.939350] it may work abnormally so need to be update in time.
[    7.939737] Try to load video/video_ucode.bin  ...
[    7.988549] load firmware size : 768768, Name : video/video_ucode.bin.
[    7.989791] start to parse fw package.
[    7.993625] the package has 35 fws totally.
[    7.993813] the fw gxl_h264_multi.bin is not match.
[    7.994031] the fw gxl_vp9.bin is not match.
[    7.994158] the fw gxl_avs.bin is not match.
[    7.994409] the fw gxl_hevc.bin is not match.
[    7.994497] the fw gxl_vc1.bin is not match.
[    7.994635] the fw gxl_h264.bin is not match.
[    7.995488] the fw gxl_h264_mvc.bin is not match.
[    8.077128] Amlogic A/V streaming port init
[    8.081838] get gate demux control ok ffffffc0c9ca3600
[    8.084983] get gate parser_top control ok ffffffc0c9ca31c0
[    8.090610] get gate vdec control ok ffffffc0c9ca3180
[    8.095766] get gate clk_81 control failed           (null)
[    8.101586] get gate clk_vdec_mux control ok ffffffc0c85e8b00
[    8.107449] get gate clk_hcodec_mux control ok ffffffc0c9165780
[    8.113414] get gate clk_hevc_mux control ok ffffffc0c9165680
[    8.119310] get gate clk_hevcb_mux control ok ffffffc0c91655c0
[    8.125309] get gate ahbarb0 control ok ffffffc0c9165540
[    8.130725] get gate asyncfifo control failed           (null)
[    8.148810] amvdec_avs module init
[    8.165311] amvdec_h264 module init
[    8.189505] ammvdec_h264 module init
[    8.219494] amvdec_h265 module init
[    8.255762] amvdec_mmpeg4 module init
[    8.286213] amvdec_vc1 module init
[    8.315058] amvdec_vp9 module init
[    8.918059] EXT4-fs (mmcblk1p2): re-mounted. Opts: errors=remount-ro
[    9.010833] systemd-journald[2015]: Received request to flush runtime journal from PID 1
[    9.027391] systemd-journald[2015]: File /var/log/journal/e00bd6223a7245d0aa6e19e0ab12a024/system.journal corrupted or uncleanly shut down, renaming and replacing.
[   10.797634] Registered IR keymap rc-empty
[   10.797874] input: meson-ir as /devices/platform/ff808040.meson-ir/rc/rc0/input6
[   10.798078] rc rc0: meson-ir as /devices/platform/ff808040.meson-ir/rc/rc0
[   10.799552] meson-ir ff808040.meson-ir: AO_RTI_PIN_MUX : 0x100011
[   10.799563] meson-ir ff808040.meson-ir: receiver initialized
[   10.825698] lirc_dev: IR Remote Control driver registered, major 499
[   10.838634] ionvid: dbg: ionvideo open
[   10.838750] ionvid: dbg: vidioc_close!!!!
[   10.838755] ionvid: dbg: vidioc_close
[   10.839127] ionvid: dbg: ionvideo open
[   10.839224] ionvid: dbg: vidioc_close!!!!
[   10.839230] ionvid: dbg: vidioc_close
[   10.840752] ionvid: dbg: ionvideo open
[   10.840757] ionvid: dbg: ionvideo open
[   10.840859] ionvid: dbg: vidioc_close!!!!
[   10.840862] ionvid: dbg: vidioc_close!!!!
[   10.840864] ionvid: dbg: vidioc_close
[   10.840867] ionvid: dbg: vidioc_close
[   10.841116] rc rc0: lirc_dev: driver ir-lirc-codec (meson-ir) registered at minor = 0
[   10.841121] IR LIRC bridge handler initialized
[   10.842653] ionvid: dbg: ionvideo open
[   10.842761] ionvid: dbg: vidioc_close!!!!
[   10.842766] ionvid: dbg: vidioc_close
[   10.845586] ionvid: dbg: ionvideo open
[   10.845781] ionvid: dbg: vidioc_close!!!!
[   10.845792] ionvid: dbg: vidioc_close
[   10.847947] ionvid: dbg: ionvideo open
[   10.848136] ionvid: dbg: vidioc_close!!!!
[   10.848149] ionvid: dbg: vidioc_close
[   10.850650] ionvid: dbg: ionvideo open
[   10.850753] ionvid: dbg: vidioc_close!!!!
[   10.850757] ionvid: dbg: vidioc_close
[   10.850811] ionvid: dbg: ionvideo open
[   10.850979] ionvid: dbg: vidioc_close!!!!
[   10.850987] ionvid: dbg: vidioc_close
[   10.956997] rtc-pcf8563 3-0051: rtc core: registered rtc-pcf8563 as rtc0
[   11.435435] vout: aml_tvout_mode_work: monitor_timeout
[   11.938492] Fine tdm clk setting range (0~2000000), 11289593
[   11.939503] Fine spdif sysclk setting range(0~2000000), 5644797
[   11.945950] out of value, fixed it
[   11.948416] id=0 set inskew=0
[   11.948532] AED req_sel0 module:TDMOUT_B
[   11.948585] spk_mute_set: mute flag = 0
[   18.293323] Fine tdm clk setting range (0~2000000), 11289593
[   18.293567] Fine spdif sysclk setting range(0~2000000), 5644797
[   18.299750] out of value, fixed it
[   18.303162] id=0 set inskew=0
[   18.303227] AED req_sel0 module:TDMOUT_B
[   18.303265] spk_mute_set: mute flag = 0
[   21.411284] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   21.586885] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.674343] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[   21.674850] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   22.518086] fb: osd[0] enable: 0 (Xorg)
[   23.723690] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   23.723713] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   25.331923] fb: osd[0] enable: 1 (Xorg)
[   29.702446] meson_uart ff803000.serial: ttyS0 use xtal(24M) 24000000 change 115200 to 115200
[   37.316339] spdif_b keep clk continuous
[   37.316346] aml_spdif_open
[   37.316533] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   37.316723] set normal 512 fs /4 fs
[   37.316751] 	 set spdifout clk:5644800, mpll:22579200
[   37.316753] 	 get spdifout clk:5644797, mpll:22579186
[   37.316756] aml_dai_set_spdif_fmt , fmt 0x4010
[   37.316759] set normal 512 fs /4 fs
[   37.316767] 	 set spdifout clk:5644800, mpll:22579200
[   37.316769] 	 get spdifout clk:5644797, mpll:22579186
[   37.316829] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[   37.316836] hdmitx: hw: set audio
[   37.316838] hdmitx: hw: hdmitx tx_aud_src = 0
[   37.316850] hdmitx: fs = 2, cd = 8, tmds_clk = 148500
[   37.316852] hdmitx: hw: aud_n_para = 6272
[   37.316859] hdmitx: hw: set channel status
[   37.316887] hdmitx: audio: Audio Type: PCM
[   37.316889] hdmitx: audio: set audio param
[   37.316892] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[   37.356355] asoc-aml-card auge_sound: S/PDIF Playback enable
[   37.359320] audio_ddr_mngr: frddrs[1] registered by device ff642000.audiobus:tdmc
[   37.359485] set mclk:11289600, mpll:22579200, get mclk:11289593, mpll:22579186
[   37.359490] asoc aml_dai_set_tdm_fmt, 0x4011, ffffffc0ca377718, id(2), clksel(2)
[   37.359491] aml_dai_set_tdm_fmt(), fmt not change
[   37.359494] dump_pcm_setting(ffffffc0ca377718)
[   37.359495] 	pcm_mode(1)
[   37.359496] 	sysclk(11289600)
[   37.359497] 	sysclk_bclk_ratio(4)
[   37.359498] 	bclk(2822400)
[   37.359499] 	bclk_lrclk_ratio(64)
[   37.359499] 	lrclk(44100)
[   37.359500] 	tx_mask(0x3)
[   37.359501] 	rx_mask(0x3)
[   37.359504] 	slots(2)
[   37.359507] 	slot_width(32)
[   37.359510] 	lane_mask_in(0x2)
[   37.359514] 	lane_mask_out(0x1)
[   37.359517] 	lane_oe_mask_in(0x0)
[   37.359521] 	lane_oe_mask_out(0x0)
[   37.359524] 	lane_lb_mask_in(0x0)
[   37.359527] aml_dai_set_tdm_sysclk(), mpll no change, keep clk
[   37.359528] aml_dai_set_tdm_sysclk(), mclk no change, keep clk
[   37.359530] set mclk:11289600, mpll:22579200, get mclk:11289593, mpll:22579186
[   37.359531] aml_dai_set_clkdiv, div 4, clksel(2)
[   37.359537] aml_dai_set_bclk_ratio, select I2S mode
[   37.359540] mclk is not configured
[   37.359648] tdm playback mute: 0, lane_cnt = 4
[   37.366349] asoc-aml-card auge_sound: tdm playback enable
[   37.369356] spdif_a keep clk continuous
[   37.369361] aml_spdif_open
[   37.370725] audio_ddr_mngr: frddrs[2] registered by device ff642000.audiobus:spdif
[   37.370834] set normal 512 fs /4 fs
[   37.370855] 	 set spdifout clk:5644800, mpll:22579200
[   37.370856] 	 get spdifout clk:5644797, mpll:22579186
[   37.370858] aml_dai_set_spdif_fmt , fmt 0x4010
[   37.370860] set normal 512 fs /4 fs
[   37.370867] 	 set spdifout clk:5644800, mpll:22579200
[   37.370869] 	 get spdifout clk:5644797, mpll:22579186
[   37.370907] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[   37.370912] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[   37.379813] asoc-aml-card auge_sound: S/PDIF Playback enable
[   42.644722] asoc-aml-card auge_sound: S/PDIF Playback disable
[   42.644767] spdif_a keep clk continuous
[   42.644771] aml_spdif_close
[   42.644816] audio_ddr_mngr: frddrs[2] released by device ff642000.audiobus:spdif
[   42.645002] asoc-aml-card auge_sound: tdm playback stop
[   42.645062] tdm playback mute: 1, lane_cnt = 4
[   42.645100] audio_ddr_mngr: frddrs[1] released by device ff642000.audiobus:tdmc
[   42.645287] asoc-aml-card auge_sound: S/PDIF Playback disable
[   42.645332] spdif_b keep clk continuous
[   42.645336] aml_spdif_close
[   42.645376] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.657375] spdif_b keep clk continuous
[   42.657380] aml_spdif_open
[   42.657493] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.657647] spdif_b keep clk continuous
[   42.657651] aml_spdif_close
[   42.657692] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.657942] spdif_b keep clk continuous
[   42.657946] aml_spdif_open
[   42.658155] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.658296] spdif_b keep clk continuous
[   42.658300] aml_spdif_close
[   42.658329] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.658571] spdif_b keep clk continuous
[   42.658573] aml_spdif_open
[   42.658675] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.658872] spdif_b keep clk continuous
[   42.658876] aml_spdif_close
[   42.658907] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.659189] spdif_b keep clk continuous
[   42.659191] aml_spdif_open
[   42.659284] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.659593] spdif_b keep clk continuous
[   42.659597] aml_spdif_close
[   42.659629] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.660153] spdif_b keep clk continuous
[   42.660157] aml_spdif_open
[   42.660909] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.661057] set normal 512 fs /4 fs
[   42.661080] 	 set spdifout clk:5644800, mpll:22579200
[   42.661082] 	 get spdifout clk:5644797, mpll:22579186
[   42.661084] aml_dai_set_spdif_fmt , fmt 0x4010
[   42.661086] set normal 512 fs /4 fs
[   42.661093] 	 set spdifout clk:5644800, mpll:22579200
[   42.661094] 	 get spdifout clk:5644797, mpll:22579186
[   42.661122] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[   42.661129] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[   42.816209] spdif_b keep clk continuous
[   42.816214] aml_spdif_close
[   42.816281] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   42.823173] spdif_b keep clk continuous
[   42.823179] aml_spdif_open
[   42.823381] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[   42.823689] set normal 512 fs /4 fs
[   42.823722] 	 set spdifout clk:5644800, mpll:22579200
[   42.823725] 	 get spdifout clk:5644797, mpll:22579186
[   42.823729] aml_dai_set_spdif_fmt , fmt 0x4010
[   42.823732] set normal 512 fs /4 fs
[   42.823741] 	 set spdifout clk:5644800, mpll:22579200
[   42.823743] 	 get spdifout clk:5644797, mpll:22579186
[   42.823812] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[   42.823820] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[   42.844595] asoc-aml-card auge_sound: S/PDIF Playback enable
[   49.277256] asoc-aml-card auge_sound: S/PDIF Playback disable
[   49.277304] spdif_b keep clk continuous
[   49.277308] aml_spdif_close
[   49.277356] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[   52.663573] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   52.671372] EXT4-fs (mmcblk1p6): mounted filesystem with ordered data mode. Opts: (null)
[   52.765195] EXT4-fs (mmcblk1p3): mounted filesystem with writeback data mode. Opts: (null)
[   52.773523] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   53.205123] fuse init (API version 7.26)
[   64.523434] fb: mem_free_work, free memory: addr:800000
[  124.104948] spdif_b keep clk continuous
[  124.104952] aml_spdif_open
[  124.105038] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[  124.105171] set normal 512 fs /4 fs
[  124.105192] 	 set spdifout clk:5644800, mpll:22579200
[  124.105194] 	 get spdifout clk:5644797, mpll:22579186
[  124.105196] aml_dai_set_spdif_fmt , fmt 0x4010
[  124.105198] set normal 512 fs /4 fs
[  124.105205] 	 set spdifout clk:5644800, mpll:22579200
[  124.105206] 	 get spdifout clk:5644797, mpll:22579186
[  124.105247] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[  124.105253] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[  124.107422] asoc-aml-card auge_sound: S/PDIF Playback enable
[  152.945685] asoc-aml-card auge_sound: S/PDIF Playback disable
[  152.945748] spdif_b keep clk continuous
[  152.945753] aml_spdif_close
[  152.945801] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[  162.927580] spdif_b keep clk continuous
[  162.927585] aml_spdif_open
[  162.927711] audio_ddr_mngr: frddrs[0] registered by device ff642000.audiobus:spdif_b
[  162.927861] set normal 512 fs /4 fs
[  162.927887] 	 set spdifout clk:5644800, mpll:22579200
[  162.927888] 	 get spdifout clk:5644797, mpll:22579186
[  162.927891] aml_dai_set_spdif_fmt , fmt 0x4010
[  162.927893] set normal 512 fs /4 fs
[  162.927900] 	 set spdifout clk:5644800, mpll:22579200
[  162.927902] 	 get spdifout clk:5644797, mpll:22579186
[  162.927952] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[  162.927960] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[  162.928752] asoc-aml-card auge_sound: S/PDIF Playback enable
root@odroid:/home/odroid# 

If this log comes from Ubuntu Mate, I think booting Ubuntu by Petitboot is fine. Is the problem that Ubuntu is not stable after Petitboot?

I have no problems with petitboot.

Previously I created 1 extended partitions and 5 logical partitions on the same card. Ubuntu -mate stutter again.
I thought that the logical partition I created in the extended partition makes ubuntu mate stuttering, but it's not.

Can you share the kernel log when Ubuntu Mate is starting?

I did the triple OS installation, ubuntu mate stuttering. I thought the new sd card I bought was not compatible with the N2.
You asked me for Ubuntu mate kernel log.
Thanks again for your help and answer,

[STARSK]

@ tobetter : thank you for helping me!

it's exactly the same behaviour without AVR using Way 2

Test 1:

1- I plug the power cable
2 - Petitboot starts (version 201907-RC1)
3 - boot from coreelec installed on EMMC =>Ok
4 - coreelec is started and works fine
5 - I power off corelec using remote =>Ok
6 - I try to power on coreelec with remote =>Ko nothing happens

Test 2 :

1- I plug the power cable
2 - Petitboot starts (version 201907-RC1)
3 - boot from Android Pie installed on µsd =>Ok
4 - Android pie is started and works fine
5 - I power off Android pie using remote =>Ok
6 - I power on Android pie with remote =>Ok

Thank you for sharing the test. For the test case 1, the reason why the system does not wake up when it's been suspended by remote on CoreELEC is that CoreELEC has its own U-boot change for IR and CEC suspend/resume feature which is not compatible with HK's implementation. I've aware of it for sometime but not applied it to HK U-boot yet and will see a chance to merge into Petitboot.

Thank you for the explanation, do you think it would be possible to implement it on the next release of petitboot ?

[xabolcs]

FYI, for mainline kernel, you can run my Debian Installer or Ubuntu image.

I copied contents of BOOT and rootfs to extended partitions of eMMC, and noticed that the BOOT is ext2 so I reformatted the new partition from FAT16 to ext2.
I fixed the UUIDs in boot.scr(!) and /etc/fstab after the copy.

Rebooting to Petitboot, it doesn't recognized your image.

Does it support ext2 and also boot.scr?

[brad]

If you need to convert a uImage to an Image (stripe the header)

Code: Select all

tail -c+65 < uImage > Image

[tobetter]

FYI, for mainline kernel, you can run my Debian Installer or Ubuntu image.

I copied contents of BOOT and rootfs to extended partitions of eMMC, and noticed that the BOOT is ext2 so I reformatted the new partition from FAT16 to ext2.
I fixed the UUIDs in boot.scr(!) and /etc/fstab after the copy.

Rebooting to Petitboot, it doesn't recognized your image.

Does it support ext2 and also boot.scr?

Yes, it does recognize ext2 and boot.scr. boot.scr and boot.init are being supported by OS images from me.
Do you have boot.ini with boot.scr in the same directory?
Does the extended partition is mounted under /usr/var/petitboot/mnt/dev/mmcblk0p*? If so, can you share the output with this command?
uboot-parser /usr/var/petitboot/mnt/dev/mmcblk0p<?> where mmcblk0p<?> is the extend partition.

[xabolcs]

If you need to convert a uImage to an Image (stripe the header)

Code: Select all

tail -c+65 < uImage > Image

Thank You! It works flawlessly!

Yes, it does recognize ext2 and boot.scr. boot.scr and boot.init are being supported by OS images from me.
Do you have boot.ini with boot.scr in the same directory?
Does the extended partition is mounted under /usr/var/petitboot/mnt/dev/mmcblk0p*? If so, can you share the output with this command?
uboot-parser /usr/var/petitboot/mnt/dev/mmcblk0p<?> where mmcblk0p<?> is the extend partition.

Your image is at sdb6:

Code: Select all

NAME    FSTYPE LABEL    UUID                                 MOUNTPOINT
sdb                                                          
├─sdb1  vfat   VFAT     5DAF-525D                            /media/VFAT
├─sdb2  ext4            dc827d6a-4b6a-47f2-a442-d3154f21778e /media/dc827d6a-4b6a-47f2-a442-d3154f21778e
├─sdb3                                                       
├─sdb5  vfat   BOOTDEB  BA12-21EE                            /media/BOOTDEB
├─sdb6  ext2   BOOTUBNT 108b71df-b312-451f-a735-96e5c420f122 /media/BOOTUBNT
├─sdb7  vfat   BOOTMNLN 2FF2-FBAD                            /media/BOOTMNLN
├─sdb8  vfat   BOOTOTHR 328A-1FDD                            /media/BOOTOTHR
├─sdb9  ext4   ROOTDEB  3c5ccbb1-faad-4f0c-bfeb-aa0e625b3bb6 /media/ROOTDEB
└─sdb10 ext4   ROOTUBNT bc903692-5bee-41c5-9240-bb94234dbc32 /media/ROOTUBNT

So I tried mmcblk0p6:

Code: Select all

/ # ls -l /usr/var/petitboot/mnt/dev/mmcblk0p6                                                                          
total 37198                                                                                                             
-rw-r--r--    1 0        0          4856497 Sep 10 14:54 System.map-4.9.190-odroidn2-arm64                              
-rw-rw-r--    1 1000     1000         41831 Sep  7 16:23 boot-logo.bmp.gz                                               
-rw-r--r--    1 0        0             6035 Nov 15 17:51 boot.scr                                                       
-rw-r--r--    1 0        0           153514 Sep 10 14:54 config-4.9.190-odroidn2-arm64                                  
lrwxrwxrwx    1 0        0               56 Nov 15 16:39 dtb -> dtbs/4.9.190-odroidn2-arm64/amlogic/meson64_odroidn2.dtb
lrwxrwxrwx    1 0        0               56 Nov 15 16:39 dtb-4.9.190-odroidn2-arm64 -> dtbs/4.9.190-odroidn2-arm64/amlog
ic/meson64_odroidn2.dtb                                                                                                 
drwxr-xr-x    3 0        0             1024 Sep 10 17:56 dtbs                                                           
-rw-r--r--    1 0        0          8630104 Sep 10 17:55 initrd.img-4.9.190-odroidn2-arm64                              
drwx------    2 0        0            12288 Nov 15 16:38 lost+found                                                     
-rw-r--r--    1 0        0         24234496 Sep 10 14:54 vmlinuz-4.9.190-odroidn2-arm64                                 
/ # 

And the parser says:

Code: Select all

/ # uboot-parser /usr/var/petitboot/mnt/dev/mmcblk0p6/boot.scr                                                          
*** Warning - bad CRC, using default environment                                                                        
                                                                                                                        
## Executing script at 7f7add7010                                                                                       
Bad data crc                                                                                                            
                                                                                                                        
/ # 

[xabolcs]

And the parser says:

Code: Select all

/ # uboot-parser /usr/var/petitboot/mnt/dev/mmcblk0p6/boot.scr                                                          
*** Warning - bad CRC, using default environment                                                                        
                                                                                                                        
## Executing script at 7f7add7010                                                                                       
Bad data crc                                                                                                            
                                                                                                                        
/ # 

Looks like it's really a CRC error, as there are interesting characters on the top of boot.scr:

Code: Select all

/ # head /usr/var/petitboot/mnt/dev/mmcblk0p6/boot.scr                                                                  
'V㳋�p�]w��Ss��boot scriptK                                                                                        
#                                                                                                                       
# flash-kernel: bootscr.odroid-n2                                                                                       
#                                                                                                                       
                                                                                                                        
# Bootscript using the new unified bootcmd handling                                                                     
#                                                                                                                       
# Expects to be called with the following environment variables set:                                                    
#                                                                                                                       
#  devtype              e.g. mmc/scsi etc                                                                               
/ # Minicom2.7.1Minicom2.7.1

Yes, I'm on UART with Minicom ... it writes out if I cat or head the boot.scr.


Deleting the first row passes the Bad data crc error:

Code: Select all

/ # uboot-parser  /usr/var/petitboot/mnt/dev/mmcblk0p6/boot.scr                                                         
*** Warning - bad CRC, using default environment                                                                        
                                                                                                                        
## Executing script at 7f8a658010                                                                                       
Wrong image format for "source" command                                                                                 
                                                                                                                        
/ # 

[mad_ady]

boot.scr is supposed to be a binary file, so having those characters looks normal.

[xabolcs]

boot.scr is supposed to be a binary file, so having those characters looks normal.

Ouch!

I edited manually the UUIDs part of it ... that's why it had crc error.

I need to migrate it to boot.ini.

[istanbulls]

Hi,
I bought a new uSD for 3-OS. Samsung EVO Plus 64GB U3 https://www.amazon.com/Samsung-MicroSDX ... B06XFWPXYD
It doesn't work with Petitboot.
I made video on Youtube. English is not my mother tongue, I can not express myself well. I thought it would be more understandable.
This uSD works very well with Ubuntu-Mate, Armbian and coreelec and doesn't stutter. I am very pleased but I do not understand why petitboot is causing problems. It doesn't make sense.
https://www.youtube.com/watch?v=cHTQ8CVQd00

Another problem,
Again I bought a Lexar 64 GB 1000x 4K Micro SD for the triple OS. https://www.lexar.com/portfolio_page/pr ... -ii-cards/
No Petitboot problem.
But he doesn't work with Ubuntu-Mate, stuttering, hanging out, not fluent.
Expensive and fast uSD but problematic with Ubuntu-Mate.
https://www.youtube.com/watch?v=CGQ8ooTZ9hI

Thank you in advance for your information and help

[ajcard]

had a problem with petitboot 2019-11-rc2
(see viewtopic.php?f=176&t=33993&start=450#p273454)

petitboot fails to start and exits to shell if I hit any key.
thought i go to /usr/var...mmcblk0p1 (media/boot on emmc) in the shell.
there I have the last working kernel/boot.ini in media/boot/oldkernel saved.
wanted to copy these files to /media/boot folder, but its mounted ro.
ok, unmount. mount again, now its rw. but copying does not work/has no effect.

Is this the expected behaviour? so in this case my emmc is inaccessable,
because pluged in, n2 doesnt boot. Dont know if its possible, but
I hoped the "emergency shell" in petitboot could help me.

[tobetter]

had a problem with petitboot 2019-11-rc2
(see viewtopic.php?f=176&t=33993&start=450#p273454)

petitboot fails to start and exits to shell if I hit any key.
thought i go to /usr/var...mmcblk0p1 (media/boot on emmc) in the shell.
there I have the last working kernel/boot.ini in media/boot/oldkernel saved.
wanted to copy these files to /media/boot folder, but its mounted ro.
ok, unmount. mount again, now its rw. but copying does not work/has no effect.

Is this the expected behaviour? so in this case my emmc is inaccessable,
because pluged in, n2 doesnt boot. Dont know if its possible, but
I hoped the "emergency shell" in petitboot could help me.

I am preparing another version to enhance the features of Petitboot and a couple of them could help you, I think.
For your working kernel, please make sure that if your boot.ini is pointing the one properly. You can run the command uboot-parser /usr/var/.../mmcblk0p1/boot.ini and check its output.

[tobetter]

Hi,
I bought a new uSD for 3-OS. Samsung EVO Plus 64GB U3 https://www.amazon.com/Samsung-MicroSDX ... B06XFWPXYD
It doesn't work with Petitboot.
I made video on Youtube. English is not my mother tongue, I can not express myself well. I thought it would be more understandable.
This uSD works very well with Ubuntu-Mate, Armbian and coreelec and doesn't stutter. I am very pleased but I do not understand why petitboot is causing problems. It doesn't make sense.
https://www.youtube.com/watch?v=cHTQ8CVQd00

It's a bit confusing, so the Ubuntu Mate can boot when it's on 3rd entry of Boot menu but not boot when in the 2nd entry with the same memory card?

Another problem,
Again I bought a Lexar 64 GB 1000x 4K Micro SD for the triple OS. https://www.lexar.com/portfolio_page/pr ... -ii-cards/
No Petitboot problem.
But he doesn't work with Ubuntu-Mate, stuttering, hanging out, not fluent.
Expensive and fast uSD but problematic with Ubuntu-Mate.
https://www.youtube.com/watch?v=CGQ8ooTZ9hI

Thank you in advance for your information and help

Is the board with another OS without shuttering?

[ajcard]

I am preparing another version to enhance the features of Petitboot and a couple of them could help you, I think.
For your working kernel, please make sure that if your boot.ini is pointing the one properly. You can run the command uboot-parser /usr/var/.../mmcblk0p1/boot.ini and check its output.

hi @tobetter,
thought I give the Petitboot (dev.20190705) from n2 wiki a try.
(see to viewtopic.php?f=176&t=33993&p=273521#p273502 )

So I downgraded petitboot.
booted, up/downgrade process started, says 100%, at least it verified
the flashing and rebooted the n2.

red led and blue led goes on - nothing more happens.

spi swtich to emmc, hk 4.9 linux boots, power off, switch to spi,
red led and blue led goes on - nothing more happens.

Any chance to rescue the spi?

[tobetter]

@ajcard, so your Petitboot does not boot and it looks like corrupted somehow? If so, download the "Recovery image" from the link and flashing it to extra SD card to boot with it, boot select switch must be "MMC" and eMMC would be removed for sure.
https://wiki.odroid.com/odroid-n2/os_im ... ev20190417

Once SPI flash memory is updated with the version, ensure you N2 can boot with SPI flash memory. Then do copy the recent version of Petitboot image to the same SD card, and reboot to update. If everything goes well, you will have recent version of Petitboot.

[istanbulls]

Hi,
I bought a new uSD for 3-OS. Samsung EVO Plus 64GB U3 https://www.amazon.com/Samsung-MicroSDX ... B06XFWPXYD
It doesn't work with Petitboot.
I made video on Youtube. English is not my mother tongue, I can not express myself well. I thought it would be more understandable.
This uSD works very well with Ubuntu-Mate, Armbian and coreelec and doesn't stutter. I am very pleased but I do not understand why petitboot is causing problems. It doesn't make sense.
https://www.youtube.com/watch?v=cHTQ8CVQd00

It's a bit confusing, so the Ubuntu Mate can boot when it's on 3rd entry of Boot menu but not boot when in the 2nd entry with the same memory card?

Lexar 64Gb and Sandisk 32 gb uSD have triple OS and work with petitboot. I just have trouble with the Samsung 64gb uSD.

Coreelec, Armbian and Ubuntu-Mate on the Samsung EVO Plus 64GB No one is powered by a petitboot. First I need to do "exit to shell" and then Ctrl + Alt + Del, restart and petitboot works. Whichever OS I choose opens.

Another problem,
Again I bought a Lexar 64 GB 1000x 4K Micro SD for the triple OS. https://www.lexar.com/portfolio_page/pr ... -ii-cards/
No Petitboot problem.
But he doesn't work with Ubuntu-Mate, stuttering, hanging out, not fluent.
Expensive and fast uSD but problematic with Ubuntu-Mate.
https://www.youtube.com/watch?v=CGQ8ooTZ9hI

Thank you in advance for your information and help

Is the board with another OS without shuttering?

just having trouble with Ubuntu-Mate. Single or triple Armbian, Coreelec is very fast and smooth.

Thanks again for your answer and help. Sometimes I think I'm a very problematic user and I'm sorry. I am so sorry

[ajcard]

@ajcard, so your Petitboot does not boot and it looks like corrupted somehow? If so, download the "Recovery image" from the link and flashing it to extra SD card to boot with it, boot select switch must be "MMC" and eMMC would be removed for sure.
https://wiki.odroid.com/odroid-n2/os_im ... ev20190417

Once SPI flash memory is updated with the version, ensure you N2 can boot with SPI flash memory. Then do copy the recent version of Petitboot image to the same SD card, and reboot to update. If everything goes well, you will have recent version of Petitboot.

Thanks, worked!

Is downgrading a general prob in petitboot? if so, a note in the wiki or a version check would be an option, maybe

[tobetter]

@ajcard, so your Petitboot does not boot and it looks like corrupted somehow? If so, download the "Recovery image" from the link and flashing it to extra SD card to boot with it, boot select switch must be "MMC" and eMMC would be removed for sure.
https://wiki.odroid.com/odroid-n2/os_im ... ev20190417

Once SPI flash memory is updated with the version, ensure you N2 can boot with SPI flash memory. Then do copy the recent version of Petitboot image to the same SD card, and reboot to update. If everything goes well, you will have recent version of Petitboot.

Thanks, worked!

Is downgrading a general prob in petitboot? if so, a note in the wiki or a version check would be an option, maybe

Downgrading itself is not a problem but since Petitboot is a baby project, you will miss features. Due to the limited space and features to be supported, as of now, I am not thinking of checking a version which is good to have.

[tobetter]

Coreelec, Armbian and Ubuntu-Mate on the Samsung EVO Plus 64GB No one is powered by a petitboot. First I need to do "exit to shell" and then Ctrl + Alt + Del, restart and petitboot works. Whichever OS I choose opens.

That's interesting...I've updated the kernel for Petitboot and preparing the new version. Would you be mind to test it later once I share the new version?

just having trouble with Ubuntu-Mate. Single or triple Armbian, Coreelec is very fast and smooth.

I guess this is a similar problem above, maybe kernel driver must be updated and test with the card. I've checked if I have the same Lexar one, but unfortunately, have another version a bit different with yours which works on ODROID-N2.

Thanks again for your answer and help. Sometimes I think I'm a very problematic user and I'm sorry. I am so sorry

Sounds interesting, too. At least you are far from there yet, just happy to see someone is trying triple OS.

[ajcard]

..For your working kernel, please make sure that if your boot.ini is pointing the one properly. You can run the command uboot-parser /usr/var/.../mmcblk0p1/boot.ini and check its output.

tried to analyze the kernel 5.4 boot problem (installed on usb stick sdb1)

* updated petitboot to spiboot-201911-rc2.img
* rebooted
* petitboot starts and stays at: "sdb1 processing new usb device"
* hit any key -> error: "failed to launch petitboot, dropping to shell"
* in shell: $uboot-parser /usr/var.....sdb1/boot.ini
Warning - bad CRC, using default environment
DTB=....n2.dtb found
boot opts found
IMAGE= is missing, not found or ...?

boot.ini
-------------
# Set load addresses
setenv dtb_loadaddr "0x1000000"

fatload usb ${devno}:1 ${dtb_loadaddr} n2.dtb
fatload usb ${devno}:1 0x01080000 uImage
bootm 0x1080000 - ${dtb_loadaddr}
-------------

Any idea whats going wrong?

[ajcard]

posted twice - deleted

[tobetter]

..For your working kernel, please make sure that if your boot.ini is pointing the one properly. You can run the command uboot-parser /usr/var/.../mmcblk0p1/boot.ini and check its output.

tried to analyze the kernel 5.4 boot problem (installed on usb stick sdb1)

* updated petitboot to spiboot-201911-rc2.img
* rebooted
* petitboot starts and stays at: "sdb1 processing new usb device"
* hit any key -> error: "failed to launch petitboot, dropping to shell"
* in shell: $uboot-parser /usr/var.....sdb1/boot.ini
Warning - bad CRC, using default environment
DTB=....n2.dtb found
boot opts found
IMAGE= is missing, not found or ...?

boot.ini
-------------
# Set load addresses
setenv dtb_loadaddr "0x1000000"

fatload usb ${devno}:1 ${dtb_loadaddr} n2.dtb
fatload usb ${devno}:1 0x01080000 uImage
bootm 0x1080000 - ${dtb_loadaddr}
-------------

Any idea whats going wrong?

It's a known issue, please refer to the link.
posting.php?mode=quote&f=182&p=273537#pr272843

You should change 0x1080000 to 0x01080000 and strip the U-boot header from uImage such that only to have Image or Image.gz. Actually, I made another Petitboot version that resolved both problems and having adding and testing a couple features more in order to publish this week, tomorrow or day after tomorrow.

[ajcard]

thanks, I found the uimage prob a few seconds ago
ok, lets wait for the new version.

[odroidn2user]

So, finally installed the spiboot-201911-rc2.img to SPI.
It works. Except, it doesn't, really.

Both my Manjaro ARM 19.08 image on a USB stick isn't identified: NOLABEL, or something thereabouts. It also just doesn't boot. The blue led keeps blinking and nothing. Used etcher to 'burn' the normal Manjaro ARM 19.08 image to a USB stick.

And my keyboard doesn't work. It's a fairly basic Microsoft Natural Ergonomic Keyboard 4000 v1.0. Keypresses, any keypress, isn't registered. Nothing moves, basically.

So, once it loads, it identifies the USB stick as something bootable, it tries to boot it, just nothing happens. And I can't actually do anything to change anything about it.

Any chance on adding support for both?

--
Ok, booted the Manjaro ARM on SD with the SPI/MMC-switch set to MMC, works fine. Just not on USB, it seems.

sudo blkid reports:
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="FBC7-FECF" TYPE="vfat" PARTUUID="6a6ec900-01"
/dev/mmcblk1p2: LABEL="ROOT" UUID="28bd7a92-0522-468c-9589-404551be0325" TYPE="ext4" PARTUUID="6a6ec900-02"
/dev/sda1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="FBC7-FECF" TYPE="vfat" PARTUUID="6a6ec900-01"
/dev/sda2: LABEL="ROOT" UUID="28bd7a92-0522-468c-9589-404551be0325" TYPE="ext4" PARTUUID="6a6ec900-02"

lsusb says:
Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0

[tobetter]

So, finally installed the spiboot-201911-rc2.img to SPI.
It works. Except, it doesn't, really.

Both my Manjaro ARM 19.08 image on a USB stick isn't identified: NOLABEL, or something thereabouts. It also just doesn't boot. The blue led keeps blinking and nothing.

And my keyboard doesn't work. It's a fairly basic Microsoft Natural Ergonomic Keyboard 4000 v1.0. Keypresses, any keypress, isn't registered. Nothing moves, basically.

So, once it loads, it identifies the USB stick as something bootable, it tries to boot it, just nothing happens. And I can't actually do anything to change anything about it.

Any chance on adding support for both?

--
Ok, booted the Manjaro ARM on SD, works fine. Just not on USB, it seems.

sudo blkid reports:
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="FBC7-FECF" TYPE="vfat" PARTUUID="6a6ec900-01"
/dev/mmcblk1p2: LABEL="ROOT" UUID="28bd7a92-0522-468c-9589-404551be0325" TYPE="ext4" PARTUUID="6a6ec900-02"
/dev/sda1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="FBC7-FECF" TYPE="vfat" PARTUUID="6a6ec900-01"
/dev/sda2: LABEL="ROOT" UUID="28bd7a92-0522-468c-9589-404551be0325" TYPE="ext4" PARTUUID="6a6ec900-02"

Can you specify the exact image file name of Manjaro Image?
You are saying your MS keyboard does not move in Petitboot, right?
After Manjaro has started, do you see the blue LED is blinking and do you recognize that the HDMI signal is out although your display is just black?

[tobetter]

I just realize that the view count of this thread hits more than 41k...is it real? I am wondering how many bots made this...

Screenshot from 2019-11-26 02-12-57.png (18.24 KiB) Viewed 1529 times

[odroidn2user]

Not quite understand the question about the image file name.

The manjaro arm image i'm trying to USB-boot with petitboot is from:
https://forum.manjaro.org/t/manjaro-arm ... ased/99031

The original image file "Manjaro-ARM-kde-on2-19.08.img.xz", though I've etchered that to a USB stick. So that file name is probably gone.

After it trying to boot the Manjaro ARM image:
The screen stays black, but it doesn't seem to go to sleep.
The blue led is blinking, stays blinking.

The keyboard arrows and keys don't move the selection in the Petitboot. The letters don't activate the options.

[tobetter]

Not quite understand the question about the image file name.

The manjaro arm image i'm trying to USB-boot with petitboot is from:
https://forum.manjaro.org/t/manjaro-arm ... ased/99031

The original image file "Manjaro-ARM-kde-on2-19.08.img.xz", though I've etchered that to a USB stick. So that file name is probably gone.

After it trying to boot the Manjaro ARM image:
The screen stays black, but it doesn't seem to go to sleep.
The blue led is blinking, stays blinking.

The keyboard arrows and keys don't move the selection in the Petitboot. The letters don't activate the options.

For the black screen issue, can you try to change the value of display_autodetect from true to false and set the decent resolve of your display with hdmimode in the boot.ini where Manjaro is installed?

[odroidn2user]

I've set the boot.ini on the usb stick to
setenv display_autodetect "false"

I couldn't find a resolve or a decent resolve, i take it you mean the setenv hdmimode.
This was set to:
setenv hdmimode "1080p60hz"
which seems about right to me.

Doesn't seem to make a difference with booting though. Blue light blinks, monitor stays on, but stays black.

I've tried to petitboot the uSD card with Manjaro ARM KDE 19.08 on it, isn't even found as a bootable device.
Only works if I switch the switch to MMC.

---

Update: Hmm, I'm detecting a pattern...
I've tried flashing the Hardkernel Ubuntu Mate N2 image from the wiki on the USB stick.
Shows as 'NOLABEL' as well. Same thing, seems to boot, blue links blinks (fast), but nothing on the screen.
Tried another USB stick. Also the Ubuntu Mate N2 image, also 'NOLABEL', also nothing on the screen.
Also tried a USB2 port instead of the USB3 port, same behavior.

Booted the device without any bootable sticks, Petitboot doesn't find anything, then added the uSD with Manjaro later.
It immediately found a bootable 'NOLABEL', selects and tries to boot it, then doesn't do anything. Black screen.

I've set the Manjaro image on the uSD to stop the blue light from blinking somewhere during the bootup procedure. (it's a little annoying)
And that doesn't happen when I try to boot it via Petitboot.
So I guess it really isn't booting this thing. Otherwise the blue light would stop blinking.

So, either way, Petitboot "dev 20191111" isn't booting or identifying anything.
I'm thinking perhaps this would be a time to consider downgrading the Petitboot?

The problem is I *really* like the concept of petitboot, and the hardkernel logo at boot time is kinda cool (could do without the letters beneath it though).
So, the concept and execution is wonderful, except that I don't seem to get it working just yet.

Oh yeah, I found another keyboard, Logitech k400r and that one works for the petitboot menu. (No booting yet though)

--

Downgraded petitboot to the 201910-rc1 version.
By the way, I'm using the "Petitboot (dev.20190417)" recovery image downloaded from:
https://wiki.odroid.com/odroid-n2/os_images/petitboot
Etched it using etcher, then manually update the spiboot image to flash the petitboot image as posted on the forum in this thread.
Seems to work, the automated check after flashing says successful.

The 201910-rc1 image: No change.
Microsoft keyboard also not enabled and it isn't booting the images from USB (HK's Ubuntu Mate) or uSD (Manjaro ARM KDE).
When switched to MMC the uSD Manjaro image boots up smoothly.
Tried a Samsung 32GB uSD, a Samsung 128GB USB3 stick and an Integral 16GB USB3 stick. All three a no go via Petitboot.
So yeah...

[ajcard]

You should change 0x1080000 to 0x01080000 and strip the U-boot header from uImage such that only to have Image or Image.gz. Actually, I made another Petitboot version that resolved both problems and having adding and testing a couple features more in order to publish this week, tomorrow or day after tomorrow.

just for information: I stripped the the header and added rootdelay and bootdelay, voila, 5.4 starts from the usb-stick

[istanbulls]

I just realize that the view count of this thread hits more than 41k...is it real? I am wondering how many bots made this...
Screenshot from 2019-11-26 02-12-57.png

Yesterday I noticed that you can be proud of yourself congratulations.

I've had the same problems with Manjaro and I've worked hard, but I haven't been successful, and I don't work with petitboot. I gave up

[istanbulls]

I've set the boot.ini on the usb stick to
setenv display_autodetect "false"

I couldn't find a resolve or a decent resolve, i take it you mean the setenv hdmimode.
This was set to:
setenv hdmimode "1080p60hz"
which seems about right to me.

Doesn't seem to make a difference with booting though. Blue light blinks, monitor stays on, but stays black.

I've tried to petitboot the uSD card with Manjaro ARM KDE 19.08 on it, isn't even found as a bootable device.
Only works if I switch the switch to MMC.

---

Update: Hmm, I'm detecting a pattern...
I've tried flashing the Hardkernel Ubuntu Mate N2 image from the wiki on the USB stick.
Shows as 'NOLABEL' as well. Same thing, seems to boot, blue links blinks (fast), but nothing on the screen.
Tried another USB stick. Also the Ubuntu Mate N2 image, also 'NOLABEL', also nothing on the screen.
Also tried a USB2 port instead of the USB3 port, same behavior.

Booted the device without any bootable sticks, Petitboot doesn't find anything, then added the uSD with Manjaro later.
It immediately found a bootable 'NOLABEL', selects and tries to boot it, then doesn't do anything. Black screen.

I've set the Manjaro image on the uSD to stop the blue light from blinking somewhere during the bootup procedure. (it's a little annoying)
And that doesn't happen when I try to boot it via Petitboot.
So I guess it really isn't booting this thing. Otherwise the blue light would stop blinking.

So, either way, Petitboot "dev 20191111" isn't booting or identifying anything.
I'm thinking perhaps this would be a time to consider downgrading the Petitboot?

The problem is I *really* like the concept of petitboot, and the hardkernel logo at boot time is kinda cool (could do without the letters beneath it though).
So, the concept and execution is wonderful, except that I don't seem to get it working just yet.

Oh yeah, I found another keyboard, Logitech k400r and that one works for the petitboot menu. (No booting yet though)

--

Downgraded petitboot to the 201910-rc1 version.
By the way, I'm using the "Petitboot (dev.20190417)" recovery image downloaded from:
https://wiki.odroid.com/odroid-n2/os_images/petitboot
Etched it using etcher, then manually update the spiboot image to flash the petitboot image as posted on the forum in this thread.
Seems to work, the automated check after flashing says successful.

The 201910-rc1 image: No change.
Microsoft keyboard also not enabled and it isn't booting the images from USB (HK's Ubuntu Mate) or uSD (Manjaro ARM KDE).
When switched to MMC the uSD Manjaro image boots up smoothly.
Tried a Samsung 32GB uSD, a Samsung 128GB USB3 stick and an Integral 16GB USB3 stick. All three a no go via Petitboot.
So yeah...

Red LED is on, blue LED is slow flash.
The blue led should be like a faster heartbeat. The ethernet lamp should light.
The ethernet lamp does not light.
So the screen is dark because Manjaro does not work. (In my opinion)

[tobetter]

@odroidn2user and @istanbulls, I've looked into Manajro image KDE and XFCE, I realize that they provide two initramfs - initramfs-linux.uimg and initramfs-linux.img and the default boot.ini points initramfs-linux.uimg which is not the format supported by the current Petitboot. The workaround for this is to replace it with initramfs-linux.imb. load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg -> load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux, at least this will bring Manjaro to Petitboot menu. I already fixed this in the next release which will come in this week.

Also if you encounter the black screen issue after a target OS is started, please do set display_autodetect as false. This works for me.

Please try it out and let me know, it would be nice if you can share the model of your display device.

[istanbulls]

thanks, i'll try it as soon as possible.

[odroidn2user]

Well, it's probably close... but nope. Doesn't seem to make much of a difference. (tested with the 201910-rc1 petitboot)

Perhaps it's just the screen staying black?
I've set the auto_detect to false and the monitor is indeed a 1080p monitor...

[tobetter]

Well, it's probably close... but nope. Doesn't seem to make much of a difference. (tested with the 201910-rc1 petitboot)

Perhaps it's just the screen staying black?
I've set the auto_detect to false and the monitor is indeed a 1080p monitor...

So you had fixed the boot.ini in order to boot Manjaro but not able to see the screen...right? What if display_autodetect is set to true?

[odroidn2user]

it would be nice if you can share the model of your display device.

The monitor is a cheap LG M2352, a 23 inch FullHD TV.
I've been using that (and it works surprisingly well) given that my main monitor is a(n old) Samsung SyncMaster 203B with the Odroid N2 unsupported resolution of 1400x1050. That resolution doesn't go well with the Odroid, it almost works, but it is garbled. So have been using a 23 inch TV as monitor. Is 1080p with HDMI, and it's all been good up until perhaps the petitboot now. Besides the viewing angles not being great, using a small TV as a monitor actually works surprisingly well. No problem with audio support in any which way!

I'll give the detect true option a go probably in a few hours.

(It seems that, given my LG TV, Samsung monitor, Samsung USB stick, Samsung uSD card (2x) and Hardkernel Odroid all here on my desk, I've been buying into South Korean equipment at an amazing rate!)

[tobetter]

it would be nice if you can share the model of your display device.

The monitor is a cheap LG M2352, a 23 inch FullHD TV.
I've been using that (and it works surprisingly well) given that my main monitor is a(n old) Samsung SyncMaster 203B with the Odroid N2 unsupported resolution of 1400x1050. That resolution doesn't go well with the Odroid, it almost works, but it is garbled. So have been using a 23 inch TV as monitor. Is 1080p with HDMI, and it's all been good up until perhaps the petitboot now. Besides the viewing angles not being great, using a small TV as a monitor actually works surprisingly well. No problem with audio support in any which way!

I'll give the detect true option a go probably in a few hours.

Please do try to set dvi as well for another env variable voutmode.

[istanbulls]

Hi @tobetter

Code: Select all

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux
fdt addr ${dtb_loadaddr}

I changed the code in this way, petitboot restarted, I did a few attempts was the same.

Code: Select all

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.img
fdt addr ${dtb_loadaddr}

Code: Select all

load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux

I added .img

petitboot ok. does not restart. But the screen is still black, Ethernet LED does not light, Blue LED heartbeat is slow.


I tried "display_autodetect" "false" and "true". screen black.

[tobetter]

Hi @tobetter

Code: Select all

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux
fdt addr ${dtb_loadaddr}

I changed the code in this way, petitboot restarted, I did a few attempts was the same.

Code: Select all

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.img
fdt addr ${dtb_loadaddr}

Code: Select all

load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux

I added .img

petitboot ok. does not restart. But the screen is still black, Ethernet LED does not light, Blue LED heartbeat is slow.


I tried "display_autodetect" "false" and "true". screen black.

Hi, is the Manjaro OS...right? I've tested Manjaro OS today with two different Samsung display, one is monitor and another one is TV. Interesting thing is it show its screen to TV regardless of the value of "display_autodetect". But monitor works always. Probably something wrong in kernel but not found the clue yet.

Any other OS you are trying to are fine, but Manjaro is not?

"Tapatalk wishes you to have fun with ODROID"

[istanbulls]

I don't have a monitor, I have an LCD TV.
Yeah, just Manjaro.
As I wrote in the previous message, I tried

Code: Select all

load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.img

[istanbulls]

I gave up on Manjaro long ago. I tried a lot but it didn't work with petitboot.
When Manjaro was on the agenda again, I wanted to share my experience. I used to live without manjaros ))

[tobetter]

I gave up on Manjaro long ago. I tried a lot but it didn't work with petitboot.
When Manjaro was on the agenda again, I wanted to share my experience. I used to live without manjaros ))

Thanks...good to know.
I am holding the another new version with a couple of new features, expected to release it with fixing the display issue. But as of now, a workaround - not a solution - I have is to change the value of display_autodetect...maybe I would release a new one and see how it works for others.

[odroidn2user]

OK, here is the deal:
I have hooked it up to the big screen tv. (A Sony 40inch 1080p thing, not recent) And it works there.
With it works, I mean petitboot boots a USB CoreElec and a USB Ubuntu Mate from HK. And the Logitech K400r keyboard works.

Just not Manjaro ARM (i tried with auto detect on and off, and with DVI and HDMI, with the .uimg and the .img) and not with my LG Monitor/TV on my desk and not with the Microsoft Natural Ergonomic Keyboard.

Booting Manjaro ARM just doesn't work. And whatever I do, the LG TV/Monitor thing just keeps showing a black screen. Doesn't go to sleep though, stays on.

Also: Petitboot did succesfully boot a USB stick with Ubuntu Mate with my oldy Samsung monitor, but its resolution isn't supported so it's all garbled. (Not an issue with petitboot but with the odroid)

Also, all but the CoreElec are listed as NOLABEL. And: CoreElec is surprisingly good!

[Cosmicbase]

Hello I'm new here and inexperienced.

I go through my questions or my knowledge point by point, with the request for help.

1. I want to buy an Odroid CoreElec Edition.
     CE is already installed on mSD card and Android wants
     I install on a USB 3.0 64GB stick. The USB
     I already have a stick. I do not have an eMMC.
2. Are there differences between Spiboot Update and
Petitboot (dev.20190705)?
3. It says something from switch to mmc and switch to
spi.

you proceed updating SPI flash memory, strongly recommend remove eMMC and attach SD card while boot select switch is placed to MMC.

And

Please let me share the new version with some bug fixes. Click spiboot-201911-rc2.img to download. 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.

4. What is the difference?

Would be very nice if you can help me.

Many thanks.

[Cosmicbase]

Hello I'm new here and inexperienced.

I go through my questions or my knowledge point by point, with the request for help.

1. I want to buy an Odroid CoreElec Edition.
     CE is already installed on mSD card and Android wants
     I install on a USB 3.0 64GB stick. The USB
     I already have a stick. I do not have an eMMC.
2. Are there differences between Spiboot Update and
Petitboot (dev.20190705)?
3. It says something from switch to mmc and switch to
spi.

you proceed updating SPI flash memory, strongly recommend remove eMMC and attach SD card while boot select switch is placed to MMC.

And

Please let me share the new version with some bug fixes. Click spiboot-201911-rc2.img to download. 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.

4. What is the difference?

Would be very nice if you can help me.

Many thanks.

[tobetter]

@Cosmicbase, welcome to ODROID

1. If you like to run Android, I recommend having eMMC since it's fast and secure. Especially Android requires faster storage than others. CE Edition already ships pre-installed CE on uSD card.
2. The "Petitboot" is the main S/W for boot management and it's in SPI flash memory on ODROID-N2. SPI boot is the method to boot from SPI flash memory other than eMMC or uSD or USB, SPI boot update is the way to update the flash memory like a firmware upgrade. Instead of using the word "SPIBOOT", we call "Petitboot" which is S/W.
3. There is a tiny slide switch on the board, it is aimed to select boot storage within eMMC/MMC or SPI flash memory. Some users may need to use Petitboot while others are not. So if you like to play with multiple OS on ODROID-N2, you need the boot manager and in order to call Petitboot, you must place the boot switch to SPI. If you are just enough to boot from eMMC or uSD, place the switch to MMC.

Hope this helps you.

[Cosmicbase]

OK thanks. My English is terrible but I try it to understand.
1. I understand that I need Petitboot if I have several operating systems to choose from.
2. For this I have to set the switch to spi to select bootmenu between Android and CE.
3. I use the switch MMC in the presence of sd card to boot it (CE) and when I remove it boots eMMC (Android).
4. If switch is on MMC Petitboot is disabled.

Did I understand that correctly?

[tobetter]

OK thanks. My English is terrible but I try it to understand.
1. I understand that I need Petitboot if I have several operating systems to choose from.
2. For this I have to set the switch to spi to select bootmenu between Android and CE.
3. I use the switch MMC in the presence of sd card to boot it (CE) and when I remove it boots eMMC (Android).
4. If switch is on MMC Petitboot is disabled.

Did I understand that correctly?

All good, thank you for understanding my poor English too.