Directory Not Found. Device detected / SD card working

Hi there. Prologue and Mea Culpa: I bit off more than I can chew with the Proffieboard. While I’m great with Excel and VBA I had no intention of dabbling in a new computer language or OS. I just wanted a light saber that I could give a friend with the Friday SoundFont of Pops saying “don’t nobody go in the bathroom for like 35-45 minutes” and then being able to ignite a brown blade. [Long story to that; but somehow I suspect many here are puerile enough to imagine…]

As I’ve come to learn, nay–regret it was much easier said than done. So I find myself here, lost, and desperately trying to right my ship…

I’ve followed many of the YouTube videos, installed Arduino, downloaded Zadig, backed up my SD card. But I’ve 'done messed up, AA-Ron". When I power up my board I get a message that says, “That directory not found”. When plugged into a computer (battery out, SD card in) via a USB data cable, Arduino (v 2.2.1) recognizes the board (info below) . A few other settings: Board = “Proffieboard V2” and USB Type = Serial + Mass Storage + WebUSB.

BN: Butterfly-L433CC
VID: 0x1209
PID: 0x6668
SN: 206F…

The blade has two buttons.

When powered by battery, it generates the same message “Directory Not Found” but is followed by a brief pause, a half-second beep, and a different (more robotic sounding male voice) that says:

“Press reset button”. After doing so, Mr. Roboto says “Press power button”, and I obey. Immediately following pressing the power button, I am instructed to “press auxiliary button”, [done], followed by what sounds like "press second auxiliary button’. It’s here that I get lost; pressing any button (power, reset, aux) after this merely results in a beep.

What I suspect happened is that I overwrote my Config File and need to start over. In my ignorance, when I did the boot-reset I removed the “//” in the Arduino code to: “config/proffieboards_v2_testing_config.h” to the board, overwriting the factory config file. The SD card has NO config file from which to restore.

The vendor provided me a file named “ota.snv4” and said simply “save this to the SD card and things should work”. I did that, and it did NOT work. Am I at least in the right direction? What is the difference between an “.snv4” file and an “.h” file?

Finally, I was fortunate (for many so many reasons) to purchase two blades. I’ve only messed up one. The other is factory fresh and fully functional. Presuming it is the config file, is there a way to view and copy the config file from the working board to my non-working board?

Sorry for so many questions in one chat. But I’m hoping to have covered all the bases before tell the world how dumb I am.

Domo Arigato Mr. Roboto…and thank you for your replies.

Let me also add, that Serial Monitor returns: a battery voltage .23 followed by a long string of “waiting for battery power”, occasionally a ‘batter voltage: 0.18’. It repeats this for several cycles then returns “booster off” then continues.

I’ll translate this to Urdu since it’ll mean as much to me in a language I do NOT speak.

Snv4. File looks like not for proffieboard use. But I am not sure about it. You can go to this website,

, it will helps you generate proper configfile that for proffieboard use. And follow the instructions to upload the configfile to board. Also the font file in sd card should match with configfile too.

First, sorry to disappoint, but this is not really possible, as brown doesn’t show up on an RGB pixel blade.

Yes, you uploaded the proffieboard_test_bench_config.h to the board, overwriting the previously uploaded config file that they programmed the board with.

Well, they gave you a config file that’s used with an SN-V4 board, not a Proffieboard.
You should tell them you need the Proffie config file they had on the saber when you bought it. Reputable vendors should be including that file stored on the SD card for you, or provided electronically to you.

No and Yes.
The compiled and uploaded programming code can not be retrieved in any form that’s useful to the user as far as viewing or editing it. However, you can download it and then upload to the board using this tool:

Use the “Read from USB device” tool and save the downloaded file locally to your computer from the “good” saber.
Then, connect the one you “done messed up” and upload using the “Write to USB device” tool.


This throws everything out the window! Somehow this does not surprise me as I’m not that original…I’ll figure something else. Perhaps a Smokey white color and just roll with the quotes… :thinking:

I believe I’ve seen and heard you say this several times. I really thought they were reputable. They had a website and everything. Do we vendor shame? I will not as I’m holding out hope that they will come through. Still, I suspect that you gave more thought to what I sent than the vendor did. So, I think however, that you’re on to something.

Thank you so much @NoSloppy . I am on this site you provided and it reminds me that the WebUSB Interface because I’ve not done anything with the other board. Before I :face_with_peeking_eye: “deflower” it I want to confirm that pressing the “Boot Reset” won’t mess with this board too…

Second, out of curiosity, I tested the board that’s not working and it uploaded a “firmware.bin” file. Presuming this was what was should have come over do I simply “Write to the USB drive” (of the bad file) and it would do the rest?

Thanks again. Very much grateful for everyone’s help.

@icewaterberg - I appreciate the reply. I did in fact follow the link and tried this approach. The first upload didn’t work because it was Arduino asked me to select my Teensy Board (but I’m not sure I can do that without unselecting the Proffieboard from “Boards Manager” can I?

What I did instead was rem out all the references to Teensy and that nearly, ALMOST, very much seemed like it might…but did not work. The error messages now are about ambiguous files and ‘const unsigned in maxledsperstrip’ which is set at 144.

Is it possible that I was a little too free with the “//” and remmed out code that was needed?

You only “need” to press the buttons on the board one time if you use Zadig to install the STM32BOOTLOADER driver onto a PC.
If you use dfu-proffie-setup, you don’t even need to use the buttons at all.

Once the driver is installed, uploading is just a matter of choosing the board on Arduino menu Tools>Port and clicking upload.

To use the programmer tool I linked:
If the board was programmed without WebUSB chosen in the Arduino menu Tools>USB Type, then you need to boot into bootloader mode manually. So yes, you need the buttons then.

Not sure what you mean.
“Read” will download a firmware.bin file from the “good” board to your computer.
Then, you connect the “bad” target board and “Write” that file to the board.

You are essentially cloning the programming from one saber to another.

As little as possible, please refer to the rules.