Products > Test Equipment

Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)

<< < (12/74) > >>

bitseeker:
Yeah, the Rigol manual (which version is that from, BravoV?) says maximum 8GB formatted as FAT32. However, there have been problems reported that conflict with the manual. Rstofer just posted success with 2GB FAT16 and 256GB FAT32. Others have had failures with 2GB FAT32.

I upgrade my scope with a 512MB FAT16, which defaults to either 8KB or 16KB clusters on Windows.(Unfortunately, Microsoft doesn't explicitly specify the size ranges. Grrr! e.g., 256 MB–512 MB has 8KB clusters; 512 MB - 1 GB has 16KB clusters. So, to which range does 512 MB apply?

It would've been helpful if Rigol published what maximum cluster size is supported.

frozenfrogz:
Testing out different allocation unit sizes might be worth trying.
BRB

BravoV:

--- Quote from: bitseeker on April 15, 2017, 04:52:36 pm ---Yeah, the Rigol manual (which version is that from, BravoV?) says maximum 8GB formatted as FAT32. However, there have been problems reported that conflict with the manual. Rstofer just posted success with 2GB FAT16 and 256GB FAT32. Others have had failures with 2GB FAT32.

I upgrade my scope with a 512MB FAT16, which defaults to either 8KB or 16KB clusters on Windows.(Unfortunately, Microsoft doesn't explicitly specify the size ranges. Grrr! e.g., 256 MB–512 MB has 8KB clusters; 512 MB - 1 GB has 16KB clusters. So, to which range does 512 MB apply?

It would've been helpful if Rigol published what maximum cluster size is supported.

--- End quote ---

The manual is dated Dec 2015, didn't aware if there is newer one. Downloaded it quite long ago though.

Looking at the USB flash drive fiasco, I suspected Rigol programmer probably either was using a really crappy FAT(32/16) library, or they screwed the library by forking/shrinking it too much, maybe to save flash size or RAM memory or even CPU cycles ?  :-//

frozenfrogz:
I took two USB sticks, one with 32Gb and one with 2Gb and tried to get my Rigol fail on write due to unsupported allocation size. Everything passed.

drive size   |file system |allocation unit size |Rigol write test 2Gb / 32Gb FAT16 32 kbyte PASS 2Gb / 32Gb FAT16 64 kbyte PASS 2Gb FAT32 512 byte PASS 2Gb / 32Gb FAT32 1024 byte PASS 2Gb / 32Gb FAT32 2048 byte PASS 2Gb / 32Gb FAT32 4096 byte PASS 2Gb / 32Gb FAT32 8192 byte PASS 2Gb / 32Gb FAT32 16 kbyte PASS 32Gb FAT32 32 kbyte PASS 32Gb FAT32 64 kbyte PASS
(formatted on Windows 7 32bit machine via on-board disk utility)

But as I reported before, there have been no issues with USB drives on my scope (apart from the obvious: NTFS / ExFAT / OS X Extended formatted drives)
I would need an USB drive that is reportedly not working to further investigate...

smithnerd:

--- Quote from: BravoV on April 15, 2017, 05:10:24 pm ---
--- Quote from: bitseeker on April 15, 2017, 04:52:36 pm ---Yeah, the Rigol manual (which version is that from, BravoV?) says maximum 8GB formatted as FAT32. However, there have been problems reported that conflict with the manual. Rstofer just posted success with 2GB FAT16 and 256GB FAT32. Others have had failures with 2GB FAT32.

I upgrade my scope with a 512MB FAT16, which defaults to either 8KB or 16KB clusters on Windows.(Unfortunately, Microsoft doesn't explicitly specify the size ranges. Grrr! e.g., 256 MB–512 MB has 8KB clusters; 512 MB - 1 GB has 16KB clusters. So, to which range does 512 MB apply?

It would've been helpful if Rigol published what maximum cluster size is supported.

--- End quote ---

The manual is dated Dec 2015, didn't aware if there is newer one. Downloaded it quite long ago though.

Looking at the USB flash drive fiasco, I suspected Rigol programmer probably either was using a really crappy FAT(32/16) library, or they screwed the library by forking/shrinking it too much, maybe to save flash size or RAM memory or even CPU cycles ?  :-//

--- End quote ---

The library is called MFS, it's part of Freescale/NXP's MQX. Somebody put an (unofficial) mirror of the source code tree on github, if you're curious:

https://github.com/gxliu/MQX-3.7.0/tree/master/mfs

...though some code from later MQX releases (3.7 is ancient) may have been back-ported into Rigol's build.

Edited to add: Freescale MQX(TM) MFS(TM) User’s Guide:

https://raw.githubusercontent.com/gxliu/MQX-3.7.0/master/doc/mfs/MQXMFSUG.pdf


Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod