RE: Un protecting flash error

[KRISHNAN SUDHAKAR-N. <sud...@mo...>]

Hi Stuart,

Thanks for the reply.
Find the attached logs which has the board boot sequence from U-Boot.
Further please see my comments below.
I am entirely new to these things so I am taking more time to reply.

Thanks
Sudhakar 

-----Original Message-----
From: Stuart MENEFY [mailto:stu...@st...] 
Sent: Tuesday, February 26, 2008 9:55 PM
To: KRISHNAN SUDHAKAR-NRD743
Cc: lin...@li...
Subject: Re: Un protecting flash error

Hi Sudhakar

KRISHNAN SUDHAKAR-NRD743 wrote:
> This is the first time I am trying to write in this board.
 >
> But unprotect and write is possible in uboot prompt.

Do you mean this is the first time you have tried to use Flash when
running the kernel, but it works OK from U-Boot?
<sudhakar>Yes this is the first time we are tring from kernel. But it
works fine in U-Boot prompt

So is it possible somebody has added code to U-Boot to enable VPP, but
that same modification hasn't been made to the kernel?
<sudhakar> yes we got U-Boot from other persons only exattly I don't
know how to find out in kernel side.

> In the same board flash info is working.
<sudhakar>Yes info is working in both Uboot ans linux

Do you mean the U-Boot flinfo command?
<sudhakar> No flash_info command in Linux terminal

It might be worth building the kernel with MTD debug to set level 3, see
if that tell us anything useful.
<sudhakar> I will try and let you know.

Are you booting the kernel from a micro connect or from U-Boot?
<sduhakar> I am booting kernel from U-boot

Can you try both, and see if it makes a difference.
<sudhakar> I doing now from ST micro connect

Is this your own board, or a reference board?
<sudhakar>Its our own board not reference board

Which Flash device are you using, and which kernel?
<sudhakar> We are using Spansion flash 32MB and kernel is
Linux-2.6.17.14

Stuart

> 
> Thanks
> -----Original Message-----
> From: Stuart MENEFY [mailto:stu...@st...]
> Sent: Tuesday, February 26, 2008 8:02 PM
> To: KRISHNAN SUDHAKAR-NRD743
> Cc: lin...@li...
> Subject: Re: Un protecting flash error
> 
> Hi Sudhakar
> 
> KRISHNAN SUDHAKAR-NRD743 wrote:
>> I am facing few flash file accessing problems ST Linux based systems.
>> I have modified the code in stboards.c file for creating partitions
> ...
>> Partition looks like the following
>>
>> /tmp # cat /proc/mtd 
>> dev:    size   erasesize  name
>> mtd0: 00500000 00020000 "VIP800 Boot"
>> mtd1: 00100000 00020000 "FFS0"
>> mtd2: 01a00000 00020000 "FFS1"
>>  
>> if I do a flash info its working fine
>>  
>> / # flash_info /dev/mtd2
>> Device /dev/mtd2 has 0 erase regions
>>
>> if i try to unlock the partion its not happeniing
>>  
>> / # flash_unlock /dev/mtd2
>> Could not unlock MTD device: /dev/mtd2 / #
>>  
>> It will be very helpful if some one give some solutions
> 
> The implication is that changing the partition table has broken this, 
> is this correct or has it never worked?
> 
> If its never worked I'd be suspicious that your board has a write 
> protect signal, VPP enable or something similar which you need to 
> enable.
> 
> Stuart
> 
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by: Microsoft Defy all challenges. 
> Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> linuxsh-dev mailing list
> lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsh-dev