-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
stm32f091 debug doesn't work #785
Comments
@subsneer what you have above as device capabilities, isn't correct. Please click this icon here in device explorer window Also make sure you have installed the latest nanoff version. The version that's being reported above it's not the most recent one, neither stable nor preview. |
OK, so I check it with VS2019 now. There is device info: System Information Firmware build Info: OEM Product codes (vendor, model, SKU): 0, 0, 0 Serial Numbers (module, system): Target capabilities: AppDomains: Assemblies: Native Assemblies: I don’t know if it is OK, cause version is 1.6.4.5 but CLR Version: 1.6.4.188, but debug still doesn’t work and there is still same output: 11:26:03.020 [Starting debug engine on nanoDevice] |
Debug output and breakpoints doesn't work
nanoFramework area: Visual Studio extension
VS version: VS Community 2017 15.9.36
VS extension version: 2017.6.0.54
Target: stm32f091
Firmware image version:
Date: May 7 2021
Type: MinSizeRel build with ChibiOS v20.3.3.3
CLR Version: 1.6.4.188
Compiler: GNU ARM GCC v9.3.1
Device capabilities output:
14:10:28.363 [Starting debug engine on nanoDevice]
14:10:28.376 [Connecting to debug engine...OK]
14:10:28.562 [Assemblies to deploy:]
14:10:28.564 [Assembly: NFApp1 v1.0.0.0 (336 bytes)]
14:10:28.612 [Assembly: mscorlib v1.10.3.0 (31220 bytes)]
14:10:28.613 [Deploying 2 assemblies to device]
14:10:29.410 [Incrementally deploying assemblies to the device]
14:10:29.411 [Erasing block @ 0x0802A000...]
14:10:30.244 [Erasing block @ 0x0802A800...]
14:10:31.032 [Erasing block @ 0x0802B000...]
14:10:31.894 [Erasing block @ 0x0802B800...]
14:10:32.596 [Erasing block @ 0x0802C000...]
14:10:33.306 [Erasing block @ 0x0802C800...]
14:10:34.184 [Erasing block @ 0x0802D000...]
14:10:35.062 [Erasing block @ 0x0802D800...]
14:10:35.707 [Erasing block @ 0x0802E000...]
14:10:36.662 [Erasing block @ 0x0802E800...]
14:10:37.243 [Erasing block @ 0x0802F000...]
14:10:38.061 [Erasing block @ 0x0802F800...]
14:10:38.962 [Erasing block @ 0x08030000...]
14:10:39.769 [Erasing block @ 0x08030800...]
14:10:40.389 [Erasing block @ 0x08031000...]
14:10:41.157 [Erasing block @ 0x08031800...]
14:10:41.610 [Assemblies successfully deployed to the device]
14:10:41.981 [Attempting to connect debugger engine (1/5)]
14:10:41.981 [Assigning debug engine of target device]
14:10:41.981 [Device running nanoCLR, updating debug flags...]
14:10:42.809 [Attempting to connect debugger engine (1/5)]
14:10:42.809 [Device running nanoCLR, updating debug flags...]
14:10:43.677 [Device is running CLR, requesting reboot and pause for debugger (1/5).]
14:10:43.957 [Reboot execution succesfull.]
14:10:44.458 [Attempting to connect debugger engine (1/5)]
14:10:44.458 [Device running nanoCLR, updating debug flags...]
14:10:45.252 [Device is running the CLR in initialized state]
14:10:45.252 [The debugger engine is listening to debug events from the nanoDevice target]
14:10:46.655 [Updating information about assemblies on the debugging target.]
14:10:48.940 [Error loading assemblies. Assemblies count is 0.]
Description
I can’t get step debug working on it, Breakpoints doesn’t work as well.
I tried default empty project with Debug.WriteLine and Blinky examples and looks like deployment is OK cause led is blinking but no debug or debug output there.
There is one error at the end of .NET nanoframework extension output:
Detailed repro steps so we can see the same problem
Other suggested things
Expected behaviour
Waiting for stop at breakpoint or "Hello from nanoFramework!" in debug output
Screenshot
Additional context
I've seen same behavior with VS2019
Make an effort to fix the bug
The text was updated successfully, but these errors were encountered: