- This topic has 3 replies, 2 voices, and was last updated 9 years, 1 month ago by
.
-
Posts
-
Can someone experienced visualgdb user look that https://github.com/rad1o/f1rmware/ and estimate that is it doable to get that project work with visualGDB? I already start configure toolchain settings but looks that with my experience it will be more try and error basis. So I think that is better to check that it is even possible to get it work before I use week or two to hit my head to wall 🙂
Hi,
It’s hard to answer that question from just looking at the project source page. What hardware is the project targeting? What toolchain is it using?
Hardware is rad1o. It based for hackrf. More info at https://rad1o.badge.events.ccc.de/hardware
About toolchain. Makefile.inc give some kind answer for that. I dont have better answer for that because I am really noob with cross compile.  Direct link for that https://github.com/rad1o/f1rmware/blob/master/Makefile.inc and looks that it is unusual distinct. So it can (or not) give good answer for more experienced person.
Hi,
Yes, the Makefile looks like it can be built with VisualGDB. Simply install our ARM toolchain, add it to PATH and replace arm-none-eabi- with arm-eabi- in your Makefile so that it matches the arm-eabi-gcc.exe executable. However if the project is made to be built on Linux, it might rely on other Linux tools and simply not build under Windows. In that case we would suggest getting a Linux cross-toolchain, getting it to build on a Linux VM and then importing it into Visual Studio as described in this tutorial.
Either way, VisualGDB is flexible enough to build/debug any project that can be built using command-line tools, so you should be able to develop it with Visual Studio and VisualGDB even if it needs to be built remotely under Linux. If you encounter strange error messages, feel free to post them here so that we could try to help you.
- You must be logged in to reply to this topic.