I cannot access my Proffieboard v3.9. It does not register as an external drive on my computer, although I can hear the connection noise when I plug it in. Additionally, I cannot upload onto the board through Arduino. When I press the upload button, it seems to work for a second until the board disconnects from my computer, and I get this error message (copied directly from the Arduino program):
C:/Users/19124/AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/../lib/gcc/arm-none-eabi/14.2.1/../../../../arm-none-eabi/bin/ld.exe:C:\Users\19124\AppData\Local\Arduino15\packages\proffieboard\hardware\stm32l4\4.6.0\variants\STM32L452RE-ProffieboardV3/linker_scripts/STM32L452RE_FLASH.ld:224: warning: memory region `SRAM2' not declared
lto-wrapper.exe: warning: using serial compilation of 7 LTRANS jobs
lto-wrapper.exe: note: see the '-flto' option documentation for more information
Sketch uses 270984 bytes (53%) of program storage space. Maximum is 507904 bytes.
1
2
3
4
5
6
Cannot open DFU device 0483:df11
7
Cannot claim the interface
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte, and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Failed uploading: uploading error: exit status 74
When I insert my ad card into my old V2.2, I can access the SD card and the files, so I imagine it is the board itself. Should I just try and get another one, or is this a resolvable issue due to an error on my part.
Does the board work?
Does the port for the board show up under Arduino->Tools->port?
Did you select the right port before uploading?
This would indicate that that it found the DFU device, but was unable to open it.
Usually that indicates a driver problem, but Iām wondering if something else is going on here.
Now this indicates that something else is using the DFU interface. Or maybe it just disappeared?
Iām a bit confused, there seems to be multiple things going on here.
Most of the time, when you canāt access the SD card is because you did an upload without having āmass storageā selected under Arduino->Tools->Usb Type, but that alone would not lead to all these other problems.
In the Arduino program, it appears as connected up until I run it, I have the correct port as COM5 (Butterfly-L344CC, Proffieboard, Proffieboard v2, Proffieboard v3), and I have USB type as serial+mass storage. Iāve tried mass storage as well as serial+mass storage+webusb.
My DOSFS is set to SDIO high speed, and my bootloader is STM32 Bootloader.
Iāll read the article you posted and see if that fixes it
okay so, when I reboot it, it shows up in my control panel as STM32 BOOTLOADER, which is what the article says is correct, but in doing that, it disconnects from COM5, and the Arduino program cannot detect it. If I unplug it and plug it back in, it reconnects and the Arduino program recognizes it; however, my control panel doesnāt detect it as STM32BOOTLOADER but now as āProffieboardā, which⦠is not mentioned in the article\
im still getting exit status 74
C:/Users/19124/AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/ā¦/lib/gcc/arm-none-eabi/14.2.1/ā¦/ā¦/ā¦/ā¦/arm-none-eabi/bin/ld.exe:C:\Users\19124\AppData\Local\Arduino15\packages\proffieboard\hardware\stm32l4\4.6.0\variants\STM32L452RE-ProffieboardV3/linker_scripts/STM32L452RE_FLASH.ld:224: warning: memory region `SRAM2ā not declared
lto-wrapper.exe: warning: using serial compilation of 7 LTRANS jobs
lto-wrapper.exe: note: see the ā-fltoā option documentation for more information
C:/Users/19124/AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/ā¦/lib/gcc/arm-none-eabi/14.2.1/ā¦/ā¦/ā¦/ā¦/arm-none-eabi/bin/ld.exe: warning: start of section .bss changed by 16
Sketch uses 272624 bytes (53%) of program storage space. Maximum is 507904 bytes.
dfu-util 0.9Cannot claim interface
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util / Tickets
Opening DFU capable USB deviceā¦
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interfaceā¦
Failed uploading: uploading error: exit status 74
I searched old posts and stuff, and I came up with two possible reasons for this particular error:
You have chosen the wrong board in Arduino->Tools->Board (like, if you have a V3 board, but you chose V2, or vice versa) Iām not sure why this would cause a ācannot claim interfaceā error, but thatās what people have marked as the solution in the past.
Some other program is taking over the DFU interface. One known culprit is a 3d slicer program, although I donāt remember which one.
There is also the possibility that this is caused by a bad cable or something, but if that was the case I would expect more randomness.
I suppose it could be a power problem. Do you have a battery connected? Is it charged?
Youāre not uploading anything to the SD card through Arduino, youāre uploading a new program (your āversionā of ProffieOS as configured) to the processor chip on the board.
Perhaps that makes things make a bit more sense.
I know Cura was bad about this, thereās probably others though.
I thought having a battery connected only applied to a teensy? Furthermore my v2.2 works fine (i can upload, access my sd card, etc.) without having a battery connected. When i plug in my v3.9 the light comes on so i think its getting power through the cable, is that different?
Good to know! When i say access my SD card i mean through my file explorer. I donāt have any 3D slicer programs i donāt even know what that is. Idk man Iām flying blind here and i appreciate yāallās help
Yeah, I understand you there. It just sounded like you perhaps thought the SD card was a prerequisite and/or otherwise involved in the flashing process, when itās entirely separate.
Perhaps thatās just more confusing, if it is, I apologize.
With respect to the error youāre seeing, Iām afraid Iām not any help. Iāve never encountered that error personally or when troubleshooting with others.
It really shouldnāt matter if you have a battery connected or not.
My thought was that maybe if the battery is connected, and mostly empty, then maybe the computer would be unhappy with the power draw and disconnect the board from the computer, which could mess things up.
Itās all hypothetical though, none of these things should happen, and if the battery is not connected, then they cannot happen.
If thatās the case, then it shouldnāt be a driver issue, in fact, it shouldnāt be anything that is happening on the computer at all.
If you cannot do the recovery method I suggested earlier, and the problem isnāt on the computer, then itās likely that there is something actually wrong with the board itself, or possibly the SD card.
Step one would be to try a different SD card.
Btw, does the board get warm when connected to the computer?
No, my board isnāt getting hot, at least not like my v2.2 does. Iāll go buy a new SD card tonight and hopefully taht will fix it, although im still getting the same errors as before. :
C:/Users/19124/AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/ā¦/lib/gcc/arm-none-eabi/14.2.1/ā¦/ā¦/ā¦/ā¦/arm-none-eabi/bin/ld.exe:C:\Users\19124\AppData\Local\Arduino15\packages\proffieboard\hardware\stm32l4\4.6.0\variants\STM32L452RE-ProffieboardV3/linker_scripts/STM32L452RE_FLASH.ld:224: warning: memory region `SRAM2ā not declared
lto-wrapper.exe: warning: using serial compilation of 7 LTRANS jobs
lto-wrapper.exe: note: see the ā-fltoā option documentation for more information
C:/Users/19124/AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/ā¦/lib/gcc/arm-none-eabi/14.2.1/ā¦/ā¦/ā¦/ā¦/arm-none-eabi/bin/ld.exe: warning: start of section .bss changed by 16
Sketch uses 272624 bytes (53%) of program storage space. Maximum is 507904 bytes.
1
2
3
4
5
6
7
Cannot claim interface
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util / Tickets
Opening DFU capable USB deviceā¦
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interfaceā¦
Failed uploading: uploading error: exit status 74
something interesting that i think is worth mentioning, is that when i first connect my board to my usb cable, it registers in my computer as proffieboard, in the hardware tab of the device properties, i can see the USB Serial Device function, which contains the correct driver:usbser.sys.
However, once i run the arduino proghram, and it disconnects from my computer (and the error message appears) The board is labeled as STM32 BOOTLOADER, which only has one function in the hardware tab, also called STM32 BOOTLOADER, which has 4 driver files:
system32\drivers\libusb0.sys
system32\libusb0.dll
system32\lilusbk.dll
and syswow64\libusb0.dll
maybe this is meaningless but, im not seeing usbser.sys after it disconnects and shows up again as STM32 BOOTLOADER
Edit: I replaced the drivers with zadig, fingers crossed it works
You need to read this, it happens to me once a week.
After a failed upload or a partial failed upload (starts uploading and fails half way), or a 1, 2, 3, ⦠10 countdown (failed upload), I use the buttons on the board, this is the sequence:
with the USB port facing away from you, press and hold the right button (boot), press and release the left button (reset), release the right button (boot), hit upload again (donāt worry about your ProffieBoard showing (not connected) in Arduino because your board has now been forced in STM32 BOOTLOADER, this is the only mode that will let you upload.
or if you get a ācanāt open DFUā error, just hit upload again. Your computer was too slow to pick-up the STM32 BOOTLOADER the first time.
HUZZAH IT WORKED! YIPEEEEE! Reinstalling the drivers with Zadig fixed it. I donāt know what happened, but Zadig must not have remembered it or whatever. Iām glad I had it still installed. And I can access my SD card now! See yall in three days when something else goes wrong