ts-7000
[Top] [All Lists]

Re: [ts-7000] Bad blocks on redboot partition

To: <>
Subject: Re: [ts-7000] Bad blocks on redboot partition
From: "Michael Schmidt" <>
Date: Mon, 18 Dec 2006 10:07:29 -0700
> Hi,
>

Hello,

>> We added support for handling bad blocks to RedBoot a while back. If you
>> look in ftp://ftp.embeddedarm.com/images/redboot
> <ftp://ftp.embeddedarm.com/images/redboot> you should find the redboot
>> image you need. If you have an older board with 512 byte blocks you will
>> want to look for something like "ts7250-128-kernel-ts11" while if you
> have a
>> newer 2k byte block size you will want a filename containing "nand2k"
>> (though in this case you should have a new enough version to not need to
>> download it...
>
> I have a TS-7250 with 2 bad blocks in the redboot partition. When I try
> to write the kernel image ("fis create" command) it fails, because there
> are some bad blocks. It seems that my redboot isn't able to skip bad
> blocks, even if you say that it should.
>

Does it give you an error message, or does it silently fail?  If you could 
provide the error message that might help.


> Can you give more information, please?
> How can I skip bad blocks?
>
>
> ---
> RedBoot> fis list
> Name              FLASH addr  Mem addr    Length      Entry point
> (reserved)        0x60000000  0x60000000  0x01D04000  0x00000000
> RedBoot           0x61D04000  0x61D04000  0x00040000  0x00000000
> vmlinux           0x61D44000  0x00218000  0x00128000  0x00218000
> (bad block)       0x61E44000  0x61E44000  0x00004000  0xFFFFFFFF
> (bad block)       0x61F80000  0x61F80000  0x00004000  0xFFFFFFFF
> FIS directory     0x61FFC000  0x61FFC000  0x00003000  0x00000000
> RedBoot config    0x61FFF000  0x61FFF000  0x00001000  0x00000000
> ---

It looks like you've got the version of RedBoot which skips bad blocks (512 
byte sector size).  The "(bad block)" entries in the fis list are special 
entries which keep track of where bad blocks are.  In the above case, it 
looks like you have one bad block in the vmlinux area:
    0x61D44000 + 0x128000 = 0x61E6C00
...and also another bad block outside of the vmlinux file.  The setup you 
have should work - when RedBoot tries to read vmlinux it will see the bad 
block and skip around it.


>
> ---
> RedBoot> version
>
> RedBoot(tm) bootstrap and debug environment [ROMRAM]
> Non-certified release, version current-TS_5 - built 10:49:48, Jun 19 2006
> ---
>
> Thanks,
> Marco Pracucci

Regards,

Michael



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU