NUCLEO_F401RE on VS Codium HELP

[CubikingChill]

I currently have difficulties flashing the hello world example project onto my NUCLEO_F401RE. I am currently using the insider version of VS Codium, and PYOCD as upload method. The current state of my project is that I have 0 problem building the .elf using the "All" target. But "flash-" doesn't work.

Here's the output when I try to flash-{MyProject}:

[main] Configuring project: MyProject
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" -DCMAKE_BUILD_TYPE:STRING=Develop -DMBED_TARGET:STRING=NUCLEO_F401RE -DUPLOAD_METHOD:STRING=PYOCD -DPYOCD_UPLOAD_ENABLED:BOOL=TRUE -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE --no-warn-unused-cli -S "C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject" -B "c:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop" -G Ninja
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Mbed: Target does not have any upload method configuration. 'make flash-' commands will not be available unless configured by the upper-level project.
[cmake] -- Mbed: Not building any Mbed OS tests.
[cmake] -- Mbed: Code upload and debugging enabled via upload method PYOCD
[cmake] -- Mbed: Detected VS Code IDE, will generate VS Code debug configurations
[cmake] -- Configuring done (4.5s)
[cmake] CMake Warning in mbed-os/connectivity/nanostack/sal-stack-nanostack/CMakeLists.txt:
[cmake] The object file directory
[cmake]
[cmake] C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop/mbed-os/connectivity/nanostack/sal-stack-nanostack/CMakeFiles/mbed-nanostack-sal_stack.dir/./
[cmake]
[cmake] has 203 characters. The maximum full path to an object file is 250
[cmake] characters (see CMAKE_OBJECT_PATH_MAX). Object file
[cmake]
[cmake] source/Service_Libs/mle_service/mle_service_interface.c.obj
[cmake]
[cmake] cannot be safely placed under this directory. The build may not work
[cmake] correctly.
[cmake]
[cmake]
[cmake] CMake Warning in mbed-os/connectivity/libraries/nanostack-libservice/CMakeLists.txt:
[cmake] The object file directory
[cmake]
[cmake] C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop/mbed-os/connectivity/libraries/nanostack-libservice/CMakeFiles/mbed-nanostack-libservice.dir/./
[cmake]
[cmake] has 205 characters. The maximum full path to an object file is 250
[cmake] characters (see CMAKE_OBJECT_PATH_MAX). Object file
[cmake]
[cmake] source/nsdynmemtracker/nsdynmem_tracker_lib.c.obj
[cmake]
[cmake] cannot be safely placed under this directory. The build may not work
[cmake] correctly.
[cmake]
[cmake]
[cmake] -- Generating done (3.3s)
[cmake] -- Build files have been written to: C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop
[main] Building folder: c:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop flash-MyProject, MyProject
[build] Starting build
[proc] Executing command: chcp
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --build "c:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop" --config Develop --target flash-MyProject MyProject --
[build] [1/1 0% :: 0.267] Flashing MyProject with pyOCD...
[build] usage: main.py load [-h] [-v] [-q] [-L LOGGERS=LEVEL]
[build] [--color [{always,auto,never}]] [-j PATH]
[build] [--config PATH] [--no-config] [--script PATH]
[build] [-O OPTION=VALUE] [-da DAPARG [DAPARG ...]]
[build] [--pack PATH] [--cbuild-run PATH] [-u UNIQUE_ID]
[build] [-t TARGET] [-f FREQUENCY] [-W] [-M MODE]
[build] [-e {auto,chip,sector}] [-a ADDR] [--trust-crc]
[build] [--format {bin,hex,elf}] [--skip BYTES] [--no-reset]
[build] [ ...]
[build] main.py load: error: argument -f/--frequency: expected one argument
[build] FAILED: [code=2] CMakeFiles/flash-MyProject C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop/CMakeFiles/flash-MyProject
[build] C:\WINDOWS\system32\cmd.exe /C "cd /D "C:\Users\Yuk\OneDrive - The University of Manchester\Documents\ESP12\MyProject\build\YOUR_MBED_TARGET-Develop" && "C:\Users\Yuk\OneDrive - The University of Manchester\Documents\ESP12\MyProject\mbed-os\venv\Scripts\python.exe" -m pyocd flash -v --no-wait -f -t --base-address 0x8000000 "C:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop/MyProject.bin""
[build] ninja: build stopped: subcommand failed.
[proc] The command: "C:\Program Files\CMake\bin\cmake.EXE" --build "c:/Users/Yuk/OneDrive - The University of Manchester/Documents/ESP12/MyProject/build/YOUR_MBED_TARGET-Develop" --config Develop --target flash-MyProject MyProject -- exited with code: 2
[driver] Build completed: 00:00:01.837
[build] Build finished with exit code 2

Below is the lineI want to talk about:

[cmake] -- Mbed: Target does not have any upload method configuration. 'make flash-' commands will not be available unless configured by the upper-level project.

Initially I don't know why as I have already include the upload method in cmake-variants.yaml

buildType:
default: Develop
choices:
Develop:
short: Develop
long: Emit debug information but also optimize
buildType: Develop
Debug:
short: Debug
long: Emit debug information and don't optimize
buildType: Debug
Release:
short: Release
long: Optimize generated code
buildType: Release
board:

Fill name of your targer which has to corespond to

target name in targets.json5 file or custom_targets.json5 in case of custom target.

For simplified just replace every occurrence of YOUR_MBED_TARGET with Mbed target name.

For example LPC1768 or NUCLEO_L452RE_P

default: NUCLEO_F401RE # default variant (choose) from below
choices:
YOUR_MBED_TARGET: # Name of one variant
short: NUCLEO_F401RE # Short name of the variant
settings:
MBED_TARGET: NUCLEO_F401RE # Your mbed target name from targets.json5 file
# Fill your upload method according to variants below
# - universal: NONE, MBED, JLINK, PYOCD, OPENOCD
# - target specific: STLINK, STM32CUBE, LINKSERVER, PICOTOOL, ARDUINO_BOSSAC
# For more visit - https://github.com/mbed-ce/mbed-os/wiki/Upload-Methods#upload-method-list
UPLOAD_METHOD: PYOCD
PYOCD_UPLOAD_ENABLED: true

[wdx04]

Currently there is no upload method config file for NUCLEO_F401RE. You may create a 'NUCLEO_F401RE.cmake' inside the 'mbed-os\targets\upload_method_cfg' folder. This file should be very similar to the existing 'NUCLEO_F446RE.cmake', except for the different chip model name.

Or you can enable upload methods in your app's CMakeLists.txt:

set(MBED_UPLOAD_ENABLED TRUE)
set(PYOCD_UPLOAD_ENABLED TRUE)
set(PYOCD_TARGET_NAME STM32F401RETx)
set(PYOCD_CLOCK_SPEED 4000k)
set(STM32CUBE_UPLOAD_ENABLED TRUE)
if ("${STM32CUBE_CONNECT_COMMAND}" STREQUAL "")
  set(STM32CUBE_CONNECT_COMMAND -c port=SWD mode=UR)
  set(STM32CUBE_GDBSERVER_ARGS -d -k)
endif()

[CubikingChill]

Thank you so much.

Just wondering, why there is no upload method config file, if the files are similar across similer hardwares.

[wdx04]

I think the upload method config file will only be added when the developers of this project have actually tested on the board.

[JohnK1987]

Solved in #506