I have been teaching a course called EMBEDDED IOT using MBED starting about 2016 to about 500 students a year. Lately I keep seeing a RETIRING message on the MBED CLOUD COMPILER and seeing KEIL STUDIO showing up as the new default.
Since we use the FRDM-64, we use the EXPORT TO MCUXpresso option to do debugging. In fact the second course in the series, uses MCUXPresso exclusively. Also, I am sure there are a lot of developers out there the create their initial code in MBED and EXPORT it to the TOOLCHAIN that supports their deployment device for rapid development.
However, in the latest proposed scenario, KEIL STUDIO will eventually replace the CLOUD COMPILER with absolutely no way to EXPORT MCUXpresso or any other TOOLCHAIN.
Why, after all these years, are they retiring the CLOUD COMPILER, in favour of a much more limited scenario with KEIL STUDIO?
Hi David,
If I understand your workflow, you’re using the mbed online compiler to create new projects (possibly from an example?) and then doing something like right clicking on the program name, selecting “Export program” in order to export to MCUXpresso.
I think you can use the mbed-cli to do those steps.
https://os.mbed.com/docs/mbed-os/v6.15/build-tools/mbed-cli-1.html
To create a new mbed project or import one of the examples you can use the docs here.
https://os.mbed.com/docs/mbed-os/v6.15/build-tools/create.html
For me this was something like…
pip install mbed-cli
mbed new example-project
cd example-project
mbed export -i mcuxpresso -m K64F
I hope this helps.
Thank you Stevep for your response . However, when they get a working version of Keil Studio, it might be easier for the students to use the integrated debugger.
Up until a couple of weeks ago, the run and debug options for the FRDM-64F were working flawlessly for both the demo code and anything I could throw at it.
Unfortunately now, the run and debug options will not work on even the demo code for the FRDM-K64F on Keil studio.
To my mind they must have done a commit on Keil studio without completely checking things out.
|
- |
Dave Ross
Hi David,
Apologies for that bug. Recent update of debugger inside Keil Studio Cloud broke deploy and debug on few boards (including FRDM-K64F). We are deploying a fix for it. It will be released in KSC version 1.5.47. It should be live within next 2 hours.
Thanks,
Arek - Studio team
Hi David,
Keil Studio Cloud 1.5.47 has just been released. Deploy & Debug on FRDM-K64F should work correctly now.
Thanks,
Arek - Studio team
Thank you so very much. Currently I am recovering from hip surgery yesterday, so I am looking forward to rewriting my labs to use keil studio for the fall.
Dave Ross
Hi Arek,
Just started working again with KEIL STUDIO 1.5.47 and have found the same issue as described before.
Even the BLINKY project will NOT run or debug. It still generates a BIN file though.
Here are the errors I am getting for the FRDM-K64:
Hopefully this will not be hard to fix?
David Elmo Ross
Hi David,
the IDE is having problems establishing a WebUSB connection to your device.
Please make sure you don’t have the device in use elsewhere, e.g. connected in Mbed Studio or to another instance of Keil Studio in a different browser tab.
It’s always worth updating the firmware for your device, too. The K64F firmware is on https://daplink.io/
Thanks,
Rob
None of these issues seem to apply to my situation.
Dave Ross
Hello,
I do not have any target with DAP link so I do not have experiences with it, but I faced similar issue with ST-link (latest ST-link firmware ) already few times. The Issue was always solved via Full Chip Erase of STM32CubeProgrammer or ST-Link Utility, but time to time it come back again.
Please be so kind and see log below.
link Testerino.NUCLEO_L432KC
L3912W: Option 'legacyalign' is deprecated.
elf2bin Testerino.NUCLEO_L432KC
Build succeeded
Preparing to run
Parse debug description...
Create system description...
Connect to debug unit (ST-Link)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Connect ('haltOnConnect') to device STM32L432KCUx...
ERROR: Cannot open RDDI JTAG connection
ERROR: JTAG_Connect exited with code 13
ERROR: JTAG_TMS exited with code 48
ERROR: JTAG_TMS exited with code 48
: Atomic sequence error- failed to execute atomic sequence
DebugPortSetup
Item #2: <control if="protType == 2">
Item #0: <control if="isSWJ">
Item #1: <control if="!hasDormant">
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register write failed (@0x00000008)
ERROR: DP register write failed (@0x00000008)
: Debug access failed- target access failed
DebugPortStart
Item #0: <block>::Line 7
WriteDP(DP_SELECT, 0x00000000);
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: AP register read failed (@0x000000f8)
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: AP register read failed (@0x000000f8)
: Debug access failed- target access failed
DebugDeviceUnlock
CheckID
Item #0: <block>::Line 9
ROMTableBase = ReadAP(0xF8) & ~0x3;
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: Memory read failed (@0xe000ef40)
ERROR: Debug_MemRead exited with code 57
Add Flash Algorithm...
'STM32L4xx 256 KB Flash' (0x08000000 - 0x0803ffff)
Load Application...
Erase sectors...
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: Memory write failed (@0x20000000)
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: Core register write failed
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: Core register write failed
ERROR: Core register write failed
ERROR: Failed to erase flash
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: Memory write failed (@0xfffffffe)
ERROR: Memory write failed (@0xfffffffe)
Disconnect from device...
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register read failed (@0x00000004)
ERROR: Memory write failed (@0xe000edf0)
ERROR: Memory write failed (@0xe000edf0)
: Debug access failed- target access failed
DebugCoreStop
Item #0: <block>::Line 9
Write32(DHCSR_Addr, 0xA05F0000);
RDDI-DSL ERROR: ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
ERROR: Debug_RegWriteList exited with code 57
ERROR: DP register write failed (@0x00000008)
ERROR: DP register write failed (@0x00000008)
: Debug access failed- target access failed
DebugPortStop
Item #2: <control if="DoDebugPortStop">
Item #0: <block>::Line 3
WriteDP(DP_SELECT, 0x00000000);
Disconnect from debug unit...
////////// After STM32CUBEProgrammer full chip erase ////////////
Preparing to run
Parse debug description...
Create system description...
Connect to debug unit (ST-Link)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Connect ('haltOnConnect') to device STM32L432KCUx...
Reset ('auto')...
Reset completed
Device connected and halted
Add Flash Algorithm...
'STM32L4xx 256 KB Flash' (0x08000000 - 0x0803ffff)
Load Application...
Erase sectors...
Sectors erased in 1.114 seconds
Program flash...
Flash programmed in 2.289 seconds
Verify flash download...
Flash download verified in 1.22 seconds
Reset & run target...
Disconnect from device...
Disconnect from debug unit...
BR, Jan
Hi @JohnnyK, @DavidElmoRoss,
Jan are you trying with under-reset mode enabled? Most ST boards requires it. Please check in settings (Debug->Connect Mode->Under Reset).
David what operating system are you on? Is it a Windows 8.1 or Windows 10? If yes, have you installed mbed Serial Driver in the past (Windows serial configuration - Handbook | Mbed)? That driver is required only on Windows 7 and may incorrectly claim mbed devices on Windows 8.1 and 10 which breaks WebUSB support.
Thanks,
Arek - Studio team
I had Keil studio working flawlessly a several weeks back on the FRDM-K64F. There were no issues with run or debug. Then just a couple of weeks ago both the run and debug options would not work.
To me that seems that there were changes made to Keil Studio that introduced these issues since I have not changed anything at this end.
Even the BLINKY code does not run or debug.
I have been running windows 11, and Mac OS Monterrey when run and debug worked on Keil studio . And as I have said there have been no changes at this end.
Dave Ross
Its only 2 weeks since I had hip replacement surgery, so I have not been able to sit for too long at the computer
to figure things out.
The next time I got on the computer, when I restarted KEIL STUDIO the issues I seem to have been having with RUN and DEBUG have disappeared.Sorry for the trouble.
Dave Ross
Hi David,
No problem. I’m glad it works for you.
Thanks,
Arek - Studio team