Hi, I posted this on qnx.qnx4 as well, but I was wondering if anyone here
could help:
Well, it’s happened. The entire family of boot block flash parts we’re using
on a 386ex-based board are end-of-life. Normally, that would mean phasing
out of the product, but folks at my company are apparently not normal.
(((((((sigh)))))))
Anyway, we’re trying to modify the 4.2.2 Ekit to support erasing/writing the
AMD 29F400BT device in the EFsys.386ex driver. We have a new module written,
based loosely on the i28F400T.c module. I can verify that the driver
contains the new module by examining the Efsys.386ex.map file. Great. PROM
burned the new OS/app image onto the 29F400 part and it boots. Great, again.
Now, when we attempt to erase the flash in the embedded application the
reply to the _FFS_FORMAT command (reply.status) is 0x2c5 (709 decimal).
Now, try as I might, I can’t find any documentation to explain to me what
this means, other than the command was not successful. Can someone point me
to a list of ffs error codes?
Also, and this is a long shot, does an MTD driver already exist for the
29F400BT?
Hi Casey,
The 0x2c5 appears to be the _FFS_FORMAT command itself, so I’m not sure
what it means that you are getting that back as a status…
I took a look at the QNX 4.25 version EKit code (which is the only EKit
source that I can locate currently), and it appears that there is an MTD
for the AM29F400T flash device. I’m not sure how we distribute older source
such as the EKit, but if you put in a request through your sales rep, you
should be able to get an archive of the EKit, and use that MTD as the basis
for your modifications.
Dave
casey-ballentine <casey-ballentine@cox.net> wrote:
Hi, I posted this on qnx.qnx4 as well, but I was wondering if anyone here
could help:
Well, it’s happened. The entire family of boot block flash parts we’re using
on a 386ex-based board are end-of-life. Normally, that would mean phasing
out of the product, but folks at my company are apparently not normal.
(((((((sigh)))))))
Anyway, we’re trying to modify the 4.2.2 Ekit to support erasing/writing the
AMD 29F400BT device in the EFsys.386ex driver. We have a new module written,
based loosely on the i28F400T.c module. I can verify that the driver
contains the new module by examining the Efsys.386ex.map file. Great. PROM
burned the new OS/app image onto the 29F400 part and it boots. Great, again.
Now, when we attempt to erase the flash in the embedded application the
reply to the _FFS_FORMAT command (reply.status) is 0x2c5 (709 decimal).
Now, try as I might, I can’t find any documentation to explain to me what
this means, other than the command was not successful. Can someone point me
to a list of ffs error codes?
Also, and this is a long shot, does an MTD driver already exist for the
29F400BT?
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
Thanks Dave!
I believe we have the 4.25 EKit as well, so I’ll take a look at it.
“Dave Green” <dgreen@qnx.com> wrote in message
news:e34vjr$hs2$1@inn.qnx.com…
Hi Casey,
The 0x2c5 appears to be the _FFS_FORMAT command itself, so I’m not sure
what it means that you are getting that back as a status…
I took a look at the QNX 4.25 version EKit code (which is the only EKit
source that I can locate currently), and it appears that there is an MTD
for the AM29F400T flash device. I’m not sure how we distribute older
source
such as the EKit, but if you put in a request through your sales rep, you
should be able to get an archive of the EKit, and use that MTD as the
basis
for your modifications.
Dave
casey-ballentine <> casey-ballentine@cox.net> > wrote:
Hi, I posted this on qnx.qnx4 as well, but I was wondering if anyone here
could help:
Well, it’s happened. The entire family of boot block flash parts we’re
using
on a 386ex-based board are end-of-life. Normally, that would mean phasing
out of the product, but folks at my company are apparently not normal.
(((((((sigh)))))))
Anyway, we’re trying to modify the 4.2.2 Ekit to support erasing/writing
the
AMD 29F400BT device in the EFsys.386ex driver. We have a new module
written,
based loosely on the i28F400T.c module. I can verify that the driver
contains the new module by examining the Efsys.386ex.map file. Great.
PROM
burned the new OS/app image onto the 29F400 part and it boots. Great,
again.
Now, when we attempt to erase the flash in the embedded application the
reply to the _FFS_FORMAT command (reply.status) is 0x2c5 (709 decimal).
Now, try as I might, I can’t find any documentation to explain to me what
this means, other than the command was not successful. Can someone point
me
to a list of ffs error codes?
Also, and this is a long shot, does an MTD driver already exist for the
29F400BT?
\
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com