Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
8 years, 1 month ago.
NXP Freedom boards macro
Since the question button on the blog is non-functional, this way:
Now all Freescale boards are going to be renamed to NXP, will this also happen in the mbed library? So that is related to the TARGET_Freescale/TARGET_NXP macros which are used in some libraries.
Be the first to answer this question.
I think there is an effort to consolidate on KSDK 2.0. Guessing this is using TARGET_Freescale for now but could be TARGET_NXP
posted by Sam Grove 15 Mar 2016Erik, how would a library use TARGET_FREESCALE or NXP or any other vendor name?
posted by Martin Kojtal 15 Mar 2016Random one, like this: https://developer.mbed.org/users/Sissors/code/FreescaleIAP/file/6749f7702fa5/FreescaleIAP.h (scroll down a bit). But IIRC also for example FastIO uses it. So everything which uses peripherals that are equal for all devices.
posted by Erik - 16 Mar 2016Most of the time it would be family of devices like Kinetis, STM32F4.. I can see how it is used in your library. As Sam pointed out, KSDK 2.0 is coming, and might solve this problem or we just get to it and have to find an answer.
posted by Martin Kojtal 16 Mar 2016A new version of KSDK solving issues, thats a funny one :D. Probably breaks everything since they decided their function names and arguments needed to be slightly different. I even doubt it is possible for quite some peripherals since they are simply too different. (For example NXP ADCs can automatically convert multiple channels while Freescale ones can only do a single one).
In the end the request is to simply set the TARGET_Freescale macro in the targets.py if it is gonna change :).
posted by Erik - 16 Mar 2016