Jump to content

stocky70

Members
  • Posts

    4
  • Joined

  • Last visited

  1. @Igor I have attached my hardware info. armhwinfo.log
  2. Wow, thx for your very fast response. Yes, i can see eMMC will all its content. First of all. I retried the whole installation process and saw that "cubox i2eX" has been detected. (Has been shown at command line on first boot, and also in nand-sata-install script) Is this correct? I have only an IMX6 Solo processor (MicroSom i1) Can you provide me with the correct command line how i can write the boot loader to eMMC manually. dd if=SPL of=/dev/mmcblk1 bs=1K seek=1 dd if=u-boot.img of=/dev/mmcblk1 bs=1K seek=4 I think mmcbkl1 should be correct, because in my case mmcblk0 is the SD card. The "nand-sata-install" script also showed me "mmcblk1p1". Are the commands above ok? (i took them from solidrun homepage, but i think their pages are not really up to date)
  3. Hi community I have a HummingBoard2 and installed Armbian on SD (first boot device). And everything works really fine! !!!Thanks a lot for the perfekt installation routine!!! Afterwards i tried to install from SD to eMMC with the "sata-nand-install.sh" script. Installation completes without errors. If i boot with inserted SD card the system boots from SD without errors (for a fused (0x5=2840 and 0x6=10) IMX6Solo and also with unfused module) - fine! If i remove the SD card and use a fused (0x5 = 3040 and 0x6=10) IMX6Solo module, i think it tries to boot from eMMC but it doesn't work. When i try to boot with inserted SD card and fused (0x5 = 3040 and 0x6=10) module, i think it tries first to boot from eMMC (fails) and then from SD(works). !!! This is only one try to boot !!! U-Boot SPL 2013.10-rc4 (Feb 02 2017 - 02:27:27) Boot Device: SD0 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4 (Feb 02 2017 - 02:27:27) CPU: Freescale i.MX6SOLO rev1.3 at 792 MHz Reset cause: POR Board: MX6-HummingBoard2 DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Warning: failed to set MAC address (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Hit any key to stop autoboot: 3 2 1 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 1734 bytes read in 107 ms (15.6 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 28 bytes read in 93 ms (0 Bytes/s) 37020 bytes read in 193 ms (186.5 KiB/s) 4652417 bytes read in 362 ms (12.3 MiB/s) 4906976 bytes read in 384 ms (12.2 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x4adfe0 ] ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4652353 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c09b Starting kernel ... Uncompressing Linux... done, booting the kernel. Any ideas what is going wrong? Is it neccessary to do some manual changes in the environment.txt? For example to change the boot location, where u-boot / kernel should be installed? I do not understand, that all files (eMMC and SD) point to the same boot device, where they expect to find U-Boot / kernel. Thank's for you help in advance! (and sorry for my bad english)
  4. Hi community I have a HummingBoard2 and installed Armbian on SD (first boot device). And everything works really fine! !!!Thanks a lot for the perfekt installation routine!!! Afterwards i tried to install from SD to eMMC with the "sata-nand-install.sh" script. Installation completes without errors. If i boot with inserted SD card the system boots from SD without errors (for a fused (0x5=2840 and 0x6=10) IMX6Solo and also with unfused module) - fine! If i remove the SD card and use a fused (0x5 = 3040 and 0x6=10) IMX6Solo module, i think it tries to boot from eMMC but it doesn't work. When i try to boot with inserted SD card and fused (0x5 = 3040 and 0x6=10) module, i think it tries first to boot from eMMC (fails) and then from SD(works). !!! This is only one try to boot !!! U-Boot SPL 2013.10-rc4 (Feb 02 2017 - 02:27:27) Boot Device: SD0 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4 (Feb 02 2017 - 02:27:27) CPU: Freescale i.MX6SOLO rev1.3 at 792 MHz Reset cause: POR Board: MX6-HummingBoard2 DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Warning: failed to set MAC address (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Hit any key to stop autoboot: 3 2 1 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 1734 bytes read in 107 ms (15.6 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 28 bytes read in 93 ms (0 Bytes/s) 37020 bytes read in 193 ms (186.5 KiB/s) 4652417 bytes read in 362 ms (12.3 MiB/s) 4906976 bytes read in 384 ms (12.2 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x4adfe0 ] ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4652353 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c09b Starting kernel ... Uncompressing Linux... done, booting the kernel. Any ideas what is going wrong? Is it neccessary to do some manual changes in the environment.txt? For example to change the boot location, where u-boot / kernel should be installed? I do not understand, that all files (eMMC and SD) point to the same boot device, where they expect to find U-Boot / kernel. Thank's for you help in advance! (and sorry for my bad english)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines