Anyone else attempt getting Yocto on the DM3730 Torpedo successfully? I am running into the same errors mentioned above where the clock speeds are showing up as zero and then:

[    0.000000] Clocking rate (Crystal/Core/MPU): 0.0/0/0 MHz

[    0.000000] Unable to handle kernel NULL pointer dereference at virtual address 00000008

I was wondering if the above people solved their issue or gave up?

 

Relevant:

http://xkcd.com/979/

Matulis,

I actually did find a solution to this problem, but I forgot to post back here.

These two patches were necessary to fix it:

https://github.com/gumstix/meta-gumstix/blob/dizzy/recipes-kernel/linux/linux-gumstix-3.2/0047-ARM-7668-1-fix-memset-related-crashes-caused-by-rece.patch

https://github.com/gumstix/meta-gumstix/blob/dizzy/recipes-kernel/linux/linux-gumstix-3.2/0048-ARM-7670-1-fix-the-memset-fix.patch

Thank you Shea! You are awesome!!

Definitely would have taken a while to figure that out!

 

I've updated my fork of the repo with the fix and sent a pull request to dtran11

Did anyone ever get the USB hubs working with Yocto?

I can't seem to get the isp1763 to load.

If anyone is still following this thread, Linux 4.2 will include preliminary device tree support for the Torpedo (and with some massaing, Torpedo + Wireless).

A a couple weeks, I will be posting some patches to the DTS and DTSI files if people want. We haven't tested Yocto with our board, but if/when Yocto supports Kernel 4.2, I would expect some of the basic functions to work.

These files won't have gone through our quality testing, but would make a nice starting point for people who want to use the latest kernel, but it won't be fully functional.

adam

it would be great, if kernel 4.2 get support for Torpedo! A matching meta layer would be perfect.

regards,
Sebastian