Sysprogs forums › Forums › VisualGDB › Unexpected endianess
Tagged: visualgdb stm32
- This topic has 3 replies, 2 voices, and was last updated 1 year, 7 months ago by support.
-
AuthorPosts
-
April 8, 2023 at 04:26 #34097arcaneParticipant
Hello,
I’m trying to understand where this error message is from ”unexpected endianess error: flag 104”. This occurs when im trying to flash my STM processor
I have not added anything else besides ST drivers to my VisualGDB project. Everything is from the base generation of building the project from a .ioc file
Any debugging ideas?
April 8, 2023 at 09:07 #34098supportKeymasterUnfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch. See this page for more information and detailed examples.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.
April 9, 2023 at 08:33 #34099arcaneParticipantSolved it, apparently I had tinkered with the VisualGDB Project properties when looking through my git logs I found the problem. The makefile settings was set to a static library, once changed back to Executable it worked.
A little too hasty on the forum post from my side, thanks for the debugging assistance on looking thru the projects source control and settings.
April 9, 2023 at 12:51 #34102supportKeymasterHi,
Good to know it works. Using git, or taking brief notes of the settings you change, could indeed save lots of time tracking down such issues.
-
AuthorPosts
- You must be logged in to reply to this topic.