Varka Bhadram <varkabhadram@xxxxxxxxx> wrote:
> You can directly use linux-wpan-next tree directly, which has the basic
> support for RPI. No need to rebase it on rpi kernel.
> Please see the blog: https://honk.sigxcpu.org/piki/hw/rpi6lowpan/
I finally got back to working on this.
Some minor edits:
you copy the kernel to the name rpi.img:
scp bluetooth-next/arch/arm/boot/zImage ${TFTP_IP}:/tftpboot/rpi.img
but you tell the system to load zImage:
dhcp ${kernel_addr_r} zImage
According to the manual, I can take my image from a different machine than
the dhcp server:
U-Boot> dhcp ${kernel_addr_r} 172.30.2.231:zImage
U-Boot> tftp ${fdt_addr_r} 172.30.2.231:${fdtfile}
U-Boot> bootz ${kernel_addr_r} - ${fdt_addr_r}
Bad Linux ARM zImage magic!
I'm still debugging what's going on...
I think the dhcp did not work correctly, as a md of the ${kernel_addr_r}
does not match a hexdump of the zImage that I built.
%file arch/arm/boot/zImage
arch/arm/boot/zImage: Linux kernel ARM boot executable zImage (little-endian)
{BTW: I will be bringing this code base to the ETSI 6lo plugfest in Yokohama
in November}
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
