[ts-7000] Re: Still Stuck in Redboot (TS7260)

["Christian" <>]

I sent you a PDF file to your yahoo mail, because I was on gmail, but, this is how I deal with it:

Lets Assume we have an ftp server on our computer and the kernel image inside the ftp folder.

1. First step is getting into the RedBoot, pressing ctrl + c once you plugged your SBC, till console shows you that you are on RedBoot command line. Inside, lets erase the old kernel, like this:

RedBoot> fis delete vmlinux

Delete image 'vmlinux' - continue (y/n)? y

So, we answer yes (y) to deleting question.

2. Now we are going to load a kernel into the RAM.

load -r -b 0x00218000 -h <ftpserver_IPaddress> <kernel_image_name>

In my case, ftpserver_IPaddress=192.168.10.99 and <kernel_image_name>=zImage, so the result of loading the kernel must be like this:

RedBoot> load -r -b 0x00218000 -h 192.168.10.99 zImage                          

Using default protocol (TFTP)                                                   

Raw file loaded 0x00218000-0x0037e6fb, assumed entry at 0x00218000

We see the that the base space in memory is 0x00218000 and the top, used for my zImage, is 0x0037e6fb, remember, this is hex, soon, we will need the kernel image length, so we have 2 ways to know this number.

Mode A:

((Top space in memory) - (Base space in memory)) + 1 = (kernel length)

my case is ((37e6fb) - (218000)) + 1 = (0x001666fc)

Always in Hexa use 0x001666fc notation, or use 1468156 means decimal as it is, and don't forget adding the 1, because we are talking about memory space indexed from zero.

Mode B:

ls -l /tftpboot/zImage

-rwxr-xr-x 1 myname myname 1468156 2011-01-06 14:10 /tftpboot/zImage

Using the command ls -l, take the size data and change it to Hexa. Both methods return the same result, obviously :-) . Which is 0x001666fc or 1468156.

3. In this step we write the kernel to flash.

fis create -b 0x00218000 -l <length> vmlinux

Remember, in my case length=0x001666fc, watch out the way you write it, you have these two examples:

fis create -b 0x00218000 -l 0x001666fc vmlinux

"or"

fis create -b 0x00218000 -l 1468156 vmlinux

NOTE! I had an space problem inside the flash, I have no idea about what was wrong but, no matter what I did, always said:

Can't locate xxxxxxxx(xxxxxxxx) bytes free in FLASH

Where X's are for sizes conflict, so, being sure about having enough space, and a working kernel I fixed this problem like this:

RedBoot> fis init -f
About to initialize [format] flash image system - continue (y/n)? y

Don't forget "-f" because this way, initializes the FIS directory and all of flash memory, except for first blocks of the flash where the boot monitor resides.

From here, everything should work fine.

4. Once we have finished the last steps successfully, lets load our kernel from the onboard flash.

RedBoot> fis load vmlinux

RedBoot> exec

The result should be, linux starting, note that I only use exec, because my kernel has the rest of this instruction compiled inside, look this tutorial to know about my kernel compilation.

NOTE! if you have the automatic script for redboot, the kernel is atomatically loaded and linux should start without problems, if you don't, remember apply the fconfig in RedBoot,  insert the two commands, in step number 4, make the update of this script and finally restart your SBC. The result is, linux running automatically with your new kernel.

__._,_.___

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe

__,_._,___