We've been using the now-outdated STM32L476 Discovery boards for a while, to teach a basic course in embedded devices. We just switch to the STM32L496 Discovery board, and have not been successful in getting it to work with uVision.
We set up the software packs & built a project easily. We compiled no problem, and flashed successfully from uVision.
When we try to run, however (Debug => Start/Stop Debug Session), trouble starts. Namely, all of the menu items to actually run anything (run, step, step over, etc) are all greyed out.
Any idea what would cause uVision to do this? If it helps, we're using Keil uVision 5.38.00.
Thanks,
/Joel
Do you also face this outcome when debugging one of the STM32L476 example projects offered by the Pack Installer?
If yes:
- To what folder is Keil MDK installed?
- What is the Debug Adapter in use?
Related:
"UVISION: Reset View To Customer Defaults"
https://developer.arm.com/documentation/ka004091/latest/
> Do you also face this outcome when debugging one of the STM32L476 example projects offered by the Pack Installer?
Do you mean STM32L496 example projects? Why would I run an STM32L476 project on an STM32L496 discovery board? Even a simple LED blinky project shouldn't work, since the LEDs are wired to different GPIO pins in each board.
> To what folder is Keil MDK installed?
C:\Keil_v5
> What is the Debug Adapter in use?
ST-LINK/V2-1, via SW port.
Another piece of data: I had somebody try out the project under PlatformIO rather than uVision yesterday, and it came right up. So our boards seem fine and the project code works. Presumably there's something in our uVision setup that worked fine for the 476 Discovery boards but not for the 496 Discovery boards. But since uVision isn't giving me any clue other than the greyed-out menus, I'm not sure how to debug what the issue is.
Sure, you can also run the STM32L496 examples offered, like the CMSIS-RTOS2 Blinky. This is most of all about the resulting menus.
OK, CMSIS-RTOS2 Blinky runs fine on the 496 Discovery Board:-).
I compared the Options for Target between the Blinky example and my project. The glaring differences are in the Target / Read-Write Memory areas. Would that cause the "run" menu items to be grayed out?
After discussing this status with our Team, one idea is that the Debug Adapter is not configured correctly.
However, a closer investigation requires to see your project. If you possess a valid license key (mandatory), open a corresponding Support Ticket please: https://www.arm.com/support/contact-support