Hi,
I'm trying to install xenomai-2.6.2.1 on the i.MX6Q Sabre Lite.
Using U-boot-mx6q-sabrelite.bin and the rootfs.ext2 from the L3.0.35_4.0.0_130424_images_MX6 directory.
The kernel used is rel_imx_3.0.15_12.03.00, and after patching it with xenomai-2.6.2.1 following these steps :
1- Applying xenomai-2.6.2.1/ksrc/arch/arm/patches/mxc/adeos-ipipe-3.0.36-arm-1.18-11-pre.patch
2- Applying xenomai-2.6.2.1/ksrc/arch/arm/patches/adeos-ipipe-3.0.36-arm-1.18-11.patch
3- Applying xenomai-2.6.2.1/ksrc/arch/arm/patches/mxc/adeos-ipipe-3.0.36-arm-1.18-11-post.patch
4- xenomai-2.6.2.1/scripts/prepare-kernel.sh --arch=arm --adeos=$xenomai_root/ksrc/arch/arm/patches/adeos-ipipe-3.0.36-arm-1.18-11.patch --linux=rel_imx_3.0.15_12.03.00
5- make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- O=$build_root/linux imx6_defconfig
6- make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- O=$build_root/linux bzImage modules
7- xenomai-2.6.2.1/configure CFLAGS="-march=armv7-a -mfpu=vfp3" FDFLAGS="-march=armv7-a -mfpu=vfp3" --build=i686-pc-linux-gnu --host=arm-none-linux-gnueabi
8- make DESTDIR=$staging_dir install
Then putting the build_root/linux/arch/arm/boot/uImage | System.map | modules.builtin | modules.order | Module.symvers ==> to /media/boot
But when booting the target the kernel doesn't start and have this display :
mmc1 is current device
MMC read: dev # 1, block # 2048, count 8192 ... 8192 blocks read: OK
## Booting kernel from Legacy Image at 10800000 ...
Image Name: Linux-$ (3.0.15_12.03.00)
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3813344 Bytes = 3.6 MB
Load Address: 10800000
Entry Point: 10800000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
"Stops here"
Any help or idea is welcome
Hi,
I want to install xenomai on the i.MX6Q Sabre Lite board, for this I followed differents strategies but still not able to have xenomai on the target.
1- linux-3.5.7 vs xenomai-2.6.2.1 vs ipipe-core-3.5.7-arm-3.patch :
Using the installation procedure for ARM from : www.xenomai.org/documentation/xenomai-2.6/html/README.INSTALL/
The problem with this strategy is that I hadn't a rootfs to boot the target, so I took a different strategy.
HOW CAN I HAVE A ROOTFS TO BOOT THE TARGET WITH THE COMPILED SOURCES ?
2- Using the L3.0.35_4.0.0_130424 Freescale Release I built LTIB and by the way a rootfs, an uImage and a u-boot.bin which work correctly on the target.
Once having the rootfs I wanted to build the kernel patching it with xenomai and using the previous rootfs (LTIB)
PATCHING FAILED
3- I tried to patch the linux-3.0.35 with : adeos-ipipe-3.0.36-arm-1.18-11-pre.patch | adeos-ipipe-3.0.36-arm-1.18-11.patch | adeos-ipipe-3.0.36-arm-1.18-11-post.patch
But I had so many rejects, that why I prefered to use the rel_imx_3.0.15_12.03.00 and it's advised in : xenomai-2.6.2.1/ksrc/arch/arm/patches/README
Doing the same procedure as for linux-3.5.7, I had an uImage that I loaded on the µ-SD with the rootfs and u-boot either with the generated files from LTIB or the L3.0.35_4.0.0_130424_images_MX6
THE KERNEL LAUNCH BUT DOESN'T START :
mmc1 is current device
MMC read: dev # 1, block # 2048, count 8192 ... 8192 blocks read: OK
## Booting kernel from Legacy Image at 10800000 ...
Image Name: Linux-$ (3.0.15_12.03.00)
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3813344 Bytes = 3.6 MB
Load Address: 10800000
Entry Point: 10800000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
"Stops here"
How can I have a rootfs that woks with a kernel patched with xenomai ? To boot the target ?
Waiting for your answers.
Best regards,
Younes