The USB-C on Portenta H7 (used for bootloader - via COM device or as UART interface to talk to board) CONFLICTs with other tools and applications.
All works fine: UART terminal is OK, bootloader is OK,
UNLESS you do this:
- start AC6 STM SystemWorkbench and have it open as an app.
Even, it should not use any UART, USB etc. (I need for other projects, with ST-Link, it just sits there as a running tool)
The bootloader of Portenta H7 does not succeed, the bootloading process is corrupted
(incomplete code flash, errors and it stays in bootloader mode...)
I have to close the app. Why?
BTW: to let the UART connected (using TeraTerm) works fine: it flashes via bootloader, I see
the boot startup - all OK.
The most annoying and very strange issue:
- I want to use Saleae Logic to trace HW signals
NOT POSSIBLE: the USB-C of Portenta H7 conflicts so heavily with it.
No way to use my USB scope together with Portenta H7
This happens - and it is very strange, suspicious and nerve wracking:
-
I start Salea Logic tool: Portenta H7 boots
(I see it on UART) -
I press start on Salea Logic: UART is dead!
And: the green LED on Portenta H7 blinks all time (and keeps blinking even I close, disconnect Salea Logic)
What is this?
Are the USB VID and PID "hijacked"?
Is there an USB driver conflict? (IDs conflicting, not using properly registered USB IDs...?)
Potentially: Salea Logic sees the Portenta H7 as the device to connect to and "talks" to Portenta H7 instead (booting, locking it up...).
This is so frustrating not being able to scope Portenta H7 signals with Salea Logic.
Dear Arduino Portenta H7 team: please, fix this issue. Thank you.