7.15 Error After Style Creation At Fett263 OS7 Style Library

ProffieOS
21

SD Card performance shouldn’t really matter since sound fonts are so small, & 32gb should be more than enough.
Maybe if you’re cataloging your entire sound fonts collection on the same card & its one HUGE collection, I can’t see it being a problem at all.
In that case, I’d just consider getting a SD Card with better performance than average & not focus on the size.

Then again maybe it’s something that doesn’t matter as much now that we have more 3.9 Proffie out there now…

But when it comes to SSD I usually go by the golden rule, only get it if it’s in an actual case no matter bench mark reviews (Gamers Nexus channel on YouTube has the best reviews).
They’re actually selling them without cases now!!! Kinda looks like a big stick of cheap RAM!!!

22

It is always suggested to use this tool for formatting, not just the built-in Windows utility:

23

Beware that larger cards tends to be formatted as vFAT, which proffieOS does not understand. These cards will need to be formatted to use FAT32 instead. If I remember correctly FAT32 works up to 2TB, and even if your card was bigger than that you could make a smaller partition for the FAT32 partition…

24

Thanks, all, for the input. I bought the 64 GB only because they didn’t have any 32 GB at the store when I went to buy one, and I was not aware that the larger size would cause an issue (potentially). Have not had a chance yet to get a 32 GB…hoping to get that in the next day or 2. Will post back after I get it and update what happened.

25

Got a new SD card today - SanDisk 32 GB Ultra Plus advertised with read speeds up to 130 MB/s. Used the SD Memory Card formatter listed in this post. ran an SD test - same speed as the original card, at 1095. Tried both styles I made and paired with the fonts listed in the post, and no change - very slow moving out. Maybe I just happened to pick 2 fonts that have the issue I mentioned, and the rest will work fine - I hope so…otherwise, will have to manually change the speed for each and then test/correct - pretty labor intensive.

26

You should test with the ProffieOS SD speed test, not a standard speed test application on a computer.

  • Comment out or temporarily remove #define DISABLE_DIAGNOSTIC_COMMANDS from your config file.
  • Hook up to serial monitor.
  • type sdtest and watch for the summary results of speed and simultaneous streams.
  • Report back here.
27

That is the test I used each time.

Also, just wondering - why do I have to re-flash the board before every time I upload a new config? If I don’t re-flash, I get an error message at loading. When I re-flash, it loads properly. Every time. I have seen video tutorials mention occasionally needing to re-flash, but I have never seen any that mention re-flashing every time as a matter of course.

28

Reflashing is the ONLY way to update a config. Having a copy of your config on your SD-card is only “nice to have” for backup purpose only, it is never used by your Proffieboard. Every time you change something in your config, the whole ProffieOS gets reflashed on your Proffieboard.

29

“re flashing the board before uploading” is not what’s happening.
If you’re talking about running Zadig, that doesn’t do anything to the Proffieboard, that’s installing a driver on your PC.
Your question should be "why do I need to keep reinstalling the driver before uploading to the board. "

The answer is quite frankly something stupid going on with Windows. If you had a different version (older) of the windows OS, or used a Mac or a Linux machine, you wouldn’t be ever needing to do it.

Uploading in Arduino is where you’re actually programming the Proffieboard.

30

My apologies, I might be using the wrong verbiage - by “re-flashing” the board, I’m talking about those 2 small buttons on the board itself, where you press and hold the one on the left, then press and hold the onew on the right, it chimes on the PC, and then you release the right and then the left buttons. Videos I watched showed that only needing to be done occasionally, yet I have to do it every time before uploading the config file. With regards to Zadig, I did have to run that a few times initially but no more.

31

That is manually putting the board into bootloader mode to force an upload, typically only needed to be done if an interrupted/bad upload occurred and the board is not responsive.

Arduino does that on its own when you click the upload button.
I wrote this a while back, so I’m just going to paste it here:

Proffieboard use 2 different drivers on the computer, depending on how it’s booted.
Just like a PC running Windows would boot into normal Windows OS or into the BIOS to set core settings, or an Android phone can boot into normal Android or bootloader,
Proffieboards either boot into normal mode running ProffieOS, or bootloader mode.
Each of those states looks like a different device to the PC. Different devices require different drivers to talk to your computer properly.
If you install the wrong driver for a device, it’s not going to work, simply put.

When booted normally and running ProffieOS, the board show up as a “Proffieboard”, a composite serial device (CDC data etc…).
Windows typically sees this device when first connected, installs the driver on its own, and will use usbser.sys driver.
The board should be seen in on a COM port in Arduino under menu Tools>Port.
It will not show up here if in bootloader mode.
When it’s in bootloader mode and showing as STM32BOOTLOADER, it needs WinUSB v6.1.7600.16385 driver installed with proffie-dfu-setup or Zadig.
It’s a one-time setup installation when the PC sees the board for the first time in bootloader mode.
It needs this because Arduino is going to put the board in this bootloader mode when you hit Upload so that the board can receive programming.
Then when the upload is complete, the board reboots back into normal ProffieOS.
*** If you do not put the Proffieboard into bootloader mode before running Zadig, you are doing it wrong, and installing the wrong driver for the board because it’s still connected as a “Proffieboard” composite device at that point.

Putting the board into bootloader mode so you can run Zadig and install the correct driver for STM32BOOTLOADER device can be done 2 ways, either with the onboard buttons, or via Serial Monitor in Arduino.
Button sequence is HOLD BOOT, PRESS and RELEASE RESET, then RELEASE BOOT.
Alternately, you could also hold BOOT with one hand, and connect the other end of the USB to the computer while holding BOOT.
Either result in the same sequence that is required; powering on the board while the BOOT button is held.
Serial Monitor command is simply choosing the COM port with the “Proffieboard” under Arduino menu Tools>Port, and sending the command RebootDFU.

If the computer has forgotten the driver, or the driver was overwritten, or SOME stupid Windows thing happened… you might just need to re-run Zadig.
If things still don’t continue working once this is done, you may have another device using a conflicting driver, see this thread for info:

32

See also: ProffieOS Documentation: Understanding usb and uploads

33

Read through and watched the video (as best that I could) - some of this over my head and a little difficult to follow. The video and the awesome text summary supplied were great except…they were made for Windows 10, and Windows 11, which i have , has a sliughtly different format that does not match.

The good news for me is that, after several times re-running Zadig and re-flashing the board (along with the info and help given on this site), everything now seems to be working as it should be…I have uploaded my config to the board a few dozen times as I’ve added more styles and it is working perfectly. Maybe the “gremlin” that was in my PC has moved on to someone else’s? In any event, just wanted to check back in and offer my thanks for all the help!! :slight_smile: