IPL block is bad on DiskOnChip 2000

IPL block is bad on DiskOnChip 2000

[Martin Chan]

Dear all,

I have successfully DFORMATted my MD2202-D64 today, and try to install a
jffs2 file system to it.
I created a root.jffs2 using mkfs.jffs2 and tried both "cp root.jffs2
/dev/mtd0" and "dd if=root.jffs2 of=/dev/mtdblock0", but I still can't
"mount -t jffs2 /dev/mtdblock0 /mnt". (Yes, I know I missed the "erase"
command after I check the HowTo again.)

When I want to start again with dformat, I get "/ERROR - IPL block is bad."

I searched from google and I found Tim has the same problem but seems
has no solution.

Does anyone know a solution to this?
/
Thanks,
Martin

Message posted by Tim:
http://lists.infradead.org/pipermail/linux-mtd/2003-August/008476.html
>/ >When I use the DOC5.1.4 DOS utilities' /
>/ >DFORMAT /WIN:DC00 /S:DOC514.EXB /FIRST /
>/ > /
>/ >ERRORS
/>/ >
/>/ >DiskOnChip 2000 found in 0xdc000. /
>/ >64M media, 16K unit
/>/ >Virgin card rebuilding unit map.
/>/ >Media has been scanned /
>/ >ERROR - IPL block is bad.
/>/ >Error formatting DiskOnChip.
/>/ >Status code is 119 (flUnknow status) received from /
>/ >flFormatPhysicalDrive. Format failed. /
>/ >
/>/ >What's the matter with it? /

Re: IPL block is bad on DiskOnChip 2000

[David Woodhouse]

On Tue, 2003-12-09 at 19:21 +0800, Martin Chan wrote:
> Dear all,
> 
> I have successfully DFORMATted my MD2202-D64 today, and try to install a
> jffs2 file system to it.

Assuming you have no bad blocks on your DiskOnChip, you need to erase it
with 'eraseall' first.

Really, you shouldn't be doing this before we properly sort out the bad
block management on these devices.

-- 
dwmw2

Re: IPL block is bad on DiskOnChip 2000

[Martin Chan]

Great! It works. Thanks David.

Martin

David Woodhouse wrote:

>On Tue, 2003-12-09 at 19:21 +0800, Martin Chan wrote:
>  
>
>>Dear all,
>>
>>I have successfully DFORMATted my MD2202-D64 today, and try to install a
>>jffs2 file system to it.
>>    
>>
>
>Assuming you have no bad blocks on your DiskOnChip, you need to erase it
>with 'eraseall' first.
>
>Really, you shouldn't be doing this before we properly sort out the bad
>block management on these devices.
>
>  
>