Search the Community

Hi. I have a bunch of HummingBoard2 boards that have been used by a company called Vivo. Basically they allow schools to transfer video through Ethernet to monitors and projectors. I also want to do this but Vivi is a subscription based system so that SUX! I therefore want to blow Vivi away and load a clean Armbian. My issue is that the boards have no SD cards soldered to the board. They have power, 2xUSB, RJ45, HDMI connectors. They must therefore boot from eMMC. I found info on the board manufactures website., SolidRun, on how to use jumpers to select boot type. It was set to eMMC so I set it to USB and flashed a SD card with Armbian 20.20 and rebooted. Alas it didn't work, it didn't even try and read the USB port with the flashed SD card. I then hooked up an FTDI to the onboard UART and got connected. I don't have the password so had to stop it booting and try and access the system that way. My problem is after the boot interruption it doesn't have any file structure so I can't edit files to change boot sequence or passwords. I can't mount the eMMC to edit the files to remove the root password or anything like that. Any suggestions as to how I can unlock this board and load a normal Armbian on to it? Cheers

hello, i struggle to boot linux kernel again in SDCard hummingboard pulse. before this i try to make U-boot in the emmc but failure. i want back to use linux kernel from SDcard again but stuck in this U-boot preview and the problem is ** File not found /boot/dtbs/5.10.72-imx8-sr/imx8mq-hummingboard-pulse.dt* ** File not found /boot/vmlinuz ** in mmc0 and ** File not found /boot/vmlinuz-5.10.72-imx8-sr ** ** File not found /boot/vmlinuz ** in mmc1 this the picture when i try to remote from minicom https://drive.google.com/file/d/15y_Q00i5NHM4h_rmrifiZSVvat8FuJmF/view?usp=sharing

