Gary,
> How are you guys programming yaffs images into the flash? Copying from an
> NFS mount or SD card?
Copying a tarball to the Yaffs mount point via an NFS root filesystem.
> On Wed, Aug 19, 2009 at 11:15 AM, dawydiuk <> wrote:
>
>> Hi Gary,
>>
>>> It's been a long time since we had this issue so I'm a bit fuzzy on the
>>> details. I do know that we used the "mkyaffs" utility to program the
>> flash
>>> on the target using an image prepared by the "mkyaffsimage" on the host.
>> Interesting we've never used the mkyaffs utility to program the nand flash.
>> Hopefully J. Chitte can comment if he also uses the mkyaffs utility...
>>
>> Regards,
>> Eddie
>>
>>> On Wed, Aug 19, 2009 at 10:54 AM, Eddie Dawydiuk <>wrote:
>>>
>>>> Hello,
>>>>
>>>>> I'm not sure what you want me to provide. The board will still boot
>> but I
>>>> only have console and it keeps spewing "yaffs tragedy" to that.
>>>>
>>>> Basically what I'm asking for is, if you can tell me how to reproduce
>> the
>>>> problems you are reporting. That is if I take a stock board, what needs
>> to
>>>> be
>>>> done to make large amounts of blocks to be marked bad as you've
>> reported.
>>>> As I
>>>> mentioned earlier the kernel hasn't changed in several years, and we've
>>>> done
>>>> quite a bit of testing on the Yaffs code base we are shipping and we
>> have
>>>> been
>>>> unable to reproduce any failures. If our tests are missing a problem,
>> we
>>>> would
>>>> be interested to know what needs to be done to cause the problem to
>> show
>>>> up.
>>>>
>>>> If you'd like you can contact me off list and I will provide you with
>> an
>>>> RMA so
>>>> your board can be returned to be restored to the factory default
>> settings
>>>> with a
>>>> new Nand flash chip.
>>>>
>>>>> Since I don't really understand what conditions produce the bad block
>>>> markage I can only guess like you. I can't provide do steps 1,2,3
>>>> > "happens every time" bug report. Sorry.
>>>>
>>>> I'll pass your report along to my manager, although I can tell you from
>>>> past
>>>> experience he will be much more likely to assign an engineer to look
>> into
>>>> your
>>>> bug report if you can provide information on how to recreate the bug
>> you
>>>> are
>>>> reporting.
>>>>
>>>> A few more questions. How many boards have seen this problem on? Have
>> you
>>>> seen
>>>> this problem on any boards that have never run a non TS kernel(I
>> believe
>>>> you
>>>> mentioned running a 2.6 kernel at one point)?
>>>>
>>>> --
>>>> Best Regards,
>>>> ________________________________________________________________
>>>> Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
>>>> 16525 East Laser Drive | fax: (480) 837-5300
>>>> Fountain Hills, AZ 85268 | web: www.embeddedARM.com
>>>>
>>>>
>>>> ------------------------------------
>>>>
>>>> Yahoo! Groups Links
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
--
Best Regards,
________________________________________________________________
Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
16525 East Laser Drive | fax: (480) 837-5300
Fountain Hills, AZ 85268 | web: www.embeddedARM.com
------------------------------------
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/
|