|
Dave Bott(deleted)
|
FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
08/13/2009 5:08 PM
post35961
|
FAT32 filesystem on NAND ?
6.4.1 ARMLE
Customer wants to use a FAT filesystem on their NAND chips (on an Atmel ARM board), so that they can plug into a PC as a
USB device for uploads to the PC directly from the filesystem.
They want the FAT filesystem to support ECC and, ideally wear-levelling.
I have explained that it is not power safe and they're fine with that.
I don't think fs-dos can run on NAND, but is that true ?
They also want to boot from the NAND:
"
We have a requirement to boot from the NAND.
From the Atmel datasheet:
"The first block must be guaranteed by the manufacturer. There is no ECC check.
The NVM bootloader program (this is the ROM code running on power up) looks for a boot.bin file in the root
directory of a FAT12/16/32 formatted NVM Flash."
"
I'm guessing we could support this, in theory, by leaving the boot area free, and only running a QNX partition./
filesystem on part of the NAND. So, if there's already a filesystem on the first N blocks of the NAND, we can ignore it
and just run on the rest - is that reasonable ?
Thanks
Dave
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
08/14/2009 10:26 AM
post36011
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: August 13, 2009 5:08 PM
> To: general-filesystems
> Subject: FAT32 filesystem on NAND ?
>
> 6.4.1 ARMLE
>
> Customer wants to use a FAT filesystem on their NAND chips
> (on an Atmel ARM board), so that they can plug into a PC as a
> USB device for uploads to the PC directly from the filesystem.
Do we need to be able to read/write the FAT filesystem, or is it purely
for the benefit of the PC?
If the PC is mounting it, then the device only needs to provide a block
interface to the raw device, so that a umass-device controller can
access the requested blocks.
>
> They want the FAT filesystem to support ECC and, ideally
> wear-levelling.
> I have explained that it is not power safe and they're fine with that.
>
> I don't think fs-dos can run on NAND, but is that true ?
That's true. We don't have a NAND devb right now (which is required for
io-blk, which is required for fs-dos).
>
> They also want to boot from the NAND:
> "
> We have a requirement to boot from the NAND.
> From the Atmel datasheet:
> "The first block must be guaranteed by the
> manufacturer. There is no ECC check.
That's a standard guarentee from NAND manufacturers.
> The NVM bootloader program (this is the ROM code
> running on power up) looks for a boot.bin file in the root
> directory of a FAT12/16/32 formatted NVM Flash."
> "
>
> I'm guessing we could support this, in theory, by leaving the
> boot area free, and only running a QNX partition./filesystem
> on part of the NAND. So, if there's already a filesystem on
> the first N blocks of the NAND, we can ignore it and just run
> on the rest - is that reasonable ?
Pretty much. All the NAND solutions we've ever done leave a 1:1 area at
the front for boot code, and then start the filesystem some number of
blocks later. It depends on what their bootloader expects for
filesystem positioning, but I would assume the same as you: just put a
small raw area at the front that holds the bootloader, and then format
the rest with FAT.
For a PC to mount this, there's probably going to need to be a partition
table also, since the partition won't be starting at the very first
block.
>
> Thanks
>
> Dave
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post35961
>
>
|
|
|
|
|
|
Dave Bott(deleted)
|
RE: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
08/14/2009 10:54 AM
post36013
|
RE: FAT32 filesystem on NAND ?
Thanks for your reply David !
The FAT file system does need to be read/written by QNX Neutrino, to generate the files that can be uploaded to the PC.
So, it sounds like we definitely don't support this today.
Hopefully, it is understood *why* they want to do this - any plans for us to support devb on NAND ?
Lots of devices get plugged in to PCs these days... it's such a convenient thing to do.
Thanks
Dave
________________________________
From: David Sarrazin [mailto:community-noreply@qnx.com]
Sent: Fri 14/08/2009 7:26 AM
To: general-filesystems
Subject: RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: August 13, 2009 5:08 PM
> To: general-filesystems
> Subject: FAT32 filesystem on NAND ?
>
> 6.4.1 ARMLE
>
> Customer wants to use a FAT filesystem on their NAND chips
> (on an Atmel ARM board), so that they can plug into a PC as a
> USB device for uploads to the PC directly from the filesystem.
Do we need to be able to read/write the FAT filesystem, or is it purely
for the benefit of the PC?
If the PC is mounting it, then the device only needs to provide a block
interface to the raw device, so that a umass-device controller can
access the requested blocks.
>
> They want the FAT filesystem to support ECC and, ideally
> wear-levelling.
> I have explained that it is not power safe and they're fine with that.
>
> I don't think fs-dos can run on NAND, but is that true ?
That's true. We don't have a NAND devb right now (which is required for
io-blk, which is required for fs-dos).
>
> They also want to boot from the NAND:
> "
> We have a requirement to boot from the NAND.
> From the Atmel datasheet:
> "The first block must be guaranteed by the
> manufacturer. There is no ECC check.
That's a standard guarentee from NAND manufacturers.
> The NVM bootloader program (this is the ROM code
> running on power up) looks for a boot.bin file in the root
> directory of a FAT12/16/32 formatted NVM Flash."
> "
>
> I'm guessing we could support this, in theory, by leaving the
> boot area free, and only running a QNX partition./filesystem
> on part of the NAND. So, if there's already a filesystem on
> the first N blocks of the NAND, we can ignore it and just run
> on the rest - is that reasonable ?
Pretty much. All the NAND solutions we've ever done leave a 1:1 area at
the front for boot code, and then start the filesystem some number of
blocks later. It depends on what their bootloader expects for
filesystem positioning, but I would assume the same as you: just put a
small raw area at the front that holds the bootloader, and then format
the rest with FAT.
For a PC to mount this, there's probably going to need to be a partition
table also, since the partition won't be starting at the very first
block.
>
> Thanks
>
> Dave
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post35961
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post36011
|
|
|
|
|
|
Mario Charest
|
RE: FAT32 filesystem on NAND ?
|
|
Mario Charest
08/14/2009 11:15 AM
post36020
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: Friday, August 14, 2009 10:54 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
> Thanks for your reply David !
>
> The FAT file system does need to be read/written by QNX Neutrino, to
> generate the files that can be uploaded to the PC.
>
Wouldn't it be somewhat easier to write a Windows application that can read ETFS?
> So, it sounds like we definitely don't support this today.
>
> Hopefully, it is understood *why* they want to do this - any plans for
> us to support devb on NAND ?
> Lots of devices get plugged in to PCs these days... it's such a
> convenient thing to do.
Raw NAND devices are not typically plugged in to PC.
>
> Thanks
>
> Dave
>
> ________________________________
>
> From: David Sarrazin [mailto:community-noreply@qnx.com]
> Sent: Fri 14/08/2009 7:26 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
>
>
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: August 13, 2009 5:08 PM
> > To: general-filesystems
> > Subject: FAT32 filesystem on NAND ?
> >
> > 6.4.1 ARMLE
> >
> > Customer wants to use a FAT filesystem on their NAND chips (on an
> > Atmel ARM board), so that they can plug into a PC as a USB device for
> > uploads to the PC directly from the filesystem.
>
> Do we need to be able to read/write the FAT filesystem, or is it purely
> for the benefit of the PC?
> If the PC is mounting it, then the device only needs to provide a block
> interface to the raw device, so that a umass-device controller can
> access the requested blocks.
>
> >
> > They want the FAT filesystem to support ECC and, ideally
> > wear-levelling.
> > I have explained that it is not power safe and they're fine with
> that.
> >
> > I don't think fs-dos can run on NAND, but is that true ?
>
> That's true. We don't have a NAND devb right now (which is required
> for io-blk, which is required for fs-dos).
>
> >
> > They also want to boot from the NAND:
> > "
> > We have a requirement to boot from the NAND.
> > From the Atmel datasheet:
> > "The first block must be guaranteed by the manufacturer.
> There
> > is no ECC check.
>
> That's a standard guarentee from NAND manufacturers.
>
> > The NVM bootloader program (this is the ROM code running on
> > power up) looks for a boot.bin file in the root directory of a
> > FAT12/16/32 formatted NVM Flash."
> > "
> >
> > I'm guessing we could support this, in theory, by leaving the boot
> > area free, and only running a QNX partition./filesystem on part of
> the
> > NAND. So, if there's already a filesystem on the first N blocks of
> > the NAND, we can ignore it and just run on the rest - is that
> > reasonable ?
>
> Pretty much. All the NAND solutions we've ever done leave a 1:1 area
> at the front for boot code, and then start the filesystem some number
> of blocks later. It depends on what their bootloader expects for
> filesystem positioning, but I would assume the same as you: just put a
> small raw area at the front that holds the bootloader, and then format
> the rest with FAT.
>
> For a PC to mount this, there's probably going to need to be a
> partition table also, since the partition won't be starting at the very
> first block.
>
>
>
> >
> > Thanks
> >
> > Dave
> >
> >
> >
> >...
|
|
|
|
|
|
Dave Bott(deleted)
|
RE: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
08/14/2009 11:23 AM
post36022
|
RE: FAT32 filesystem on NAND ?
Hi Mario,
It certainly would be possible to write ETFS for Windows, but then you couldn't plug the device into practically *any*
Windows box without having to install extra software - this customer wants to use a generic approach, which has merit.
You're right that raw NAND chips are not plugged into a PC - no argument here. Their requirement is only a little
unusual; it is quite common to make the filesystem of a device visible over USB. They will have SD or SDHC card(s) (with
FAT), but also want the internal filesystem (the NAND chips) to be visible too.
I think *a* way to go here, assuming (and it's a big assumption) a read-only requirement from Windows, could be to
create an emulation layer, making the ETFS look like a FAT FS. If it's just reading files and directories, that should
be possible. Writing gets a lot more hairy...
Dave
________________________________
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Fri 14/08/2009 8:15 AM
To: general-filesystems
Subject: RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: Friday, August 14, 2009 10:54 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
> Thanks for your reply David !
>
> The FAT file system does need to be read/written by QNX Neutrino, to
> generate the files that can be uploaded to the PC.
>
Wouldn't it be somewhat easier to write a Windows application that can read ETFS?
> So, it sounds like we definitely don't support this today.
>
> Hopefully, it is understood *why* they want to do this - any plans for
> us to support devb on NAND ?
> Lots of devices get plugged in to PCs these days... it's such a
> convenient thing to do.
Raw NAND devices are not typically plugged in to PC.
>
> Thanks
>
> Dave
>
> ________________________________
>
> From: David Sarrazin [mailto:community-noreply@qnx.com]
> Sent: Fri 14/08/2009 7:26 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
>
>
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: August 13, 2009 5:08 PM
> > To: general-filesystems
> > Subject: FAT32 filesystem on NAND ?
> >
> > 6.4.1 ARMLE
> >
> > Customer wants to use a FAT filesystem on their NAND chips (on an
> > Atmel ARM board), so that they can plug into a PC as a USB device for
> > uploads to the PC directly from the filesystem.
>
> Do we need to be able to read/write the FAT filesystem, or is it purely
> for the benefit of the PC?
> If the PC is mounting it, then the device only needs to provide a block
> interface to the raw device, so that a umass-device controller can
> access the requested blocks.
>
> >
> > They want the FAT filesystem to support ECC and, ideally
> > wear-levelling.
> > I have explained that it is not power safe and they're fine with
> that.
> >
> > I don't think fs-dos can run on NAND, but is that true ?
>
> That's true. We don't have a NAND devb right now (which is required
> for io-blk, which is required for fs-dos).
>
> >
> > They also want to boot from the NAND:
> > "
> > We have a requirement to boot from the NAND.
> > From the Atmel datasheet:
> > "The first block must be guaranteed by the manufacturer.
> There
> > is no ECC check.
>
> That's a standard guarentee from NAND manufacturers.
>
> > The NVM bootloader program (this is the ROM code running on
> > power up) looks for a boot.bin file in the root directory of a
> > FAT12/16/32 formatted NVM Flash."
> > "
> >
> > I'm guessing we could...
View Full Message
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
08/14/2009 11:33 AM
post36024
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: August 14, 2009 11:24 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
> Hi Mario,
>
> It certainly would be possible to write ETFS for Windows, but
> then you couldn't plug the device into practically *any*
> Windows box without having to install extra software - this
> customer wants to use a generic approach, which has merit.
>
> You're right that raw NAND chips are not plugged into a PC -
> no argument here. Their requirement is only a little unusual;
> it is quite common to make the filesystem of a device visible
> over USB. They will have SD or SDHC card(s) (with FAT), but
> also want the internal filesystem (the NAND chips) to be visible too.
>
> I think *a* way to go here, assuming (and it's a big
> assumption) a read-only requirement from Windows, could be to
> create an emulation layer, making the ETFS look like a FAT
> FS. If it's just reading files and directories, that should
> be possible. Writing gets a lot more hairy...
Filesystem-in-a-file. A FAT "filesystem" inside an ETFS partition. I
could envision starting ETFS, and then devb-loopback, and running the
umass_device code on top of the /dev/lo0 provided by devb-loopback, or
mounting the filesystem when NOT connected to a PC. Don't ask about
performance though.
>
> Dave
>
> ________________________________
>
> From: Mario Charest [mailto:community-noreply@qnx.com]
> Sent: Fri 14/08/2009 8:15 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: Friday, August 14, 2009 10:54 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> > Thanks for your reply David !
> >
> > The FAT file system does need to be read/written by QNX
> Neutrino, to
> > generate the files that can be uploaded to the PC.
> >
>
> Wouldn't it be somewhat easier to write a Windows application
> that can read ETFS?
>
> > So, it sounds like we definitely don't support this today.
> >
> > Hopefully, it is understood *why* they want to do this -
> any plans for
> > us to support devb on NAND ?
>
> > Lots of devices get plugged in to PCs these days... it's such a
> > convenient thing to do.
>
> Raw NAND devices are not typically plugged in to PC.
>
> >
> > Thanks
> >
> > Dave
> >
> > ________________________________
> >
> > From: David Sarrazin [mailto:community-noreply@qnx.com]
> > Sent: Fri 14/08/2009 7:26 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Dave Bott [mailto:community-noreply@qnx.com]
> > > Sent: August 13, 2009 5:08 PM
> > > To: general-filesystems
> > > Subject: FAT32 filesystem on NAND ?
> > >
> > > 6.4.1 ARMLE
> > >
> > > Customer wants to use a FAT filesystem on their NAND chips (on an
> > > Atmel ARM board), so that they can plug into a PC as a USB device
> > > for uploads to the PC directly from the filesystem.
> >
> > Do we need to be able to read/write the FAT filesystem, or is it
> > purely for the benefit of the PC?
> > If the PC is mounting it, then the device only needs to provide a
> > block interface to the raw device, so that a umass-device
> controller
> > can access the requested...
View Full Message
|
|
|
|
|
|
Mario Charest
|
RE: FAT32 filesystem on NAND ?
|
|
Mario Charest
08/14/2009 11:34 AM
post36026
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: David Sarrazin [mailto:community-noreply@qnx.com]
> Sent: Friday, August 14, 2009 11:33 AM
> To: general-filesystems
> Subject: RE: FAT32 filesystem on NAND ?
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: August 14, 2009 11:24 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> > Hi Mario,
> >
> > It certainly would be possible to write ETFS for Windows, but
> > then you couldn't plug the device into practically *any*
> > Windows box without having to install extra software - this
> > customer wants to use a generic approach, which has merit.
> >
> > You're right that raw NAND chips are not plugged into a PC -
> > no argument here. Their requirement is only a little unusual;
> > it is quite common to make the filesystem of a device visible
> > over USB. They will have SD or SDHC card(s) (with FAT), but
> > also want the internal filesystem (the NAND chips) to be visible too.
> >
> > I think *a* way to go here, assuming (and it's a big
> > assumption) a read-only requirement from Windows, could be to
> > create an emulation layer, making the ETFS look like a FAT
> > FS. If it's just reading files and directories, that should
> > be possible. Writing gets a lot more hairy...
>
> Filesystem-in-a-file. A FAT "filesystem" inside an ETFS partition. I
> could envision starting ETFS, and then devb-loopback, and running the
> umass_device code on top of the /dev/lo0 provided by devb-loopback, or
> mounting the filesystem when NOT connected to a PC. Don't ask about
> performance though.
>
Windows still wouln't be able to read it, right?
>
>
> >
> > Dave
> >
> > ________________________________
> >
> > From: Mario Charest [mailto:community-noreply@qnx.com]
> > Sent: Fri 14/08/2009 8:15 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Dave Bott [mailto:community-noreply@qnx.com]
> > > Sent: Friday, August 14, 2009 10:54 AM
> > > To: general-filesystems
> > > Subject: RE: FAT32 filesystem on NAND ?
> > >
> > > Thanks for your reply David !
> > >
> > > The FAT file system does need to be read/written by QNX
> > Neutrino, to
> > > generate the files that can be uploaded to the PC.
> > >
> >
> > Wouldn't it be somewhat easier to write a Windows application
> > that can read ETFS?
> >
> > > So, it sounds like we definitely don't support this today.
> > >
> > > Hopefully, it is understood *why* they want to do this -
> > any plans for
> > > us to support devb on NAND ?
> >
> > > Lots of devices get plugged in to PCs these days... it's such a
> > > convenient thing to do.
> >
> > Raw NAND devices are not typically plugged in to PC.
> >
> > >
> > > Thanks
> > >
> > > Dave
> > >
> > > ________________________________
> > >
> > > From: David Sarrazin [mailto:community-noreply@qnx.com]
> > > Sent: Fri 14/08/2009 7:26 AM
> > > To: general-filesystems
> > > Subject: RE: FAT32 filesystem on NAND ?
> > >
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Dave Bott [mailto:community-noreply@qnx.com]
> > > > Sent: August 13, 2009 5:08 PM
>...
View Full Message
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
08/14/2009 11:47 AM
post36029
|
RE: FAT32 filesystem on NAND ?
[snip]
> >
> > Filesystem-in-a-file. A FAT "filesystem" inside an ETFS
> partition. I
> > could envision starting ETFS, and then devb-loopback, and
> running the
> > umass_device code on top of the /dev/lo0 provided by
> devb-loopback, or
> > mounting the filesystem when NOT connected to a PC. Don't
> ask about
> > performance though.
> >
>
> Windows still wouln't be able to read it, right?
Windows isn't reading the NAND directly, it's over USB (from Dave's
original post), so Windows is talking UMASS to some umass device driver
on the board. The FAT code in Windows is driving what blocks to read,
and the umass_device on the target is pulling them from the
FAT-in-a-file. Devb-loopback is in there to allow the target to mount
the partition locally, when not connected to a PC.
>
> >
> >
> > >
> > > Dave
> > >
[snip]
|
|
|
|
|
|
Dave Bott(deleted)
|
Re: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/09/2009 4:44 PM
post37693
|
Re: FAT32 filesystem on NAND ?
So, after a few travails, I'm in a position to try this...
I have an Atmel ARM G45 running 6.4.1.
I have etfs on it, formatted and mounted.
However, there's no devb-loopback in 6.4.1. I can see the source in svn
- do I have to build it, or is there a prebuilt version I can grab ?
Then, if we don't ship devb-loopback as standard product, is it safe to
suggest its use to a customer ? This will be a production device, and
this element will be crucial...
Then, what is the procedure for using devb-loopback ?
Do you create a file first, then reference it with devb-loopback ?
Does the file need to be pre-grown ?
Any suggested options to devb-loopback ?
In this case, they have a 2GBit NAND (256MB) and want the DOS filesystem
to be ~230MB of it - so is there a way to grab that space for this DOS
filesystem ?
They are jumping up and down to try this ASAP...
Thanks
Dave
David Sarrazin wrote:
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: August 14, 2009 11:24 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> > Hi Mario,
> >
> > It certainly would be possible to write ETFS for Windows, but
> > then you couldn't plug the device into practically *any*
> > Windows box without having to install extra software - this
> > customer wants to use a generic approach, which has merit.
> >
> > You're right that raw NAND chips are not plugged into a PC -
> > no argument here. Their requirement is only a little unusual;
> > it is quite common to make the filesystem of a device visible
> > over USB. They will have SD or SDHC card(s) (with FAT), but
> > also want the internal filesystem (the NAND chips) to be visible too.
> >
> > I think *a* way to go here, assuming (and it's a big
> > assumption) a read-only requirement from Windows, could be to
> > create an emulation layer, making the ETFS look like a FAT
> > FS. If it's just reading files and directories, that should
> > be possible. Writing gets a lot more hairy...
>
> Filesystem-in-a-file. A FAT "filesystem" inside an ETFS partition. I
> could envision starting ETFS, and then devb-loopback, and running the
> umass_device code on top of the /dev/lo0 provided by devb-loopback, or
> mounting the filesystem when NOT connected to a PC. Don't ask about
> performance though.
>
>
>
> >
> > Dave
> >
> > ________________________________
> >
> > From: Mario Charest [mailto:community-noreply@qnx.com]
> > Sent: Fri 14/08/2009 8:15 AM
> > To: general-filesystems
> > Subject: RE: FAT32 filesystem on NAND ?
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Dave Bott [mailto:community-noreply@qnx.com]
> > > Sent: Friday, August 14, 2009 10:54 AM
> > > To: general-filesystems
> > > Subject: RE: FAT32 filesystem on NAND ?
> > >
> > > Thanks for your reply David !
> > >
> > > The FAT file system does need to be read/written by QNX
> > Neutrino, to
> > > generate the files that can be uploaded to the PC.
> > >
> >
> > Wouldn't it be somewhat easier to write a Windows application
> > that can read ETFS?
> >
> > > So, it sounds like we definitely don't support this today.
> > >
> > > Hopefully, it is understood *why* they want to do this -
> > any plans for
> > > us to support devb on NAND ?
> >
> > > Lots of devices get plugged in to PCs these days... it's such a
> > > convenient thing to do.
> >
> > Raw NAND devices are not typically plugged...
View Full Message
|
|
|
|
|
|
Steve Reid
|
Re: FAT32 filesystem on NAND ?
|
|
Steve Reid
09/09/2009 5:11 PM
post37695
|
Re: FAT32 filesystem on NAND ?
You'll be pleased to hear that devb-loopback is going into 6.4.2, so I guess it's OK for your customer to use it.
There's an entry for it in the 6.4.2 Utilities Reference that might help you:
http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
If it doesn't, please make suggestions for improving it (as if I could stop you...)
Steve Reid (stever@qnx.com)
Technical Editor
QNX Software Systems
|
|
|
|
|
|
Dave Bott(deleted)
|
RE: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/09/2009 5:15 PM
post37698
|
RE: FAT32 filesystem on NAND ?
Excellent - thanks Steve !
One suggestion jumps out - can you make at least one example with rw as an option - both examples are read-only today.
Cheers
Dave
_____
From: Steve Reid [mailto:community-noreply@qnx.com]
Sent: Wed 09/09/2009 2:11 PM
To: general-filesystems
Subject: Re: FAT32 filesystem on NAND ?
You'll be pleased to hear that devb-loopback is going into 6.4.2, so I guess it's OK for your customer to use it.
There's an entry for it in the 6.4.2 Utilities Reference that might help you:
http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
If it doesn't, please make suggestions for improving it (as if I could stop you...)
Steve Reid (stever@qnx.com)
Technical Editor
QNX Software Systems
_______________________________________________
General
http://community.qnx.com/sf/go/post37695
|
|
|
|
|
|
Thomas Luetzel
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
|
|
Thomas Luetzel
09/10/2009 12:23 AM
post37709
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
Ich werde ab 22.08.2009 nicht im Büro sein. Ich kehre zurück am
13.09.2009.
I will answer this mail after my return.
Kind Regards,
Thomas Luetzel
_________________________________________________________________________
Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf
Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf
__________________________________________________________________________
Disclaimer:
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.
__________________________________________________________________________
http://www.endress.com/
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
09/09/2009 5:16 PM
post37699
|
RE: FAT32 filesystem on NAND ?
The first sentence for the "fd=path" option is confusing. "path" is a
path to the device (or file) that devb-loopback should treat as the
backing-store for it's block special device.
> -----Original Message-----
> From: Steve Reid [mailto:community-noreply@qnx.com]
> Sent: September 9, 2009 5:11 PM
> To: general-filesystems
> Subject: Re: FAT32 filesystem on NAND ?
>
> You'll be pleased to hear that devb-loopback is going into
> 6.4.2, so I guess it's OK for your customer to use it.
> There's an entry for it in the 6.4.2 Utilities Reference that
> might help you:
>
> http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
>
> If it doesn't, please make suggestions for improving it (as
> if I could stop you...)
>
>
> Steve Reid (stever@qnx.com)
> Technical Editor
> QNX Software Systems
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37695
>
>
|
|
|
|
|
|
Thomas Luetzel
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
|
|
Thomas Luetzel
09/10/2009 12:22 AM
post37707
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
Ich werde ab 22.08.2009 nicht im Büro sein. Ich kehre zurück am
13.09.2009.
I will answer this mail after my return.
Kind Regards,
Thomas Luetzel
_________________________________________________________________________
Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf
Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf
__________________________________________________________________________
Disclaimer:
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.
__________________________________________________________________________
http://www.endress.com/
|
|
|
|
|
|
Dave Bott(deleted)
|
Re: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/10/2009 12:52 PM
post37759
|
Re: FAT32 filesystem on NAND ?
I have a devb-loopback built, but how do I get a DOS FS onto the ETFS ?
I tried creating an empty file and mounting that - not too surprisingly
the mount fails with 'corrupted file system' which seems fair.
I'm starting devb-loopback with:
devb-loopback blk cache=256k,vnode=128 loopback
rw,blksz=2048,fd=/flash/dosfs
where /flash/dosfs is the file on the etfs filesystem (mounted as
/flash) that I want to use.
So, how do I make 'dosfs' look like a dos filesystem ?
Sorry to be so clueless....
Dave
David Sarrazin wrote:
>
> The first sentence for the "fd=path" option is confusing. "path" is a
> path to the device (or file) that devb-loopback should treat as the
> backing-store for it's block special device.
>
>
>
> > -----Original Message-----
> > From: Steve Reid [mailto:community-noreply@qnx.com]
> > Sent: September 9, 2009 5:11 PM
> > To: general-filesystems
> > Subject: Re: FAT32 filesystem on NAND ?
> >
> > You'll be pleased to hear that devb-loopback is going into
> > 6.4.2, so I guess it's OK for your customer to use it.
> > There's an entry for it in the 6.4.2 Utilities Reference that
> > might help you:
> >
> > http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
> >
> > If it doesn't, please make suggestions for improving it (as
> > if I could stop you...)
> >
> >
> > Steve Reid (stever@qnx.com)
> > Technical Editor
> > QNX Software Systems
> >
> >
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post37695
> >
> >
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37699
>
--
Dave Bott (dbott@qnx.com) Field Applications Engineer
QNX Software Systems, Inc. Cell:408 391-3535
San Jose CA
Join Foundry27 <http://community.qnx.com>; - the new QNX developer forum.
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
09/10/2009 12:57 PM
post37761
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: September 10, 2009 12:52 PM
> To: general-filesystems
> Subject: Re: FAT32 filesystem on NAND ?
>
> I have a devb-loopback built, but how do I get a DOS FS onto
> the ETFS ?
>
> I tried creating an empty file and mounting that - not too
> surprisingly the mount fails with 'corrupted file system'
> which seems fair.
>
> I'm starting devb-loopback with:
> devb-loopback blk cache=256k,vnode=128 loopback
> rw,blksz=2048,fd=/flash/dosfs
>
> where /flash/dosfs is the file on the etfs filesystem (mounted as
> /flash) that I want to use.
>
> So, how do I make 'dosfs' look like a dos filesystem ?
You should just have to do
1. fdisk add -t 12 /dev/lo0
2. mount -e /dev/lo0
3. mkdosfs -F32 /dev/lo0t12
>
> Sorry to be so clueless....
>
> Dave
>
>
> David Sarrazin wrote:
> >
> > The first sentence for the "fd=path" option is confusing.
> "path" is a
> > path to the device (or file) that devb-loopback should treat as the
> > backing-store for it's block special device.
> >
> >
> >
> > > -----Original Message-----
> > > From: Steve Reid [mailto:community-noreply@qnx.com]
> > > Sent: September 9, 2009 5:11 PM
> > > To: general-filesystems
> > > Subject: Re: FAT32 filesystem on NAND ?
> > >
> > > You'll be pleased to hear that devb-loopback is going
> into 6.4.2, so
> > > I guess it's OK for your customer to use it.
> > > There's an entry for it in the 6.4.2 Utilities Reference
> that might
> > > help you:
> > >
> > >
> > >
> http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
> > >
> > > If it doesn't, please make suggestions for improving it (as if I
> > > could stop you...)
> > >
> > >
> > > Steve Reid (stever@qnx.com)
> > > Technical Editor
> > > QNX Software Systems
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > >
> > > General
> > > http://community.qnx.com/sf/go/post37695
> > >
> > >
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post37699
> >
>
>
> --
> Dave Bott (dbott@qnx.com) Field Applications Engineer
> QNX Software Systems, Inc. Cell:408 391-3535
> San Jose CA
>
> Join Foundry27 <http://community.qnx.com>; - the new QNX
> developer forum.
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37759
>
>
|
|
|
|
|
|
Dave Bott(deleted)
|
Re: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/10/2009 1:31 PM
post37770
|
Re: FAT32 filesystem on NAND ?
Hmm. the fdisk fails with:
Unable to open device: No such file or directory
Here's what I did:
fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 5128
[I find I need to format the etfs when I reboot - no idea why]
[I see a lot of output like this in sloginfo
760
Jan 01 00:00:38 2 3 800 fs-etfs-at91sam9xx: readtrans DATAERR
on cluster 5824
Jan 01 00:00:38 2 3 800 fs-etfs-at91sam9xx: readtrans DATAERR
on cluster 5888
Jan 01 00:00:38 2 3 800 fs-etfs-at91sam9xx: readtrans DATAERR
on cluster 5952
Jan 01 00:00:39 2 3 800 fs-etfs-at91sam9xx: readtrans BADBLK on
cluster 39424
Jan 01 00:00:39 2 3 800 fs-etfs-at91sam9xx: readtrans BADBLK on
cluster 73984
Jan 01 00:00:39 2 3 800 fs-etfs-at91sam9xx: readtrans BADBLK on
cluster 89600
]
etfsctl -f /dev/etfs2
mount -t etfs /dev/etfs2 /flash
echo > /flash/dosfs
[If I don't create the file, then devb-loopback fails]
devb-loopback blk cache=256k,vnode=128 loopback
rw,blksz=2048,fd=/flash/dosfs
fdisk add -t 12 /dev/lo0
Unable to open device: No such file or directory
[fail]
/dev/lo0 does exist
Any suggestions ?
Thanks !
Dave
David Sarrazin wrote:
>
>
>
> > -----Original Message-----
> > From: Dave Bott [mailto:community-noreply@qnx.com]
> > Sent: September 10, 2009 12:52 PM
> > To: general-filesystems
> > Subject: Re: FAT32 filesystem on NAND ?
> >
> > I have a devb-loopback built, but how do I get a DOS FS onto
> > the ETFS ?
> >
> > I tried creating an empty file and mounting that - not too
> > surprisingly the mount fails with 'corrupted file system'
> > which seems fair.
> >
> > I'm starting devb-loopback with:
> > devb-loopback blk cache=256k,vnode=128 loopback
> > rw,blksz=2048,fd=/flash/dosfs
> >
> > where /flash/dosfs is the file on the etfs filesystem (mounted as
> > /flash) that I want to use.
> >
> > So, how do I make 'dosfs' look like a dos filesystem ?
>
> You should just have to do
>
> 1. fdisk add -t 12 /dev/lo0
> 2. mount -e /dev/lo0
> 3. mkdosfs -F32 /dev/lo0t12
>
> >
> > Sorry to be so clueless....
> >
> > Dave
> >
> >
> > David Sarrazin wrote:
> > >
> > > The first sentence for the "fd=path" option is confusing.
> > "path" is a
> > > path to the device (or file) that devb-loopback should treat as the
> > > backing-store for it's block special device.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Steve Reid [mailto:community-noreply@qnx.com]
> > > > Sent: September 9, 2009 5:11 PM
> > > > To: general-filesystems
> > > > Subject: Re: FAT32 filesystem on NAND ?
> > > >
> > > > You'll be pleased to hear that devb-loopback is going
> > into 6.4.2, so
> > > > I guess it's OK for your customer to use it.
> > > > There's an entry for it in the 6.4.2 Utilities Reference
> > that might
> > > > help you:
> > > >
> > > >
> > > >
> > http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
> > > >
> > > > If it doesn't, please make suggestions for improving it (as if I
> > > > could stop you...)
> > > >
> > > >
> > > > Steve Reid (stever@qnx.com)
> > > > Technical Editor
> > > > QNX Software Systems
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > >
> > > > General
> > > >...
View Full Message
|
|
|
|
|
|
Thomas Luetzel
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
|
|
Thomas Luetzel
09/11/2009 12:22 AM
post37790
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
Ich werde ab 22.08.2009 nicht im Büro sein. Ich kehre zurück am
13.09.2009.
I will answer this mail after my return.
Kind Regards,
Thomas Luetzel
_________________________________________________________________________
Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf
Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf
__________________________________________________________________________
Disclaimer:
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.
__________________________________________________________________________
http://www.endress.com/
|
|
|
|
|
|
Dave Bott(deleted)
|
Re: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/14/2009 12:12 PM
post37919
|
Re: FAT32 filesystem on NAND ?
fdisk was failing because the suggested command was not quite right:
fdisk /dev/lo0 add -t 12
*does* work.
However, it appears that the file that gets mounted must already be the maximum size required. because the size of the
filesystem that fdisk can create appears to be limited by whatever filesize is already there. So, an empty file is no
use - it won't grow it.
Once I create a larger file, I can create and mount the filesystem. However, I didn't make the file large enough
(started with 64KB) for mkdosfs, so had to repeat with larger file, and use -F16. Once I did that, it worked ! :-)
Is there a command line way to pre-grow a file on etfs ? In this case, I'd like it to be 250MB in size...
The ETFS also seems to require formatting every time, which certainly doesn't seem right. This is an early BSP, so could
just have some issues to be tested, but am I doing something wrong when I start etfs with:
fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 5128
Thanks !
Dave
|
|
|
|
|
|
David Sarrazin
|
RE: FAT32 filesystem on NAND ?
|
|
David Sarrazin
09/14/2009 12:22 PM
post37921
|
RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 12:13 PM
> To: general-filesystems
> Subject: Re: FAT32 filesystem on NAND ?
>
> fdisk was failing because the suggested command was not quite right:
>
> fdisk /dev/lo0 add -t 12
>
> *does* work.
>
> However, it appears that the file that gets mounted must
> already be the maximum size required. because the size of
> the filesystem that fdisk can create appears to be limited by
> whatever filesize is already there. So, an empty file is no
> use - it won't grow it.
>
> Once I create a larger file, I can create and mount the
> filesystem. However, I didn't make the file large enough
> (started with 64KB) for mkdosfs, so had to repeat with larger
> file, and use -F16. Once I did that, it worked ! :-)
>
> Is there a command line way to pre-grow a file on etfs ? In
> this case, I'd like it to be 250MB in size...
>
> The ETFS also seems to require formatting every time, which
> certainly doesn't seem right. This is an early BSP, so could
> just have some issues to be tested, but am I doing something
> wrong when I start etfs with:
>
> fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 5128
The -ek (I'm not sure what -k is, it should be giving an error), will
cause fs-etfs to erase the filesystem on startup. I saw that earlier,
but thought you had added the -e to solve the problem of "have to
format everytime".
>
> Thanks !
>
> Dave
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37919
>
>
|
|
|
|
|
|
Dave Bott(deleted)
|
RE: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/14/2009 12:30 PM
post37922
|
RE: FAT32 filesystem on NAND ?
Hi David,
Thanks for the suggestion, but that is actually part of the board name...
All of the variants of this driver for the Atmel SAM 91 chips are like that.
In the chipio.c source, are lines like this:
if(strcasecmp(cio->board_id,"at91sam9m10-ek") == 0) {
to select the default NAND chip parameters and base address etc.
Regards
Dave
________________________________
From: David Sarrazin [mailto:community-noreply@qnx.com]
Sent: Mon 14/09/2009 9:22 AM
To: general-filesystems
Subject: RE: FAT32 filesystem on NAND ?
> -----Original Message-----
> From: Dave Bott [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 12:13 PM
> To: general-filesystems
> Subject: Re: FAT32 filesystem on NAND ?
>
> fdisk was failing because the suggested command was not quite right:
>
> fdisk /dev/lo0 add -t 12
>
> *does* work.
>
> However, it appears that the file that gets mounted must
> already be the maximum size required. because the size of
> the filesystem that fdisk can create appears to be limited by
> whatever filesize is already there. So, an empty file is no
> use - it won't grow it.
>
> Once I create a larger file, I can create and mount the
> filesystem. However, I didn't make the file large enough
> (started with 64KB) for mkdosfs, so had to repeat with larger
> file, and use -F16. Once I did that, it worked ! :-)
>
> Is there a command line way to pre-grow a file on etfs ? In
> this case, I'd like it to be 250MB in size...
>
> The ETFS also seems to require formatting every time, which
> certainly doesn't seem right. This is an early BSP, so could
> just have some issues to be tested, but am I doing something
> wrong when I start etfs with:
>
> fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 5128
The -ek (I'm not sure what -k is, it should be giving an error), will
cause fs-etfs to erase the filesystem on startup. I saw that earlier,
but thought you had added the -e to solve the problem of "have to
format everytime".
>
> Thanks !
>
> Dave
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37919
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post37921
|
|
|
|
|
|
Dave Bott(deleted)
|
Re: RE: FAT32 filesystem on NAND ?
|
|
Dave Bott(deleted)
09/14/2009 2:57 PM
post37938
|
Re: RE: FAT32 filesystem on NAND ?
Here's what works for me (leaving aside the issue of my specific ETFS seeming to need formatting quite often...)
Thanks for the help !
It assumes you've already formatted the ETFS.
Boot the system
#Start the ETFS file system: (note the -r7000 is a large offset - set this as required)
# For other boards, change the board_id/program name to the appropriate values
fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 7000
# Mount the ETFS file system
mount -t etfs /dev/etfs2 /flash
# Now, create a BIG file on the ETFS. Need it to be the max. required size before mounting it.
# Various ways to do this...
# e.g. A nice controlled way to get a 250MB file.
# dd if=/dev/zero bs=1000k count=250 of=/flash/dosfs
# or, a simple, but uncontrolled way (hit CTRL-C after a few seconds to get a random-sized file !
# cp /dev/zero /flash/dosfs
# Once the file is large enough, create a loopback device associated with the file we're going to mount
devb-loopback blk cache=256k,vnode=128 loopback rw,blksz=2048,fd=/flash/dosfs
# This will create /dev/lo0 as a block device that actually read/writes to the /flash/dosfs file
# create a partition in the new block device - will use all available space on the 'disk'
fdisk /dev/lo0 add -t 12
# Some more magic - mount /dev/lo0 so that the partitions are available
mount -e /dev/lo0
# Now /dev/lo0t12 should exist
# Now, format the DOS partition. If the file is small, replace -F32 with -F16 or -F12
mkdosfs -F32 /dev/lo0t12
# Disk is formatted, now can be mounted (where you want)
mount -t dos /dev/lo0t12 /dos
# Now you have a /dos filesystem that you can read or write.
# On subsequent boots, you run:
fs-etfs-at91sam9xx -D board_id=at91sam9m10-ek -r 7000
waitfor /dev/etfs2
mount -t etfs /dev/etfs2 /flash
# Now the ETFS is up and runninng - start the loopback driver
devb-loopback blk cache=256k,vnode=128 loopback rw,blksz=2048,fd=/flash/dosfs
waitfor /dev/lo0t12
# Mount the Dos disk
mount -t dos /dev/lo0t12 /dos
# waitfor /dos
# Now you can read/write the disk
|
|
|
|
|
|
Thomas Luetzel
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
|
|
Thomas Luetzel
09/11/2009 12:22 AM
post37791
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
Ich werde ab 22.08.2009 nicht im Büro sein. Ich kehre zurück am
13.09.2009.
I will answer this mail after my return.
Kind Regards,
Thomas Luetzel
_________________________________________________________________________
Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf
Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf
__________________________________________________________________________
Disclaimer:
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.
__________________________________________________________________________
http://www.endress.com/
|
|
|
|
|
|
Thomas Luetzel
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
|
|
Thomas Luetzel
09/11/2009 12:22 AM
post37792
|
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]
Ich werde ab 22.08.2009 nicht im Büro sein. Ich kehre zurück am
13.09.2009.
I will answer this mail after my return.
Kind Regards,
Thomas Luetzel
_________________________________________________________________________
Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf
Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf
__________________________________________________________________________
Disclaimer:
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.
__________________________________________________________________________
http://www.endress.com/
|
|
|
|
|
|
Steve Reid
|
RE: FAT32 filesystem on NAND ?
|
|
Steve Reid
09/09/2009 5:15 PM
post37697
|
RE: FAT32 filesystem on NAND ?
You'll be pleased to hear that devb-loopback is going into 6.4.2, so I
guess it's OK for your customer to use it. There's an entry for it in
the 6.4.2 Utilities Reference that might help you:
http://stevernto.ott.qnx.com/neutrino/utilities/d/devb-loopback.html
If it doesn't, please make suggestions for improving it (as if I could
stop you...)
Steve Reid (stever@qnx.com)
Technical Editor
QNX Software Systems
|
|
|
|
|
|