Hello! I'm trying to boot latest releases of of Armbian (following images: Armbian_21.02.3_Cubox-i_buster_current_5.10.21.img and Armbian_21.02.3_Cubox-i_focal_current_5.10.21.img) on a Solid-Run Hummingboard2 Gate V1.4 board. (Board V1.2 freeze during Uboot) I'm getting to the "Starting kernel" message but after that things stop. Switching on the verbose output in ArmbianEnv.txt result in the output below where the kernel always stop at message: [ 0.000000] Freeing unused kernel memory: 2048K Do anyone have any thoughts/ideas here on what could possibly be the problem stopping the kernel from booting? U-Boot SPL 2018.01-armbian (Mar 08 2021 - 10:51:22) Trying to boot from MMC1 U-Boot 2018.01-armbian (Mar 08 2021 - 10:51:22 +0000) CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 38C Reset cause: POR Board: MX6 HummingBoard2 Watchdog enabled DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment No panel detected: default to HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2091 bytes read in 104 ms (19.5 KiB/s) ## Executing script at 12000000 0 bytes read in 72 ms (0 Bytes/s) 147 bytes read in 88 ms (1000 Bytes/s) 37976 bytes read in 1600 ms (22.5 KiB/s) 21327224 bytes read in 19315 ms (1.1 MiB/s) 10707456 bytes read in 650 ms (15.7 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 21327160 Bytes = 20.3 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 1800c457 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.10.21-imx6 (root@hirsute) (arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #21.02.3 SMP Mon Mar 8 07:05:20 UTC 2021 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: SolidRun Cubox-i Dual/Quad [ 0.000000] printk: debug: ignoring loglevel setting. [ 0.000000] Memory policy: Data cache writeback [ 0.000000] efi: UEFI not found. [ 0.000000] cma: Size (0x10000000) of region at 0x80000000 exceeds limit (0x30000000) [ 0.000000] cma: Failed to reserve 256 MiB [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000010000000-0x000000002fffffff] [ 0.000000] Normal empty [ 0.000000] HighMem empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000010000000-0x000000002fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000010000000-0x000000002fffffff] [ 0.000000] On node 0 totalpages: 131072 [ 0.000000] DMA zone: 1152 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 131072 pages, LIFO batch:31 [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] percpu: Embedded 19 pages/cpu s46924 r8192 d22708 u77824 [ 0.000000] pcpu-alloc: s46924 r8192 d22708 u77824 alloc=19*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129920 [ 0.000000] Kernel command line: root=UUID=17df30e5-6838-4ce3-b871-47f297687856 rootfstype=ext4 rootwait console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1920x1080m60,if=RGB24,bpp=32 coherent_pool=2M cma=256M@2G rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi vt.global_cursor_default=0 loglevel=7 usb-storage.quirks= earlyprintk ignore_loglevel [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 476608K/524288K available (10511K kernel code, 2391K rwdata, 5352K rodata, 2048K init, 532K bss, 47680K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] random: get_random_u32 called from __kmem_cache_create+0x28/0x324 with crng_init=0 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 47647 entries in 94 pages [ 0.000000] ftrace: allocated 94 pages with 5 groups [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC physical location is 0xa01000 [ 0.000000] L2C-310 erratum 769419 enabled [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 ID prefetch enabled, offset 16 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 cache controller enabled, 16 ways, 512 kB [ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76450001 [ 0.000000] Switching to timer-based delay loop, resolution 333ns [ 0.000000] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns [ 0.000000] clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=3000) [ 0.000000] pid_max: default: 32768 minimum: 301 [ 0.000000] LSM: Security Framework initializing [ 0.000000] Yama: becoming mindful. [ 0.000000] SELinux: Initializing. [ 0.000000] TOMOYO Linux initialized [ 0.000000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.000000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.000000] CPU: Testing write buffer coherency: ok [ 0.000000] CPU0: Spectre v2: using BPIALL workaround [ 0.000000] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.000000] Setting up static identity map for 0x10300000 - 0x103000ac [ 0.000000] rcu: Hierarchical SRCU implementation. [ 0.000000] EFI services will not be available. [ 0.000000] smp: Bringing up secondary CPUs ... [ 0.000000] smp: Brought up 1 node, 1 CPU [ 0.000000] SMP: Total of 1 processors activated (6.00 BogoMIPS). [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] devtmpfs: initialized [ 0.000000] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.000000] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 0.000000] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.000000] pinctrl core: initialized pinctrl subsystem [ 0.000000] DMI not present or invalid. [ 0.000000] NET: Registered protocol family 16 [ 0.000000] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.000000] audit: initializing netlink subsys (disabled) [ 0.000000] thermal_sys: Registered thermal governor 'fair_share' [ 0.000000] thermal_sys: Registered thermal governor 'step_wise' [ 0.000000] thermal_sys: Registered thermal governor 'user_space' [ 0.000000] cpuidle: using governor menu [ 0.000000] CPU identified as i.MX6DL, silicon rev 1.3 [ 0.000000] imx6q_suspend_init: failed to get iomuxc base -19! [ 0.000000] imx6_pm_common_init: No DDR LPM support with suspend -19! [ 0.000000] No ATAGs? [ 0.000000] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.000000] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.000000] debugfs: Directory 'dummy-iomuxc-gpr@20e0000' with parent 'regmap' already present! [ 0.000000] imx6q-pinctrl 20e0000.pinctrl: initialized IMX pinctrl driver [ 0.000000] Serial: AMBA PL011 UART driver [ 0.000000] Kprobes globally optimized [ 0.000000] audit: type=2000 audit(0.052:1): state=initialized audit_enabled=0 res=1 [ 0.000000] cryptd: max_cpu_qlen set to 1000 [ 0.000000] raid6: skip pq benchmark and using algorithm neonx8 [ 0.000000] raid6: using neon recovery algorithm [ 0.000000] vcc_3v3: supplied by v_5v0 [ 0.000000] v_usb2: supplied by v_5v0 [ 0.000000] v_usb1: supplied by v_5v0 [ 0.000000] iommu: Default domain type: Translated [ 0.000000] vgaarb: loaded [ 0.000000] SCSI subsystem initialized [ 0.000000] libata version 3.00 loaded. [ 0.000000] usbcore: registered new interface driver usbfs [ 0.000000] usbcore: registered new interface driver hub [ 0.000000] usbcore: registered new device driver usb [ 0.000000] pps_core: LinuxPPS API ver. 1 registered [ 0.000000] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.000000] PTP clock support registered [ 0.000000] EDAC MC: Ver: 3.0.0 [ 0.000000] NetLabel: Initializing [ 0.000000] NetLabel: domain hash size = 128 [ 0.000000] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.000000] NetLabel: unlabeled traffic allowed by default [ 0.000000] clocksource: Switched to clocksource mxc_timer1 [ 0.000000] VFS: Disk quotas dquot_6.6.0 [ 0.000000] VFS: Dquot-cache hash table entries [ 0.000000] Segment Routing with IPv6 [ 0.000000] NET: Registered protocol family 17 [ 0.000000] ThumbEE CPU extension supported. [ 0.000000] Registering SWP/SWPB emulation handler [ 0.000000] registered taskstats version 1 [ 0.00000scrypt registered [ 0.000000] Key type fscrypt-provisioning registered [ 0.000000] Btrfs loaded, crc32c=crc32c-generic [ 0.000000] Key type encrypted registered [ 0.000000] ima: No TPM chip found, activating TPM-bypass! [ 0.000000] ima: Allocated hash algorithm: sha256 [ 0.000000] ima: No architecture policies found [ 0.000000] Freeing unused kernel memory: 2048K

