Andreas Odermatt

Hummingboard2 Next Kernel Infos

Recommended Posts

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/
Choose Linux Next Kernel.


If you would use an existing "next" image then you could put the attached dtb files to /boot/dtb.


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  

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  
u-boot.img should be placed on first EXT4 partition on SATA device.




Share this post

Link to post
Share on other sites
This topic is now closed to further replies.