I have commented USE_INVERTED_DISK_DATA but PCFlash show: "Data is inverted"

[Miyuki]

Hello,
I have the application done as I want. But I have a problem with uploading it.

When I use PCFlash with spiall.spi
pcflash.exe -p 6 -l spiall.spi
Data is inverted, reserved blocks 64
...
Programming Finished Successfully

It runs OK
But then I must format FAT and upload files separately

If I try to include file with
pcflash.exe -p 6 -l spiall.spi -f 01.ogg
Data is non-inverted, reserved blocks 32
...
SPI Programming Failed, Retrying..
Programming failed

It just failed

And when I create Image with ImageGenerator and put files inside
it shows
Data is inverted, reserved blocks 64
And Flashes OK but still no valid FAT with files is visible

Where is the problem?

in system.h
// storing the disk data inverted is optimal for the system.
// storing the disk data uninverted (as is) makes it easier to debug the SPI image
//#define USE_INVERTED_DISK_DATA 1

[pasi]

Hi,
The -f option is only intended to work with the Voicemail firmware. In addition to being a custom format (instead of FAT), it sets reserved sectors to 32 and removes invert.

If you want the normal FAT with non-inverted data, use the "-i fatimage" and "-noinvert" options.

When you run pcflash with the -h option you get something like:

Code: Select all

pcflash 1.0 (Sep 28 2018)
Usage: /usr/local/projects/VS1000/sw/vs1000b-examples/audiomodule/autoprog/pcflash [-p <port>] [-s <speed>] [-l <firmwarefile>]
      [-i <fatimage>]
      [-f <voicemailfile>]*    (Also sets -r 32 and -noinvert)
      [-r <reservedsectors>]   Default: 64
      [-noinvert]              Do not invert audio image data
Example: pcflash -p 1 -s 115200 -r 64 -l spiall.spi -i content.raw

[Miyuki]

Thanks a lot
-l spiall.spi -i content.raw -noinvert
Works fine

btw I have a customer who considering using VS1000 / VSMD001 module in a new design
And is concerned about future availability in the horizon of 5 to 10 years

[pasi]

There are no plans to discontinue VS1000. We keep all chips available for as long as possible.

If the volume is a few thousand vs1000 or vs1000 audio modules per year, I don't think there's any reason to worry or prepare specifically. If the volume is hundred thousand or million chips per year, then detailed discussions and contracts would be needed in any case.