Linux.com

Hi world, I'm starting to develop an embeded project based on an ICOP small board : the VSX-6154 ... -> The board : http://www.icop.com.tw/products_detail.asp?ProductID=275 On this board, I've install the Linux (v5.51) provided by ICOP, this is OK, I've got my shel command line. -> Some details about this Linux : http://www.dmp.com.tw/tech/os-xlinux/ [quote][b]Linux Kernel 2.6.23[/b] /boot/linux [b]Loader SysLinux 2.13[/b] /boot [b]Shell BusyBox 1.10.4[/b] /bin/busybox [b]FTP Server vsftpd 2.0.3[/b] /usr/sbin/ftpd [b]TELNET Server BusyBox 1.10.4[/b] /usr/sbin/telnetd [b]HTTP Server WN Server 2.4.6[/b] /usr/httpd [b]DHCP Client BusyBox 1.01[/b] /sbin/udhcpc [b]Share Library glibc 2.7[/b] /lib [b]PPP Daemon pppd 2.4.1[/b] /sbin [b]NFS NFS-Utils 1.0.6[/b] /sbin[/quote] I actually use this on a PC's CRT screen on VGA output. For my project, I will need to draw some birmaps on screen, so I will probably use framebuffer, or a small lib like Nano-X, if framebuffer is too borring... So, I've found this small piece of C code on the www : [quote]#include <unistd.h> #include <stdio.h> #include <fcntl.h> #include <linux/fb.h> #include <sys/mman.h> #include <sys/ioctl.h> #include <errno.h> int main(int argc, char *argv[]) { int fbfd = 0; struct fb_var_screeninfo vinfo; struct fb_fix_screeninfo finfo; long int screensize = 0; char *fbp = 0; int x = 0, y = 0; long int location = 0; // Open the file for reading and writing fbfd = open("/dev/fb0", O_RDWR); if (fbfd<0) { printf("Error: cannot open framebuffer device.\nreturn=%d\n",fbfd); return(1); } printf("The framebuffer device was opened successfully.\n"); // Get fixed screen information if (ioctl(fbfd, FBIOGET_FSCREENINFO, &finfo)) { printf("Error reading fixed information.\nerrno=%d\n",errno); return(2); } // Get variable screen information if (ioctl(fbfd, FBIOGET_VSCREENINFO, &vinfo)) { printf("Error reading variable information.\n"); return(3); } printf("%dx%d, %dbpp\n", vinfo.xres, vinfo.yres, vinfo.bits_per_pixel); // Figure out the size of the screen in bytes screensize = vinfo.xres * vinfo.yres * vinfo.bits_per_pixel / 8; // Map the device to memory fbp = (char *)mmap(0, screensize, PROT_READ | PROT_WRITE, MAP_SHARED, fbfd, 0); if ((int)fbp == -1) { printf("Error: failed to map framebuffer device to memory.\n"); return(4); } printf("The framebuffer device was mapped to memory successfully.\n"); x = 100; y = 100; // Where we are going to put the pixel // Figure out where in memory to put the pixel for (y = 100; y < 300; y++) for (x = 100; x < 300; x++) { location = (x+vinfo.xoffset) * (vinfo.bits_per_pixel/8) + (y+vinfo.yoffset) * finfo.line_length; if (vinfo.bits_per_pixel == 32) { *(fbp + location) = 100; // Some blue *(fbp + location + 1) = 15+(x-100)/2; // A little green *(fbp + location + 2) = 200-(y-100)/5; // A lot of red *(fbp + location + 3) = 0; // No transparency } else { //assume 16bpp int b = 10; int g = (x-100)/6; // A little green int r = 31-(y-100)/16; // A lot of red unsigned short int t = r<<11 | g << 5 | b; *((unsigned short int*)(fbp + location)) = t; } } munmap(fbp, screensize); close(fbfd); return(0); } [/quote] ( sorry for "quoting" code, but code display strange results... ) I've build it with Code::Block on my Kubuntu station ( I'm new to dev on Linux ! ... I'm a pro-dev on Windows classicaly ) ... and it does'nt work on my station ... Got this : [quote]Error: cannot open framebuffer device. return=-1[/quote] So, the [i]open("/dev/fb0", O_RDWR)[/i] fails ... ( same result when calling by sudo ) first : Is that normal on Kunbuntu ? Now, I want to test this on my embeded board, but when I call ldd to know dependecies, I don't know where to found that files ( to put them in /lib/ of target system ) ... there is no "simple way" for Code::Block to serach them for me, and put them in my project ( in lib directory for exemple ) Thanks for help, and a merry chrismas to you ! *<Bo) Seb.

