Wandboard new kernel

[pepedog]

It now works on cubox i4pro.
Did you build the package with all the bits? And edit the conf.d file? Crawx says this works, please report here
https://github.com/CrawX/PKGBUILDs/issues

Edit
I see there is a line in the start script, enumerating which firmware, you might want to find out if wandboard uses the same
a=`cat /sys/class/mmc_host/mmc0/mmc0\:0001/mmc0\:0001\:1/device`

[h0tw1r3]

I have already modified the firmware-brcm43xx PKGBUILD to correctly load the bcm4329.hcd firmware and use the correct tty.
The modified firmware-brcm43xx package is working correctly with linux-wandboard 3.0.35-7 and uboot-wandboard-quad-2014.01-1.

With the only change of upgrading linux-wandboard to 3.10.17-2 and uboot-wandboard-quad to 2014.04-1, bluetooth firmware no longer loads.

$this->bbcode_second_pass_code('', '
[root@wandboard ~]# systemctl start brcm43xx
[root@wandboard ~]# journalctl -r |head -20
-- Logs begin at Wed 1969-12-31 18:00:03 CST, end at Fri 2014-05-23 15:47:40 CDT. --
May 23 15:47:40 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:40 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:36 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:36 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:32 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:32 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:31 wandboard systemd[1]: Started Load Broadcom bluetooth firmware.
May 23 15:47:28 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:28 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:24 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:24 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:20 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:20 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:16 wandboard start-brcm-patchram-plus[467]: 01 03 0c 00
May 23 15:47:16 wandboard start-brcm-patchram-plus[467]: writing
May 23 15:47:16 wandboard start-brcm-patchram-plus[467]: Found chip version 0x4329.
May 23 15:47:16 wandboard systemd[1]: Starting Load Broadcom bluetooth firmware...
May 23 15:36:48 wandboard systemd[1]: Started User Manager for UID 0.
May 23 15:36:48 wandboard systemd[443]: Startup finished in 166ms.
')

[h0tw1r3]

$this->bbcode_second_pass_quote('pepedog', 'I')t now works on cubox i4pro.
Did you build the package with all the bits? And edit the conf.d file? Crawx says this works, please report here

[hansan]

Dear all,

I have the same problem as andrenam mentions on his post of Monday 19 May. The system does not perform a soft reboot.
Power cycling makes the system start correctly. But after the "reboot" or "shutdown -r now" command is the process hanging after the messages "Starting Kernel ..."

I think I have the latest version of uboot and the roofs:
$this->bbcode_second_pass_code('', 'md5sum -b ArchLinuxARM-wand-latest.tar.gz
89f603bf66347c75120c82b99658c048 *ArchLinuxARM-wand-latest.tar.gz
uname -a
Linux wandboard 3.10.17-3-ARCH #1 SMP Tue Jul 15 20:38:48 MDT 2014 armv7l GNU/Linux')

Have others this problem as well? And is there a solution to this reboot problem?
I am quite lost because I have not much experience with Arch linux. Having to power-cycle is a bit of a show stopper for my embedded project. So I am very willing to invest time to solve this, just let me know what I should check / do.

[kamalraghav81]

Any error related to

** File not found /boot/undefined **

indicates that this file has been mentioned in the uEnv.txt in /media/boot partition of the SD card.

This file is required in the file system partition in the /media/rootfs and in the folder "boot" inside this partition on the SD card.
It might revert to older/default images/binaries in case it does not find them on rootfs partition. As it looks to be the case for your setup.

This is relevant to any file error you get on the u-boot console. Solution is to copy the file mentioned in error to the respective location.

Else the error could be in the mapping of SD card partition address specified in the loadaddr in uEnv.txt for /media/boot partition. This is rare as the settings are inside closed git repository, unless tweaked.

Note: There is another uEnv.txt file present in the /boot directory of the /media/rootfs partition. Which is quite confusing.