ozhvankov Posted November 28, 2017 Share Posted November 28, 2017 Hi All! does anyone know how to resolve next error My custom board based on h3 this is oem china's set-top box right now Im used Beelink X2 for build image for some resone i need mainline kernel but if i buld image with mainline or dev I get the scoring result Quote U-Boot 2017.11-armbian (Nov 27 2017 - 20:54:33 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Beelink X2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 158 ms (1.4 MiB/s) starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 3 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) unable to get device descriptor (error=-1) 1 USB Device(s) found scanning bus 5 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 209 ms (16.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 175 bytes read in 169 ms (1000 Bytes/s) 5807625 bytes read in 756 ms (7.3 MiB/s) 6779416 bytes read in 853 ms (7.6 MiB/s) Found mainline kernel configuration 31210 bytes read in 616 ms (48.8 KiB/s) 1065 bytes read in 1419 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-spdif-out.dtbo 382 bytes read in 1353 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-cir.dtbo 4179 bytes read in 1367 ms (2.9 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5807561 Bytes = 5.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49a76000, end 49fffdc9 ... OK reserving fdt memory region: addr=43000000 size=6d000 Loading Device Tree to 49a06000, end 49a75fff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Loading, please wait... starting version 229 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=c4f45323-542b-4392-86c4-4664a3089878 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 68.551887] reboot: Restarting system When I build an image with a legacy kernel everything works although there is a usb error but I need a mainline kernel for docker and I upgrade system to mainline kernel and usb stop working tell me where to look or what you can fix ! Thanx Quote U-Boot SPL 2017.09-armbian (Nov 22 2017 - 13:56:04) DRAM: 1024 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC2 U-Boot 2017.09-armbian (Nov 22 2017 - 13:56:04 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Beelink X2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 1, SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 177 ms (1.2 MiB/s) starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 3 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) unable to get device descriptor (error=-1) 1 USB Device(s) found scanning bus 5 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 175 ms (20.5 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 324 bytes read in 212 ms (1000 Bytes/s) 5699229 bytes read in 753 ms (7.2 MiB/s) 6790944 bytes read in 835 ms (7.8 MiB/s) Found mainline kernel configuration 31210 bytes read in 326 ms (92.8 KiB/s) 1065 bytes read in 410 ms (2 KiB/s) Applying kernel provided DT overlay sun8i-h3-spdif-out.dtbo 382 bytes read in 456 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-cir.dtbo 4179 bytes read in 290 ms (13.7 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5699165 Bytes = 5.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49a90000, end 49fff65d ... OK reserving fdt memory region: addr=43000000 size=6d000 Loading Device Tree to 49a20000, end 49a8ffff ... OK Starting kernel ... Link to comment Share on other sites More sharing options...
Igor Posted November 28, 2017 Share Posted November 28, 2017 Is any of those working for you: https://dl.armbian.com/beelinkx2/nightly/ Docker is supported out of the box. Image building might be broken at the moment. Try building by using latest stable tag: https://github.com/armbian/build/tree/v2017.11 Link to comment Share on other sites More sharing options...
ozhvankov Posted November 28, 2017 Author Share Posted November 28, 2017 Hello Igor ! thanx for U post I tested many images for some reson i need this patch - @@ -4,7 +4,7 @@ -CONFIG_MMC0_CD_PIN="PH13" +CONFIG_MMC0_CD_PIN="" but every day I build custom image's with different patches PS thank U for this project - very cool Link to comment Share on other sites More sharing options...
Igor Posted November 28, 2017 Share Posted November 28, 2017 Understand. Just after release, we switched to more recent u-boot and some patches were adjusted ... This is most likely THE problem. Try to use our build script tagged with v2017.11 as mentioned. Thank you! Link to comment Share on other sites More sharing options...
ozhvankov Posted November 28, 2017 Author Share Posted November 28, 2017 ok start to build image based on u-boot v2017.11 1 or 2 days ago ok be waiting Link to comment Share on other sites More sharing options...
Igor Posted November 28, 2017 Share Posted November 28, 2017 8 minutes ago, ozhvankov said: start to build image based on u-boot v2017.11 No. Start to build with build script v2017.11 which has a known working configuration based on U-boot v2017.09 Link to comment Share on other sites More sharing options...
ozhvankov Posted November 28, 2017 Author Share Posted November 28, 2017 hmmm sounds interesting must to test right now! Link to comment Share on other sites More sharing options...
ozhvankov Posted November 30, 2017 Author Share Posted November 30, 2017 Hello again! maybe i do something wrong ?! Igor can U give me some simple example what I can to edit ? and how to ? for build image with main line build script but with 2017.09 rewrite files or something smarter ? ))) thanx All my attempts did not have a positive result ((( Link to comment Share on other sites More sharing options...
ozhvankov Posted December 11, 2017 Author Share Posted December 11, 2017 good evening colleagues. unfortunately I can not solve the problem with yusb scanning bus 3 for devices ... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) unable to get device descriptor (error = -1) 1 USB Device (s) found scanning bus 5 for devices ... 1 USB Device (s) found scanning usb for storage devices ... 0 Storage Device (s) I tried various build scripts different versions of u-boot various fex settings 3.4.113 kernel usb work fine next build (4.13(14)) usb don't work dev build cant boot any help??? thanx Link to comment Share on other sites More sharing options...
Recommended Posts