Hi Pekka,
Thanks for the reply.
Yes the runtime error is via the DAPLink USB serial connection, and yes I want to use a second USB ‘Device Interface’ port for general debug serial output when my board is mounted in it’s application environment - the DAPLink port is physically inaccessible in that case…
I’ve implemented a workaround using the normal UART pins into a Serial-USB adaptor-on-a-cable but it’s also physically cumbersome & fragile. A simple USB cable would be more robust.
I’ll try your suggestion, thanks. I’m also wondering if using the latest MBedOS (5.15.1) is an issue since the data on the board says 5.4 is the latest supported version?
How do I access the API docs for an older MBedOS version like that?
Update: Compiling your linked USBCDC example with MBedOS5.15.1 gives an almost identical result:
Attempting to build with OS 5.4 (acting on my previous thought about board compatibilty) doesn’t even get past ‘go’:
Traceback (most recent call last):
File "f:\Users\Chris\Documents\Mbed Programs\Workspaces\mbed-os-test/mbed-os/tools/make.py", line 45, in <module>
from tools.options import get_default_options_parser
File "f:\Users\Chris\Documents\Mbed Programs\Workspaces\mbed-os-test\mbed-os\tools\options.py", line 21, in <module>
from tools.toolchains import TOOLCHAINS
File "f:\Users\Chris\Documents\Mbed Programs\Workspaces\mbed-os-test\mbed-os\tools\toolchains\__init__.py", line 28, in <module>
from tools.config import Config
File "f:\Users\Chris\Documents\Mbed Programs\Workspaces\mbed-os-test\mbed-os\tools\config\__init__.py", line 29, in <module>
from tools.arm_pack_manager import Cache
File "f:\Users\Chris\Documents\Mbed Programs\Workspaces\mbed-os-test\mbed-os\tools\arm_pack_manager\__init__.py", line 20, in <module>
from fuzzywuzzy import process
ImportError: No module named fuzzywuzzy