Thank you.
Please note that the problem only exists on new cards. Cards that have an acceptable partition table will never show the issue - no matter how many times they are reformatted.
The reason it shows up on new cards is that the need for a partition table on SD-Cards has been removed, so new cards do not have one and Windows will not add one. A partition table does reduce the capacity of the card; this is probably why it has been eliminated.
I have been able to duplicate the error using the LPC55S69-EVK with lpcxpresso55s69_filex_sdcard. What I do is try a new card in this setup - I verify that Windows recognizes the card without having to initialize it, and that I can write files to it. I then test the card in the EVK setup and notice that the software returns an error. The typical error in this case is 0x02 - FX_MEDIA_INVALID.
I have also tried formatting the card without a partition table. In all cases Windows and Linux can mount/read/write the card perfectly. Depending on the version of Windows used to format the card I will get 0x02, 0x03, or 0x21 errors from lpcxpresso55s69_filex_sdcard. The error codes are unique and repeatable according to the OS used to format the card.
If I put a card into an older version of Linux (Ubuntu-14) and make a file system there (Linux's version of format) then the card is usable by all three - Windows, Linux, and FileX. Re-formatting the card in Windows after Linux has created a file system does not make it stop working.
I have found no relationship between the 0x02 error and the size or maker of the card. I have found a 100% relationship between the partition table and card errors.
My issue is that the end user will typically not have the ability - or desire - to manually add a partition table prior to use, and that will prevent them from being able to use the product.
Gary.