Other Parts Discussed in Thread: C2000WARE
Tool/software:
Hello,
I have noticed, that the binaries of the USB library among the F2838x and F2837x series are inconsistent.
The binaries in the F2838xD directory seems to have been built with the "Release" and "Release EABI" configuration.
Therefore I can use it directly in my project without having to deal with the "ASSERT" or the "__error__" symbol because "ASSERT" is defined empty.
However, the F2837xD and F2837xS binaries seems to have been build with the "Debug" and "Debug EABI" configuration.
If I try to use this binary in my project, I have to deal with an error caused by an undefined __error__ symbol that is caused by the ASSERT define.
My workaround was to built the "Release EABI" configuration by myself and copied the newly generated library into my project. So I can be sure, that the ASSERT lines do not execute (unnecessary) extra code and I do not get any compiler/linker errors.
It would be nice that all distributed binaries are consistent regarding the build configuration (Release config preferred) or, like in the the C2000Ware driverlib, provide the library binaries for both configurations in different sub-directories.
Edit: I currently use C2000Ware v5.04.00.00
Regards,
Markus
