-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED and Error: Failed to get flash maps (4294967290)! (OCD-666) #260
Comments
Here it is with -d3 output: User : 3 0 options.c:63 configuration_output_handler(): debug_level: 3 Debug: 210 0 command.c:166 script_debug(): command - esp32.cpu1 configure -event gdb-attach Debug: 211 0 command.c:166 script_debug(): command - esp32.cpu1 configure -event reset-assert-post soft_reset_halt Debug: 213 0 command.c:166 script_debug(): command - esp32.cpu1 configure -event examine-end Debug: 214 0 command.c:166 script_debug(): command - add_help_text program_esp32 write an image to flash, address is only required for binary images. verify, reset, exit are optional Debug: 304 47 command.c:166 script_debug(): command - arm semihosting enable Debug: 322 58 command.c:166 script_debug(): command - arm semihosting enable Debug: 405 84 command.c:166 script_debug(): command - arm semihosting enable Debug: 455 99 command.c:166 script_debug(): command - arm semihosting enable Debug: 468 99 command.c:166 script_debug(): command - arm semihosting enable |
Hi @skanky-dev !
This confusing error message can be printed on Windows, but it does not prevent debugger from working properly. So you just can ignore it.
|
Thank you very much. I'm not used to tools where errors in the output should be ignored and assumed this was the cause of what it turns out are unrelated issues being able to program and debug this project. |
Probably we need to convert it to warning to avoid confusion. @erhankur What do you think?
If I am not wrong |
Ah OK, I thought it related to the "Warn : Failed to get flash mappings (-4)!" message after it. Thanks for clarifying |
Yes, I agree. Actually, we were printing a warning message but looks like it is broken now. Will be fixed in one of the upcoming commits. |
Hi, I also had these errors recently.
I fixed this by replacing USB driver. The ones installed by idf-env and Zadig weren't working, just UsbDriverTool worked for me. I set on Interface 0 "USB Serial Device".
It was due to wrong setting "Partition Table -> Offset of partition table" in sdkconfig. Changing to default 0x8000 helped. |
Development Kit
Custom Hardware
Module or chip used
ESP32-WROOM-32E (16MB)
Debug Adapter
ESP-PROG
OpenOCD version
v0.11.0-esp32-20220706
Operating System
Win10 Pro
Using an IDE ?
Command line and VS Code
OpenOCD command line
C:\Espressif\frameworks\esp-idf-v4.4.3>openocd -f board/esp32-wrover-kit-3.3v.cfg
JTAG Clock Speed
20000 kHz
ESP-IDF version
1.0.3
Problem Description
Using this on the command line: openocd -l openocd_log.txt -f board/esp32-wrover-kit-3.3v.cfg -c "init; reset halt; flash erase_address 0x1000 61440; exit"
I get errors and warnings that I can find no explanation or resolution for:
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: Failed to get flash maps (4294967290)!
Warn : Failed to get flash mappings (-4)!
Debug Logs
Expected behavior
Operation should complete without errors
Screenshots
The text was updated successfully, but these errors were encountered: