Hello all !<br>I'm porting a former Control application from x86 (Linux+RTAI+Comedi) to PowerPC (Xenomai+Comedi for RTDM). I've choosed for my development the ELDK tool and a MPC8315ERDB platform. So I 've properly patched and build my kernel with the Xenomai support and I get some errors when running a latency test app. I've managed to spot the problem , that consists in an incompatibility between the shared libraries used on the target (ver 2.5) and the standard libraries used (and with which were compiled the kernel and the Xenomai addon) version 2.6, and so ld screams and a SegFault appears. Now I,ve creted an ext2.img rootfs with the rootfs.tar.gz from /eldk/ppc_6xx/images and I've added in the rootfs some libs and other useful stuff for Xenomai for elliminating the need for an NFS mount. <br>
My primary concern is now to write the new FS to a USB Flash Stick so that I can test if the latency tests works now when the libs are compatible (ver 2.6).<br>So resuming I want to now what are the corect steps to do this, because I've tried to write the generated ext2.img to my USB flash stick (formated as ext2) and added to the uBoot bootargs to the following :<br>
<br>setenv usbstick_args setenv bootargs root=/dev/sdb1 ro rootdelay=10 rootfstype=ext2 console=$consoledev,$baudrate;<br>setenv usbstick 'run usbstick_args;bootm fe500000 - fe700000'<br>setenv bootcmd run usbstick<br>
<br>As a result I get the following output :<br><br>Waiting 10sec before mounting root device...<br>scsi 2:0:0:0: Direct-Access SanDisk Cruzer Micro 0.1 PQ: 0 ANSI: 2<br>sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB)<br>
sd 2:0:0:0: [sdb] Write Protect is off<br>sd 2:0:0:0: [sdb] Assuming drive cache: write through<br>sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB)<br>sd 2:0:0:0: [sdb] Write Protect is off<br>sd 2:0:0:0: [sdb] Assuming drive cache: write through<br>
sdb: sdb1<br>sd 2:0:0:0: [sdb] Attached SCSI removable disk<br>sd 2:0:0:0: Attached scsi generic sg1 type 0<br>VFS: Mounted root (ext2 filesystem) readonly.<br>Freeing unused kernel memory: 156k init<br>Warning: unable to open an initial console.<br>
Failed to execute /bin/busybox. Attempting defaults...<br>Kernel panic - not syncing: No init found. Try passing init= option to kernel.<br>Rebooting in 180 seconds..<br><br>Shall I explicitly give the init ? What should be ... init=/sbin/init, init=/bin/busybox ????<br>
<br>Thanks in advance !!!<br><br>Best regards ,<br>Cristian<br>