[Avila] Oops, flashed redboot

[Joel Lindsay]

I think that my partitions are already split up.  This is what they look 
like!

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0x50000000  0x50000000  0x00080000  0x00000000
zImage            0x50080000  0x01600000  0x00100000  0x01600000
ramdisk           0x50180000  0x50180000  0x00400000  0x00800000
persistant        0x50580000  0x50580000  0x00100000  0x00800000
FIS directory     0x507E0000  0x507E0000  0x0001F000  0x00000000
RedBoot config    0x507FF000  0x507FF000  0x00001000  0x00000000

Would I still need to fix redboot?  It seems that the source redboot I have 
on my CD is very different from whats shipped because I get all kinds of 
errors when I try to use it.  I don't even know.  It appears that something 
is still wrong as linux says this

Creating 6 MTD partitions on "IXP4XX-Flash.0":
0x00000000-0x00080000 : "RedBoot"
0x00080000-0x00180000 : "zImage"
0x00180000-0x00580000 : "ramdisk"
0x00580000-0x00680000 : "persistant"
0x007e0000-0x007ff000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block -- force 
read-only
0x007ff000-0x00800000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary --  
force read-only

So this leads me to believe they are still together even though they appear 
to be in different partitions? (This is different from old firmware)

Also, what exactly is the fconfig program?  Do I actually need to change 
something in fconfig to make this work, or is this only in case I want to in 
the future?

When I tried to compile my own redboot it didn't work well so I tried to 
flash to the original.  Using the boot disk method this took me about 8 
hours using the parallel JTAG programmer.  Is this normal?

Thanks,

Joel Lindsay, B.Eng
Project Engineer
Waveteq Communications
(250) 766-9229
----- Original Message ----- 
From: "David Acker" <dacker at roinet.com>
To: "'Avila'" <avila at lists.unixstudios.net>
Sent: Wednesday, December 20, 2006 8:33 AM
Subject: RE: [Avila] Oops, flashed redboot
Subject: [Avila] >> -----Original Message-----
>> From: Joel Lindsay [mailto:joel at waveteq.com]
>> Sent: Wednesday, December 20, 2006 2:22 AM
>> To: 'Avila'
>> Subject: [Avila] Oops, flashed redboot
>>
>> Hi,
>>
>> Please note I am using the 2347 Rev C 1 port board.
>>
>> I tried to flash redboot as I wanted to use netflash to
>> update my firmware from a cgi form.  It was all working great
>> except I was getting CRC errors when checking the FIS partitions.
>>
>> Reading the mailing list archives I learned that this was
>> because I needed to turn off the CRC checking in redboot.
>>
>
> Well, you can keep your crc checking if you do the following:
> Turn off readonly redboot partitions in the kernel config.
>
> Fix redboot to put the redboot and fis partition in separate flash blocks
> and size them properly.  This will make mtd happy and thus allow fconfig 
> to
> work.
> http://lists.unixstudios.net/avila/2006/11/635
>
> Use fconfig to update redboot configuration data.
> http://lists.unixstudios.net/avila/2006/11/629
>
> Use the attached fis program to update the checksums in your fis 
> directory.
> fis <mtd_device> <fis_name> <file>
> where mtd_device is the fis directory device, fis_name is the name of the
> partition you will be copying to, and file is the file that will be 
> copied.
> For example:
> fis /dev/mtdblock7 zImage /tmp/zImage
>
> The program is GPL as it uses redboot's crc code which is GPL.  Enjoy!
> -Ack
>

--------------------------------------------------------------------------------

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
> For additional commands, e-mail: avila-help at lists.unixstudios.net