-
-
Notifications
You must be signed in to change notification settings - Fork 16
Portenta H7 using 4.1.0-rc2 loses USB after updating firmware #84
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
Comments
Some possible background information. @mjs513 and I have been trying to figure out what is different. Between the GIGA and the Portenta H7 and what changed between the stuff up till the zephyr 4.1. We know that the GIGA uses USB_FS for communications to the pc, where the Portenta uses USB_HS object for the communications. I included the giga and H7 dtsh outputs here in case anyone wants to take a look Now trying to figure out whare the 2nd one (board_cdc_acm_uart) came from and if it matters. |
@facchinm @pillo79 @mjs513 - I believe I have a fix for the USB issue here. I found that object was defined in zephyr: <../boards/common/usb/cdc_acm_serial.dtsi I looked for who included this file and found that only two of the Arduino boards included it:
I also noted that the GIGA had added another chosen define that was in that looked related, so I added it as well
(The uart-mcumgr) line. I removed it from the Portenta H7 board and rebuilt and reflashed and programmed and now have USB working again on the H7 Edit: @mjs513 confirmed the zephyr,uart-mcumgr = &usart6; |
Just started doing some regression testing on the nano, giga and H7. So just tested this on the H7 and release of 0.3.0 fix the issue. |
Describe the bug
Portenta H7 compiles and loads seemly after updating firmware but USB is lost after upload and lost at firmware upload. However Sketch (BLINK) still runs!!!
Target board + cli verbose compilation output
Output of Serial Monitor
NONE - portenta not recognized by windows PC
Optional: attach the sketch
Use blink
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: