I was attempting to set up the discovery board I have to run stand alone. Went to “Generate Target Files” and decided to click every checkbox. Hangs on <project>full.h.
My project is real simple, just pass 2 channels of audio through with no external controls or tuning.
Any idea why this happens?
Thanks for getting back to me.
I’m using the STM32F746G, and GCC (and System Workbench).
I am getting a TargetInfo.h and the AWB .c and .h files. From the manual, I think I understand how to load the DSP ‘engine’. I was mostly wondering if there was more that would be generated, or if my example may have been overly simple.
From my poking around, I don’t see other way for the Designer to generate the <project>full.h file…
So, from what I gather, the <project>full.h file is no longer supposed to be generated. However, all I can get created is <project>_TargetInfo.h, <project>AWB.c, and <project>AWB.h. These seem sufficient to get the project off the PC and onto the target device. I may need to dig further into the Fine Manual (and let me know if that is the case), but is this enough to get the project actually running on the target?
I am able to reproduce your issue when the 'TSF' option is selected in the Generate Target Files tool in the 6.17.05 edition of Designer, but the issue is fixed in 6.17.06, which will be released today or tomorrow on our website.
The <project>full.h file is not required to get your project running on your target. A <project>.tsf file is created when you select the TSF (Tuning Symbol File), and that file is used to convert the ObjectIDs in your AWB into symbols that are understood by the Server and upstream tools, so that you can perform tuning steps on a running target.
I hope this helps,
Thanks for confirming this. Look forward to the update.
Just grabbed and tried 6.17.06 and I get the same behavior. Simplified the project down to connecting the deinterleave straight into the interleave.
I apologize, I originally tested with the full Pro version of 6.17.06, not the Standard version. I do also see this error with Standard, even in the new edition of Designer.
The problem turns out to be that a certain template file needed to create the .tsf file is not available in the Standard edition. This will be remedied in the next release of Designer.
Any idea when we might see this?
We don't have a release date yet, but it is likely that we create one more release by the end of the year.