I strongly encourage you to either get the examples in a state that developers can just clone them, install VGDB and get going, or create a “starter project”. I am getting “no input files” and multiple missing file errors when attempting to build libdaisy. Every time I seem to make progress I run into more issues. I have been struggling with the DaisyExamples for weeks trying to get it building in VS. I am super eager to get over the setup hump and into creating some digital instruments! If anyone has gotten VSCode set up, either with PlatformIO or not, it would be great to get that documented too. Not even sure how to get console output from the device with VSCode. I am also using VSCode to get by, but having to treat the device as a black box is… well frustrating. And then what about debugging? Does the Daisy include onboard debugging or do I need to use JTAG or similar? It would be great if you could create a guide to getting set up with VS and VGDB, given that it is probably the best toolchain out there. I looked at the repo comments and it looks like i2c support was removed but perhaps someone did not check in their config changes along with the code changes. I have set the file type prop to C/C++ Header, but no dice. It looks like it is treating that file or something it depends on as a C file rather than a C++ file (causes “unknown type name ‘namespace’” error). I keep getting build errors related to per_i2c.h. Questions: which toolchain do I use the custom one documented in “getting started”, or will the regular ARM toolchain work? None of the samples will build with either, because the libdaisy build fails. I just cloned the repo and tried to build some of the samples with VS2019 and VGDB.
0 Comments
Leave a Reply. |