Forum Replies Created
-
AuthorPosts
-
jonaSpectator
OK.. this is a little weird! I loaded a project that is a couple months old and the Mem Explorer worked. Oddly, I also noticed that the “Visual GDB Project Properties ” was back under the Project Menu. I did not change any settings.
So I loaded my current project back in and built it and I can see the Memory Explorer again. I checked the build of VGDB and it is 5.4R3 (build 3000).
I’m good to go now but I thought I should pass this along.
Thanks.
jonaSpectatorThe project is fine, still building and running as it was before yesterday’s upgrade. Which settings in particular might affect this?
jonaSpectatorI submitted a support ticket before I found it.. don’t know how to close that from here.
jonaSpectatorFOUND IT! Sorry!
jonaSpectatorOr more accurately .. the project settings, I think? Used to be under project but it is gone..
jonaSpectatorTHAT. is. cool. Thanks!
jonaSpectatorStill learning while I create this product.. did not know that about the ARM instruction set.
So that means that no matter what you have selected in the build settings it will always be thumb 1?
I guess that settles that! But I guess there is Thumb 1 and Thumb 2? Will that distinction be available in VGDB?
Thanks again!
jonaSpectatorI wish I could. VS restarts and then puts up the yellow prompt at the top notifying me that I should disable VGDB.
jonaSpectatorI’m having this same problem a lot lately in VS2017. Any ideas how to solve it permanently? Is it a VS bug that we just have to deal with?
jonaSpectatorThank you for your reply. I have to tell you. Very few of these examples actually run properly on the STM32F7. For someone rushing to get up to speed on this platform it is extremely difficult.
jonaSpectatorI am not sure that file contains the proper _sbrk() routine though. This is something I am trying to understand as I go through these examples and was the root of one of my questions earlier.
jonaSpectatorNew Project -> Embedded Project Wizard -> New Embedded Project ->Sample Selection…..
jonaSpectatorthanks!
Every example that attempts to write to the LCD via LCD_LOG_PUTCHAR ( int __io_putchar(int ch)) needs syscalls.c (I am using the one from the STM32Cube_FW sources) syscalls.c is a ” System Workbench Minimal System calls file”
Perhaps someone here knows which file these examples should be using.
jonaSpectatorUpdating the framework yielded the controls.
Thank you
jonaSpectatorI don’t see any controls in the Embedded Frameworks page of the project properties.
I have buffer size, printf(0 redirect and what to do when out of buffer space.
And the profiler controls .. but nothing else.. please advise.
-
AuthorPosts