Hello, I have recently tried a more recent kernel 5.10.x for my HummingBoard with imx6 solo. After playing with GPU/OpenGL acceleration I have noticed that there is no H.264/MJPEG Video acceleration present in the kernel. The video codec Chips&Media 960 driver module (kernel option VIDEO_CODA) is simply not build in. Why is that? Can it be enabled by default for future IMX6 builds? Thanks for your support!!

Hi, I've just created a SD-card with Armbian Bionic (mainline kernel 4.19.y) for a Hummingboard Gate. I noticed during boot that it says it uses U-boot version 2013.10-rc4. This seems quite old compared to the 2018 version that was on the Debian Stretch image from SolidRun. I've tried to search the internet to see what the impact of something like this is and wasn't able to find something that made sense to me (could be entirely my fault). I therefore have the question: Is the U-boot version intentional? (maybe it has some features that newer versions have dropped.)

This post is, more or less, a continuation of something I started here, but adapted to Armbian. I will start with an overview of what I have done (maybe this is relevant) and finish with my questions. What I've done: I have a Hummingboard Gate with a Mikrobus RS485 click 3.3V (this one: https://www.mikroe.com/rs485-33v-click). In order to make this work I need to change a few things in de device tree. The dtb that my board uses is 'imx6dl-hummingboard2.dtb' so I copy that file to my home directory for safe keeping. cd ~ sudo cp /boot/dtb-4.19.18-cubox/imx6dl-hummingboard2.dtb . Then I convert this dtb to a dts: sudo dtc -I dtb -O dts -o imx6dl-hummingboard2.dts imx6dl-hummingboard2.dtb I looked for the pwm1grp to find the phandle of the group that is using the pin I need to use as the RTS-pin. Using this phandle I find 'pwm@2080000' in which I change the status to 'disabled'. If I understand correctly, this will free the pin for RTS use (but I might be wrong... Device trees might as well be magic to me). Next I find uart3. This is the uart that is on the Mikrobus-connector. For the clickboard I use, I need to swap RX en TX (don't ask me why). I change the uart3-entry from: hummingboard2-uart3 { fsl,pins = <0x168 0x538 0x0 0x2 0x0 0x1b0b1 0x164 0x534 0x90c 0x2 0x0 0x40013000>; phandle = <0x4b>; }; to: hummingboard2-uart3 { fsl,pins = <0x168 0x538 0x90c 0x2 0x1 0x1b0b1 0x164 0x534 0x0 0x2 0x0 0x1b0b1>; phandle = <0x4b>; }; This switches the RX en TX function on the pins. Note that I do not completely understand the significance of the "0x40013000" and "0x1b0b1". Perhaps I have chosen the wrong value (see question 2 below). Using the phandle in uart3, I find the serial-definition that I am using: "serial@21ec000". This is the serial to which I add definition for the rs485. I end up with: serial@21ec000 { compatible = "fsl,imx6q-uart", "fsl,imx21-uart"; reg = <0x21ec000 0x4000>; interrupts = <0x0 0x1c 0x4>; clocks = <0x4 0xa0 0x4 0xa1>; clock-names = "ipg", "per"; dmas = <0x13 0x1d 0x4 0x0 0x13 0x1e 0x4 0x0>; dma-names = "rx", "tx"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0x4b>; rs485-rts-delay = <0x0 0xc8>; linux,rs485-enabled-at-boot-time; rts-gpios = <0x2f 0x1d 0x0>; }; I've added the last 3 entries. The rest is unchanged. I now compile the changed dts with: sudo dtc -I dts -O dtb -o imx6dl-hummingboard2-changed.dtb imx6dl-hummingboard2.dts And copy the result to the dtb-directory (See question 1 below). sudo cp imx6dl-hummingboard2-changed.dtb /boot/dtb-4.19.18-cubox/imx6dl-hummingboard2.dtb Now I reboot my board and the result is a board with a working rs485 connection. I use this board to communicate with a modbus-rs485-device. Every now and then I see the following error message in syslog: "localhost kernel: imx-uart 21ec000.serial: DMA transaction error." Luckily this doesn't completely disturb the board. It is able to continue (see question 3 below). My questions: Question 1: Right now I am overwriting the dtb in /boot/dtb-4.19.18-cubox/ with my custom dtb. Is there a better way to do this? Question(s) 2: Am I using the right values in the RX/TX-swap? Any idea how I would find this out? Question(s) 3: What does the "imx-uart 21ec000.serial: DMA transaction error." mean? Any ideas how to fix it? (I've tried searching the web, but to no avail as of yet... as I said before: "Device trees might as well be magic to me").

Hi Sir/Madam, I am using Humming bard Gate for testing, i am trying to interface a minipcie of 4G module L718 from Fibocom. I am using Armbain platforn for testing. i am unable to interface the Module and use the module to access internet(Use as mobile broadband). Kindly support

So I downloaded Armbian Stretch image here https://www.armbian.com/hummingboard-2/ and dd it onto an SD Card. As it didn't produce any output during boot after 'uncompressing kernel' I had to add 'console=both' into the armbianEnv.txt. After that I could see that I land into (initramfs). It looked like it couldn't see the rootfs for some reason. So additionally I've changed rootdev to 'rootdev=/dev/mmcblk0p1' in the armbianEnv.txt. Still the same problem here is the full boot log https://pastebin.com/K64xKHBd What am I doing wrong? 2. Provided that the problem above is easy to fix, how do I start a script after the first boot? Solidrun images have /etc/runonce.d/ scripts but nothing like that in Armbian rootfs. I've seen a template in the /boot but is it possible to start a script to allocate a new partition after the first boot? The only reason why I want to try Armbian is because I cannot use Solidrun image to boot from eMMC with the v1.5 SOC. And I've seen some patches merged into Armbian to solve this problem

I have lots of HummingBoards 2 Edge with eMMC but now got a batch with the new SOM 1.5 and eMMC the original u-boot from next and stable branch (2013-10rc4) get stuck on SPL from time to time on the new SOMs so I'm trying the dev branch which has this new patch: https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-cubox-next/U-Boot-mx6cuboxi-add-support-for-detecting-Revision-1.5-SoMs.patch Copying SPL and u-boot.img to eMMC and booting produce the following: U-Boot SPL 2018.03-armbian (Jun 07 2018 - 16:06:14 -0400) Trying to boot from MMC1 Card did not respond to voltage select! spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### But if I have a SD card which has the old u-boot: U-Boot SPL 2018.03-armbian (Jun 07 2018 - 16:06:14 -0400) Trying to boot from MMC1 U-Boot 2013.10-rc4 (May 11 2018 - 13:06:31) CPU: Freescale i.MX6DL rev1.3 at 792 MHz Reset cause: POR Board: MX6-HummingBoard2 DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 HummingBoard2 U-Boot > And everything goes fine. So it seems that the SPL tries MMC1 which I suppose is SD card so when no card is inserted it get stuck. But when booting from eMMC it does read SPL from eMMC but the new SPL try to read uboot from SD, So how can I force MMC2_2 (I guess this is eMMC) inside the code or see if the new SPL honours the HummingBoards jumpers. TIA

Hello, I'm newbie on freescale imx6. I've just bought a hummingBoard2 rev1.4. A modem SIMCOM7600E mcpie is attached. When I used ignition and install debian, it's works but I 've a problem with the driver of this modem, the WWAN is not configured. ATCOMMAND works fine but I would like to use it by wwan interface and I didn't know how to put the driver file.c! I decided to install armbian_5.38 debian or ubuntu but my hummingboard doesn't boot. The autoboot stop at ##Flattend Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 after this I had "No signal" on my HDMI screen. I use a µSDHC1 Transcend 8Go. She is erased by SDFORMATTER and I use win32diskimager for the.img. How can I do for my H2 works fine? Thanks in advance.

Hello. I have been running Armbian_5.41_Cubox-i_Ubuntu_xenial_next_4.15.7_desktop.img with no issues on my Hummingboard Edge which consists of rev 1.4 Hummingboard2 carrier and rev 1.5 SOM. I decided to try the legacy image (Armbian_5.41_Cubox-i_Ubuntu_xenial_default_3.14.79_desktop.img) to gain support for the hardware video decoder. However, I have been unable to get the legacy version to boot properly. Initially, the board is detected as having a rev 1.5 SOM and there is a message about not being able to find the right dtb file (imx6q-hummingboard2-som-v15.dtb). Looking under /boot/dtb there are no dtb files for the rev 1.5 SOM in the legacy image. So I copied the default imx6q-hummingboard2-som-v15.dtb from my 'next' image into the dtb folder of my legacy image. Now I no longer see the message about the missing dtb file, but the boot process stops at "Starting kernel ..." Does anyone have any ideas what may be the problem? Is the legacy image compatible with the rev 1.5 SOM? Thanks in advance to anyone that can help. I sure appreciate it. Thanks, Dale

I am unable to boot the latest armbian version on my hummingboard using a MicroSoM i1 rev. 1.5. It seems to be an DTB problem. The boot error is "no valid device tree binary" Does anybody have the same problem or a solution?

Hello, I am having a problem using the uart and I guess it is related with this topic. I am trying to make my Hummingboard to communicate via UART with a serial ublox GPS. I identified that the right device in armbian (5.34) is /dev/ttymxc0 since it echoes characters when I join tx/rx together. When I connect the GPS it starts sending gps data normally, but when I have to reboot the hummingboard, it does not boot. I connected a screen to the HDMI interface to see what was happening, and I get the screen message as if a key had been pressed in order to stop booting process, so the boot stops here and the hummingboard does not come up. When I disconnect the GPS power or the UART, the HB boots normally, and the gpsd gets the serial port. when the gpsd is closed, agetty takes the control of the uart and I cannot use it again until I reboot. I concluded that the boot was configured to take the console keyboard from the UART, so I modified /boot/boot.cmd as suggested in this thread; I found the line: if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=ttymxc0,115200"; fi So I changed to if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi in order to avoid the boot to grab the ttymxc0 serial port. I recompiled the boot.cmd and rebooted, but the problem persists. The boot is still stopped due to an abnormal keypress. I have no idea of how to make it work, since I have tried the procedure above and also explored the alternative of resetting via hardware the GPS during hummingboard boot, but it still stops the booting. The GPS will be permanently connected to the hummingboard, so I cannot disconnect it everytime I reboot. Do you have any ideas about what would be the problem? How to avoid the boot to depend on the uart? I also checked the boot configuration built on the kernel: cat /boot/config-4.13.12-cubox |grep ttymxc and th result was: CONFIG_CMDLINE="noinitrd console=ttymxc0,115200" Does this mean that I have to recompile the kernel to solve it? Thanks very much in advance Regards

Hi I moved from 3.14 to 4.13. In 3.14 I had a imx framebuffer , needed for my lvds LCD In the 4.13 kernel menuconfig i cannot find a way to set CONFIG_FB_IMX. How to enable this? Dig

Hello everyone, I am a beginner in Linux. I have a Hummingboard i2ex and I am running Armbian_5.30_Cubox-i_Ubuntu_xenial_4.11.4_desktop on it. Trying to use a CSI Tool, I have to compile and install this kernel : https://github.com/xieyaxiongfly/Atheros-CSI-Tool.git Here are the steps that I did on the Hummingboard: ( you can see the tutorial: http://pdcc.ntu.edu.sg/wands/Atheros/document/Atheros-CSI-Tool-User-Guide.pdf ) 1) sudo apt-get install git (to clone the source) 2) sudo apt-get install libncurses5-dev libncursesw5-dev (to run makemenuconfig) 3) git clone https://github.com/xieyaxiongfly/Atheros-CSI-Tool.git 4) Enter the dir ~/Atheros-CSI-Tool/ 5) make menuconfig (use the default config provided by the kernel) 6) make 7) make modules 8) sudo make modules_install 9) sudo make install The compilation works fine and the make install command creates the following files in the /boot directory. ◾vmlinuz-4.1.10-fslc-imx6-sr+ ◾System.map-4.1.10-fslc-imx6-sr ◾initrd.img-4.1.10-fslc-imx6-sr ◾config--4.1.10-fslc-imx6-sr Then I copy the zImage Atheros-CSI-Tool/arch/arm/boot/zImage to the boot partition /boot. But when I reboot the hummingboard, I get no HDMI output and in the serial console I get the initialization and then Starting kernel ... Do you have any idea if the process is alright and how can I run this kernel on my Hummingboard. Thanks in advance, Fares

Hello, i have Hummingboard 1 with mainline kernel 4.11.6. And i have problem with GPIOs, after exporting GPIO 72 (also i try 73,71,1 / pin 11,13,7), set direction to OUT and value to 0 i have still 3.3V on pin 12 (11,13,7...). Also try 72 as OUT value 1 and 73 as IN ... and short this pins 11-12 by wire. gpiochip2: GPIOs 64-95, parent: platform/20a4000.gpio, 20a4000.gpio: gpio-68 ( |PCIe reset ) out hi gpio-69 ( |gpio-ir-recv ) in hi gpio-72 ( |sysfs ) out hi gpio-73 ( |sysfs ) in lo gpio-83 ( |brcm_reg ) out lo gpio-86 ( |usb_otg_vbus ) out lo 73 read as LOW. Also i try wiringX and test app "wiringx-read 1 0": running on a hummingboard Writing to GPIO 1: High Reading from GPIO 0: 0 Writing to GPIO 1: Low Reading from GPIO 0: 0 please help me :-) thanks.

Hi I have spent a lot of time with the Hummingboard2 Edge over the last months and i would like to share my experiences here. My Configurations is: Hummingboard 2 Edge with SSD Sata and MC7304 PCIE Lte Modem. Carrier Board is V1.2. Microsom is version 1.5. They are available since end of 2016. The difference is the WLAN and Bluetooth Module. Solidrun has changed it from Broadcom to TI Wlink 1831. First of all. If you have an unfused Microsom and you want to use the bootjumpers. (Only Carrier Board V1.2) Boot from SD: Set Jumper to SD (J5005 Pin 7 and 8) and (Connect J23 Pin 11 with J24 Pin 2 and with J21 Pin 5 Boot from MMC: Set Jumper to MMC (J5005 Pin 5 and 6) and (Connect J23 Pin 11 with J22 Pin 2) Carrier Board V1.4 is different. Then U-Boot from Solidrun is loading the dtb files as following. Microsom before V1.5 (imx6q-hummingboard2.dtb) and Microsom since V1.5 (imx6q-hummingboard2-som-v15.dtb) I have made the experience that the automatic board detection does not work a 100%. So set the fdt file manually: setenv fdt_file "imx6q-hummingboard2-som-v15.dtb" To create the imx6q-hummingboard2-som-v15.dtb file i have created a patch. See attached. If you would create the Image from source: apt-get -y install git git clone https://github.com/igorpecovnik/lib --depth 1 cp lib/compile.sh . Put the patch to userpatches/kernel/cubox-next/ ./compile.sh Choose Linux Next Kernel. If you would use an existing "next" image then you could put the attached dtb files to /boot/dtb. Working: HDMI, Audio, Wifi, Bluetooth, USB, Sata, Pcie Modem, Gpio's. I don't know if the IR Receiver is working. I don't need that. Note for bluetooth: There is a problem with the usage of dma on the imx6 platform. So i have disabled the usage in the dtb file. If there is a patch for the imx.c driver, it's possible to reenable it. The bluetooth device can be attached with "hciattach /dev/ttymxc3 texas 3000000 flow". It also needs new firmware files for the microsom v1.5. Put the attached firmware files to /lib/firmware/ti-connectivity TIInit_11.8.32 is for bluetooth. wl18xx-conf.bin and wl18xx-fw-4.bin are for wlan. If you would like to boot directly from sata device, then you could do the following. apt install mercurial hg clone https://kkubacki@bitbucket.org/kkubacki/u-boot-imx6 export ARCH=arm export CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- cd u-boot-imx6 make mx6cuboxi_defconfig make As result we get two files: SPL and u-boot.img. SPL file should be placed at address 0x00000400 at SATA device. Copy SPL to SATA device e.g. sda: dd if=SPL of=/dev/sda bs=512 seek=2 sync u-boot.img should be placed on first EXT4 partition on SATA device. kernel-cubox-next.patch Firmware.zip DTB.zip

Recently I took my old Hummingboard and to run Armbian on it. I chose the desktop-version for Hummingboard using mainline kernel (presently 4.11.6-cubox). Unfortunately Armbianmonitor shows high CPU -temperature. It gradualy builds up, starting from 50 degrees next to 70 degrees, eventualy approaching 85 degrees and then it shuts down. I use the passive heatsink that came with the board and no case. I use it for light desktop things like browsing the internet. Is there something I can do to prevent this, is there something in the kernel like throttling when the board reaches a certain temperature? Thanks again for a great OS, I think you are doing an outstanding job for all those different kinds of boards!

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)

Hello, I want to boot Hummingboard Edge with Armbian (Jessie - kernel 3.14.54) , but I'm experiencing problems during the booting procedure. Bootloader is searching for some files then it gives up. I have copied two files (imx6q-hummingboard2.dtb to imx6q-hummingboard.dtb) to /boot/dtb/ folder. It looks like it starts with the kernel, but it never loads completely. Below are the steps: U-Boot SPL 2013.10-rc4-sun7i (Oct 11 2015 - 20:45:45) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4-sun7i (Oct 11 2015 - 20:45:45) CPU: Freescale i.MX6Q rev1.5 at 792 MHz Reset cause: POR Board: MX6-HummingBoard2 DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 437 bytes read in 130 ms (2.9 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 40257 bytes read in 421 ms (92.8 KiB/s) 6015384 bytes read in 584 ms (9.8 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x5bc998 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800cd40 Starting kernel ... I would be happy, if you can give me some pointers on how to solve this problem. With Solidrun linux port it works normally. Thank you.

Hello Solidrun has updatet their microsoms to v1.5. MicroSOM rev 1.5 Wifi: 802.1 b/g/n - 2.4 / 5 Ghz, single or dual MIMO with Bluetooth V4.0 (TI Wilink 8 WL18xx) http://wiki.solid-run.com/lib/exe/fetch.php?media=imx6:microsom:docs:sr-usom-mx6-pcn-20160915.pdf This is from the solidrun website: Make sure that your kernel .config has the following enabled either as modules or statically part of the kernel, in order to build the TI WiLink8 WiFi drivers -CONFIG_WL18XX=yCONFIG_WLCORE=yCONFIG_WLCORE_SPI=yCONFIG_WLCORE_SDIO=yCONFIG_WILINK_PLATFORM_DATA=yCONFIG_WL_TI=y# CONFIG_WL1251 is not set# CONFIG_WL12XX is not setThe firmware is typically searched under under /lib/firmware/ti-connectivity/wl18xx-fw-4.bin directory in your root filesystem.The firmware is loaded when the interface is activated 'ifconfig wlan0 up' so there is no race between initializing the driver before the root filesystem is mounted. And then there are new dts files. I have attached them. They are from the solidrun kernel 3.14 git source. https://github.com/SolidRun/linux-fslc Is it possible, that you can adapt them and add these changes to one of the next armbian versions? I have tried it to do a patch, but when i launched the image with vanilla 4.10. I have got no HDMI output. Thanks in advice. Andreas Odermatt imx6qdl-cubox-i-som-v15.dtsi imx6qdl-hummingboard2-som-v15.dtsi imx6qdl-hummingboard-som-v15.dtsi imx6qdl-solidrun-microsom-v15.dtsi imx6dl-cubox-i-som-v15.dts imx6dl-hummingboard2-som-v15.dts imx6dl-hummingboard-som-v15.dts imx6q-cubox-i-som-v15.dts imx6q-hummingboard2-som-v15.dts imx6q-hummingboard-som-v15.dts