I don't know ... I've done the linux install by restoring a GHOST image directly to the HDD, so I don't know what is installed and what isn't ... -> how could I know if it's done or not ? thanks for your reply ;o) [Modified by: Seb.26 on December 30, 2008 11:19 PM]

Arrgghhh ... it's not easy to build a standard kernel on Kunbuntu !!! Does anybody have a tutorial for this special need ??? Thanks

[quote=tophandcwby]http://beginlinux.wordpress.com/2008/12/03/how-to-compile-an-ubuntu-810-kernel/[/quote] Hi tophandcwby, thanks a lot for the link ... But this is for building an Ubuntu Kenel, no ? I'm probably wrong, but I have the feel that ubuntu use a special kernel ... ( Am I wrong ? ) ... And, I need to build a classic kernel for embeded target from ICOP ... ?! Or maybe could I just follow this steps and replace the .config by mine ? All of that is pretty confused in my mind ... sorry ... [Modified by: Seb.26 on January 02, 2009 12:05 AM]

OK, so I've restart from scratch : 1) I've downloading latests stable full sources from www.kernel.org ( linux-2.6.28.tar.bz2 ) 2) I've put the file in a local directory ( /home/dev/kernel/ ) 3) I've unpack files : bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf - 4) I've done a "make mrproper" to clean all ( in the case of ??? ) 5) I've put my .config file ( provided by ICOP ) in root of source files 6) I've done a "make oldconfig" to set all new setup ( by the default value each time ) 7) I've done a "make" to build all ... this take some times ( with some warnings about ) 8) I've take the original "linux" file (1.8MB) in /boot/ , rename it as "linux.old" 9) I've copy in place the "bzimage" (1.3MB) and rename it as "linux" Then, I've boot my board with new kernel ... it's start, but hangup ... last lines are : [quote]TCP cubic registered NET: Regstered protocol familly 17 Using IPI Shortcut mode VFS: Cannot open root device "hda2" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions : Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)[/quote] Hum ... sincerly : I don't understand anything exept that's is like my seond partition (hda2) is bad/locked ?! ... I will try to restore the "linux.old" as "linux" to see what happen ... If you have an idea ... thanks ... ;o) [Modified by: Seb.26 on January 02, 2009 07:53 PM]

[quote=tophandcwby]Steps 4 and 5 are reversed. Do make mrproper before you copy your old .config file. mrproper deletes the .config.[/quote] Yes, sorry ... in reality, I've done them in the right order ... (I will edit my post) [quote=tophandcwby]Is the system expecting a initrd file?[/quote] I don't know ... how could I know ? Note : my loader is SysLinux 2.13

my boot partition ( hda1 in MS DOS type ) contains 4 files : << LDLINUX.SYS (7KB) linux (1700KB) SYSLINUX.CFG (1KB) SYSLINUX.COM (20KB) >> And the SYSLINUX.CFG file contain this text : << DEFAULT linux LABEL linux KERNEL linux APPEND root=/dev/hda2 >> no "initrd" in it ... but you are probably near the problem : my root partition is not compliant with my kernel build ... IMO, there are 2 ways : 1 > it's due to the hda2 partition type : Linux, ID = 83 ... but since I cannot found information about that in changelog, I don't think ... 2 > something in the partition data is bad for the new kernel, so I have to check what the kernel look for in the root filesystem ... Any idea/sugestion ? ... to be continued ... In any case : a big thanks to you tophandcwby for your help from the start of this post ( and also for your patience ! ... I know how it's hard to help newbies ... ) [Modified by: Seb.26 on January 03, 2009 06:07 PM] [Modified by: Seb.26 on January 03, 2009 06:36 PM]

Hi world ... Great news : my kernel is working ... bad news : I don't know if framebuffer is OK ! Borring with that strange problem, I've just take previous kernel sources (2.6.24.7) and build them with same .config, and all is OK at the first time ... And since I probably won't need new features like ext4 & co ... it's enought for the moment ... So that's cool ! But now, I'm back with my first problem : using framebuffer !!! my .config include vesa drivers, the fb console is activated, but I cannot see Tux on boot ( I think this is the first think visible when framebuffer is corectly set ) In my syslinux:cfg, I've add "vga=ask", but this only offer me some 80x25 / 80x50 ...etc... setup, no one looks like graphic : 800x600 @ 24bpp ... Any idea ??? Thanks