Viald

Members
  • Content Count

    50
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by Viald

  1. Yes I have a N2. Could you please point me the link ? I'm using your odroid-n2 SPI u-boot image https://yadi.sk/d/pHxaRAs-tZiei/UPDATE_U-BOOT_odroid_n2
  2. It seems that the 5.99 kernel package doesn't install meson-g12b-odroid-n2.dtb file in dtb directory. It only installs amlogic and rockchip directories. Update: My bad the file is in amlogic directory. I have to modify my boot.ini file.
  3. ii linux-buster-root-aml-g12 5.98 arm64 Armbian tweaks for buster on aml-g12 (default branch) ii linux-u-boot-aml-g12-default 5.98 arm64 Uboot loader 2019.07-rc3 @balbes150 What about those one ?
  4. root@jdm:~# dpkg -l | grep dtb ii linux-dtb-aml-g12 5.98 arm64 Linux DTB, version 5.3.0-aml-g12 Indeed ! Should I have to reinstall 5.99 after removing linux-dtb-aml-g12 ? And should it solves my UAS issue ?
  5. I have added this option in boot.ini file to blacklist the UAS driver usb-storage.quirks=2109:0715:u
  6. @balbes150 it seems that you enabled UAS driver in 5.99. It hangs my system at boot time
  7. @balbes150 What's new in 5.99 ?
  8. root@jdm:~# tar cvf ~/boot.051219.tar /boot root@jdm:~# dpkg -l | grep linux-image ii linux-image-aml-g12 5.98 arm64 Linux kernel, version 5.3.0-aml-g12 root@jdm:~# sudo apt-get purge linux-image-aml-g12 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-aml-g12* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 110 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 53311 files and directories currently installed.) Removing linux-image-aml-g12 (5.98) ... update-initramfs: Deleting /boot/initrd.img-5.3.0-aml-g12 (Reading database ... 51042 files and directories currently installed.) Purging configuration files for linux-image-aml-g12 (5.98) ... dpkg: warning: while removing linux-image-aml-g12, directory '/boot/dtb' not empty so not removed root@jdm:~# apt update Hit:1 https://deb.nodesource.com/node_12.x buster InRelease Hit:2 http://mirrors.dotsrc.org/armbian-apt buster InRelease Hit:3 http://security.debian.org buster/updates InRelease Hit:4 http://cdn-fastly.deb.debian.org/debian buster InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease Hit:6 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@jdm:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@jdm:~# apt install linux-image-aml-g12 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: linux-image-aml-g12 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/27.2 MB of archives. After this operation, 141 MB of additional disk space will be used. Selecting previously unselected package linux-image-aml-g12. (Reading database ... 51041 files and directories currently installed.) Preparing to unpack .../linux-image-aml-g12_5.99_arm64.deb ... Unpacking linux-image-aml-g12 (5.99) ...######################................................................................................................................................................................................] Setting up linux-image-aml-g12 (5.99) ...#################################################################....................................................................................................................................] update-initramfs: Generating /boot/initrd.img-5.3.0-aml-g12###########################################################################################........................................................................................] update-initramfs: Converting to u-boot format root@jdm:~# apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://mirrors.dotsrc.org/armbian-apt buster InRelease Hit:3 https://deb.nodesource.com/node_12.x buster InRelease Hit:4 http://cdn-fastly.deb.debian.org/debian buster InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease Hit:6 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@jdm:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@jdm:~# dpkg -l | grep linux-image ii linux-image-aml-g12 5.99 arm64 Linux kernel, version 5.3.0-aml-g12 5.99 And voila root@jdm:/boot# uname -a Linux jdm 5.3.0-aml-g12 #5.98 SMP PREEMPT Tue Oct 8 12:22:08 MSK 2019 aarch64 GNU/Linux Need to reboot
  9. Thank you all for your help. I'm running the server release so I can't use Synaptic. I will try with apt command.
  10. I just tried, still the same issue trying to "Unpacking linux-image-aml-g12 (5.99) over (5.98)"
  11. May I wrong, the kernel update comes from @balbes150 and it's not an official update. If I want a official Debian release, where can I find it ?
  12. Ok, but I didn't plan to do a complete new installation and I want my system to be up to date. So how can I do ?
  13. Hello. I have an error when trying to upgrade the kernel root@jdm:/boot# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-aml-g12 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/27.2 MB of archives. After this operation, 31.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Reading changelogs... Done (Reading database ... 53286 files and directories currently installed.) Preparing to unpack .../linux-image-aml-g12_5.99_arm64.deb ... Unpacking linux-image-aml-g12 (5.99) over (5.98) .............................................................................................................................................................................................] dpkg: error processing archive /var/cache/apt/archives/linux-image-aml-g12_5.99_arm64.deb (--unpack): unable to make backup link of './boot/System.map-5.3.0-aml-g12' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) mv: cannot stat '/boot/vmlinuz-5.3.0-aml-g12': No such file or directory......................................................................................................................................................................] Errors were encountered while processing: /var/cache/apt/archives/linux-image-aml-g12_5.99_arm64. The content of /boot root@jdm:/boot# ll total 40802 drwxr-xr-x 2 root root 2048 Oct 4 12:21 'System Volume Information' -rwxr-xr-x 1 root root 4381366 Oct 8 11:22 System.map-5.3.0-aml-g12 -rwxr-xr-x 1 root root 660 Oct 2 09:01 aml_autoscript -rwxr-xr-x 1 root root 588 Oct 2 09:01 aml_autoscript.cmd -rwxr-xr-x 1 root root 651 Oct 2 09:01 aml_autoscript.zip -rwxr-xr-x 1 root root 1536 Oct 2 09:01 armbian_first_run.txt.template -rwxr-xr-x 1 root root 4882 Oct 2 09:01 boot-desktop.png -rwxr-xr-x 1 root root 38518 Oct 2 09:01 boot.bmp -rwxr-xr-x 1 root root 709 Oct 2 09:09 boot.ini -rwxr-xr-x 1 root root 177990 Oct 8 11:22 config-5.3.0-aml-g12 drwxr-xr-x 3 root root 6144 Oct 16 12:49 dtb drwxr-xr-x 2 root root 6144 Oct 2 09:00 dtb-5.3.0-aml-g12 -rwxr-xr-x 1 root root 679 Oct 2 09:01 emmc_autoscript -rwxr-xr-x 1 root root 607 Oct 2 09:01 emmc_autoscript.cmd drwxr-xr-x 2 root root 2048 Oct 2 09:01 extlinux -rwxr-xr-x 1 root root 7934926 Nov 17 13:42 initrd.img-5.3.0-aml-g12 drwxr-xr-x 2 root root 2048 Oct 12 12:02 old -rwxr-xr-x 1 root root 1112 Oct 2 09:01 s905_autoscript -rwxr-xr-x 1 root root 1040 Oct 2 09:01 s905_autoscript.cmd -rwxr-xr-x 1 root root 209 Oct 2 09:01 uEnv.ini -rwxr-xr-x 1 root root 7934990 Nov 17 13:42 uInitrd -rwxr-xr-x 1 root root 21262344 Oct 8 11:22 zImage root@jdm:/boot# And the kernel release: root@jdm:/boot# uname -a Linux jdm 5.3.0-aml-g12 #5.98 SMP PREEMPT Tue Oct 8 12:22:08 MSK 2019 aarch64 GNU/Linux Thank you
  14. @balbes150 I have to go back to your kernel. Mine have strange issue. The system reboots without any reason. I have no error coming from the UAS driver in the syslog. Even with your kernel, I have noticed that reboot doesn't really work. The system stops, but the hardware doesn't restart. Could be a pain for a headless server.
  15. @qstaq Done Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M @balbes150 I will keep you informed if I have any issue with UAS driver.
  16. Thank you @balbes150 Perhaps you plan to add UAS driver in your next release ?
  17. I succeed in building a new kernel with UAS driver. I have an issue when I want to install the .deb package. The same issue when I do 'apt upgrade' with a new kernel release available. Preparing to unpack .../linux-image-aml-g12_5.98_arm64.deb ... Unpacking linux-image-aml-g12 (5.98) over (5.98) ..........................................................................................................................................................................................] dpkg: error processing archive /var/cache/apt/archives/linux-image-aml-g12_5.98_arm64.deb (--unpack): unable to make backup link of './boot/System.map-5.3.0-aml-g12' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) mv: cannot stat '/boot/vmlinuz-5.3.0-aml-g12': No such file or directory...................................................................................................................................................................] Preparing to unpack .../nodejs_12.11.1-1nodesource1_arm64.deb ... Detected old npm client, removing...#########################..............................................................................................................................................................................] Unpacking nodejs (12.11.1-1nodesource1) over (12.10.0-1nodesource1) ... Errors were encountered while processing:##################################................................................................................................................................................................] /var/cache/apt/archives/linux-image-aml-g12_5.98_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
  18. I think that the driver is not available on my release root@jdm:~# lsmod Module Size Used by cdc_acm 36864 2 bnep 32768 2 zstd 16384 6 zram 32768 2 btusb 53248 0 btrtl 24576 1 btusb btbcm 16384 1 btusb btintel 28672 1 btusb bluetooth 552960 26 btrtl,btintel,btbcm,bnep,btusb ecdh_generic 16384 2 bluetooth ecc 32768 1 ecdh_generic ftdi_sio 65536 1 rfkill 28672 3 bluetooth option 57344 0 usb_wwan 24576 1 option usbserial 53248 5 ftdi_sio,usb_wwan,option crct10dif_ce 16384 1 snd_soc_meson_axg_sound_card 20480 1 ir_nec_decoder 20480 0 dw_hdmi_cec 16384 0 meson_ir 16384 0 ao_cec_g12a 16384 0 snd_soc_meson_axg_tdmout 20480 1 snd_soc_meson_axg_frddr 24576 3 snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout ip_tables 32768 0 x_tables 40960 1 ip_tables ipv6 503808 54 nf_defrag_ipv6 24576 1 ipv6 crc_ccitt 16384 1 ipv6 rtc_pcf8563 24576 0 mdio_mux_meson_g12a 16384 0 root@jdm:~# modprobe uas modprobe: FATAL: Module uas not found in directory /lib/modules/5.3.0-aml-g12
  19. I confirm, after many reboots, I do not face SSD detection failure anymore. Thank you @balbes150 and @qstaq for your precious help.
  20. Does Armbian support UAS driver ? The driver used for my disk is usb-storage Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M When I plug it on Ubuntu, the driver used is UAS. Port 1: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
  21. For information, I just did tests with my new enclosure and it works well. The SSD is well detected at each boot. I noticed that the usb scanning duration at boot time is much longer than with the first enclosure. The chipset JMS567 is the exactly the same than the old one. But it's not the same brand.
  22. Here it is G12B:BL:6e7c85:7898ac;FEAT:E0F83180:402000;POC:B;RCY:0;SPINOR:0;0. 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:0000c067 L3:14000020 B2:00402000 B1:e0f83180 TE: 58313 BL2 Built : 06:17:13, Jun 28 2019. g12b gf0505d7-dirty - qi.duan@dr oid13 Board ID = 4 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: 00012ba5 DDR driver_vesion: LPDDR4_PHY_V_0_1_14 build time: Jun 28 2019 06:1 7:09 board id: 4 Load FIP HDR from SPI, src: 0x00010000, des: 0xfffd0000, size: 0x00 004000, part: 0 fw parse done Load ddrfw from SPI, src: 0x00030000, des: 0xfffd0000, size: 0x0000 c000, part: 0 Load ddrfw from SPI, src: 0x0002c000, des: 0xfffd0000, size: 0x0000 4000, part: 0 PIEI prepare done fastboot data load fastboot data verify verify result: 255 Cfg max: 1, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz Load ddrfw from SPI, src: 0x00014000, des: 0xfffd0000, size: 0x0000 c000, 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: 0x0000 c000, 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==106 ps 9 R1_RxClkDly_Margin==0 ps 0 R1_TxDqDly_Margi==0 ps 0 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 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==435 bdlr_100_min==435 bdlr_100_max==43 5 bdlr_100_cur==435 aft test bdlr_100_average==435 bdlr_100_min==435 bdlr_100_max==43 5 bdlr_100_cur==435 non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 435 result report boot times 0Enable ddr reg access Load FIP HDR from SPI, src: 0x00010000, des: 0x01700000, size: 0x00 004000, part: 0 Load BL3X from SPI, src: 0x0003c000, des: 0x0172c000, size: 0x00094 c00, 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@droi d11-sz] OPS=0x40 ring efuse init chipver efuse init 29 0a 40 00 01 13 0f 00 00 07 31 32 54 52 4d 50 [0.019859 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 (Oct 03 2019 - 13:03:26) DRAM: 3.5 GiB Relocation Offset is: d6ef3000 spi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 00000000d7f84a50 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 paramete rs 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 stora ge 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 emmc/sd response timeout, cmd1, status=0x1bf2800 Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) foun d No storage devices, perhaps not 'usb start'ed..? USB device tree: 1 Hub (5 Gb/s, 0mA) | u-boot XHCI Host Controller | +-2 Hub (480 Mb/s, 100mA) GenesysLogic USB2.1 Hub 1: Hub, USB Revision 3.0 - u-boot XHCI Host Controller - Class: Hub - PacketSize: 9 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Hub, USB Revision 2.10 - GenesysLogic USB2.1 Hub - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x05e3 Product 0x0610 Version 147.4 Configuration: 1 - Interfaces: 1 Self Powered Remote Wakeup 100mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) foun d ## Attempting fetch boot.ini in usb:0... ** Bad device usb 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in usb:0... ** Bad device usb 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in usb:0... ** Bad device usb 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in usb:0... ** Bad device usb 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.ini in usb:1... ** Bad device usb 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in usb:1... ** Bad device usb 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in usb:1... ** Bad device usb 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in usb:1... ** Bad device usb 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.ini in usb:2... ** Bad device usb 2 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in usb:2... ** Bad device usb 2 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in usb:2... ** Bad device usb 2 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in usb:2... ** Bad device usb 2 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.ini in usb:3... ** Bad device usb 3 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in usb:3... ** Bad device usb 3 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in usb:3... ** Bad device usb 3 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in usb:3... ** Bad device usb 3 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.ini in mmc:0... 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 emmc/sd response timeout, cmd1, status=0x1bf2800 ** Bad device mmc 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in mmc:0... 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 emmc/sd response timeout, cmd1, status=0x1bf2800 ** Bad device mmc 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in mmc:0... 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 emmc/sd response timeout, cmd1, status=0x1bf2800 ** Bad device mmc 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in mmc:0... 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 emmc/sd response timeout, cmd1, status=0x1bf2800 ** Bad device mmc 0 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.ini in mmc:1... card out ** Bad device mmc 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in mmc:1... card out ** Bad device mmc 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in mmc:1... card out ** Bad device mmc 1 ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.scr in mmc:1... card out ** Bad device mmc 1 ** ## Executing script at 04000000 Wrong image format for "source" command 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 emmc/sd response timeout, cmd1, status=0x1bf2800 movi: not registered partition name, boot 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 stora ge device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only movi: not registered partition name, dtbs 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 stora ge device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed Bad Linux ARM64 Image magic! ee_gate_off ... Wrong Image Format for bootm command ERROR: can't get kernel image! [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed ee_gate_on ... card out movi: not registered partition name, boot 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 stora ge device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only movi: not registered partition name, dtbs 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 stora ge device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed Bad Linux ARM64 Image magic! ee_gate_off ... Wrong Image Format for bootm command ERROR: can't get kernel image! [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed ee_gate_on ... Speed: 1000, full duplex BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.1.162 (822 ms) Retrieving file: pxelinux.cfg/909802f2-a1dd-11e8-98d0-529269fb1459 Speed: 1000, full duplex Using dwmac.ff3f0000 device TFTP from server 192.168.1.2; our IP address is 192.168.1.162 Filename 'pxelinux.cfg/909802f2-a1dd-11e8-98d0-529269fb1459'. Load address: 0x1070000 Loading: T T
  23. I saw some options about usb boot. I don't know what are their impact. Is there any documentation ?
  24. Thank you for your search and feedback. I will buy a new one tomorrow and do new tests. For information, I have no problem when testing with an USB flash drive. That sounds effectively an issue with the enclosure.