Hi, I have an issue on my hummingboard i2ex. I installed mpd and configured it with SPDIF. The kernel is 4.9.12-cubox. Unfortunately the sound looks strange. It sounds like a slow motion recording. The load is very load (<0.2) so I think it is not a performance problem. I saw there was an issue with the SPDIF previously but it is a little bit different. Do you have any idea what could be wrong? Is it possible to test it your side? Thanks, Warter

@Igor how come there isn't any mainline kernels available for these boards lack of time or lack of interest ? currently using xilka kernel but would love to have it in apt less messy would be awesome to include/combine those builds and get more support for imx6 since graphics is up to 3.14.60 and mainline is at 4.4.0 (minimal support for graphics kinda like your mainline packages).

Hello, I installed rpi-monitor via the debian micro home server script. It's nice, especially cpu load and ram usage but I don't get the right temperature of the cpu. Here's a screenshot. Any idea how I can fix that?

Hello, I have a problem with connecting to ILI9341 hummingboard postaebuje as described http://docs.armbian.com/Hardware_Freescale-imx6/ I do entry Add this to your / etc / modules: fbtft_device name = adafruit22a rotate speed = 90 = 48000000 fps = 50 GPIOs reset = 67, led 72, dc 195 busnum = 1 reboot but the display is lit only shows nothing What may be the problem wyśietlacz exactly http://allegro.pl/wyswietlacz-lcd-tft-2-4-240x320-spi-bte-141-i6258585811.html