FAT32 file size limitation

Hi Scott,

RTFS is actually provided/developed by a 3rd party outside of TI (EBS software).  The version of RTFS shipped by TI only supports up to FAT32 (so you are limited by the 32GB max file size); however, I believe it is possible for you to upgrade to

a version of RTFS that supports FAT64/exFat.  This is mentioned in the following section of the RTFS user guide (sprugm3a.pdf):

1.5 Upgrading RTFS Features

I've also sent an inquiry to the 3rd party to see if I can get some more details on this.  Once I hear back, I'll reply to this post.

Steve

Steve, 

Thank you so much for your time on this.  I will contact EBS on how to obtain a copy of their FAT64 implementation.  Hopefully, it will plug right into the RTFS.

Scott

Does TI have any plans to incorporate this exFAT solution into future releases of RTFS?  The 4GB file size limit and 138GB Partition limit of FAT32 would seem to be a big limitation given the availability of large inexpensive memory devices for audio and video streaming.

Hi Scott,

Unfortunately TI does not have any near term plans to incorporate exFat into the RTFS product that we ship.  To obtain exFat, you should contact EBS and they should be able to help you.  Were you able to get in touch with EBS?

Steve

I did get a hold of EBS and they were very helpful but they don't have exFAT incorporated into the TI RTFS.  They have an implementation that can be incorporated but it's not quite ready to roll.  I posed the question regarding TI incorporating exFAT because it seems like something that your customers would need.  FAT32 can only handle volumes up to 138 GB and file sizes up 4 GB.  Frankly, I'm a little surprised that no one else has requested this upgrade given these limitations.

Scott

Hi Scott,

I requested this very limitation for months (SATA half working), but unfortunately I had exactly the same response from TI like you have !!!

It's very frustrating and really disappointing where TI does not really stand behind their product !!!

Regards,

~Duy-Ky

Hi Duy-Ky,

I couldn't help but become somewhat confused by your post.  I remember working with you on the problem that you were experiencing, and that Sandeep Krishnaswamy provided you one on one support in order to get past this limitation you had encountered.  After Sandeep had helped you, you had very positive things to say about him and the support that we (TI) had provided.

Was there something else that happened that caused your opinion to change?  Maybe you are experiencing another issue?

Thanks,

Steve

Hi Steve,

Sandeep gave me his driver, it appeared to do partition and format the whole HDD, BUT the PC does NOT recognize it is a FAT !?!?

While the old driver works up to 128 GB and PC sees it as FAT

I agreed with Sandeep that the new problem is Filesystem problem, not driver, so it's beyond his control

Anyway, the problem is still unsolved, and I'm not able to use the whole 500 GB

Thanks for your reponse, Steve,

~Duy-Ky

Duy-Ky,

Ok, thanks for informing me of this.  Is there some forum thread that covers the discussion between you and Sandeep?  In which you determined that the problem is due to the file system?

Steve

Steve,

This is my thought

1) The old driver can partition and format 500 GB to get 128 GB maximum, it's possible to do File_IO in create folder and files and PC can read all of them, using SATA example from RTFS package

2) Using exactly the same RTFS SATA example, the new driver can partition and format the whole 500 GB, not limit to 128 GB, but not able to do File_IO, PC can NOT recognize it as FAT32

3) Sandeep is able to do read/write at the lowest level read/write to disk

So, I see the format, create folder, read & write are filesystem operations, am I correct ?

Attached are test result using the same RTFS SATA example but with old and new drivers

I did send these to Sandeep, and he asked me to post the preoblem in filesystem forum, but I don't know where it is while I had several posts unanswered for months in number of areas, not only SW, not only digital chips, but also analog one (ADS7230), so I gave up with some uncomfortable feeling!!!

Thanks so much for your response, Steve

~Duy-Ky

5710.sata_origEx_oldDrv.txt

4505.sata_origEx_newDrv.txt

Duy-Ky,

I apologize for the lack of response on your issue, but I have been on vacation and so was unable to work on your issue.  I'll look into it more now that I'm back and respond once I have more information.  Thanks for your patience.

Steve