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.
9 years, 2 months ago.
'mbed enabled' prerequisites?
I'm trying to figure out what it takes to 'mbed enable' a board we're going to design soon.
Obviously, I'll need to add a USB interface by including a Debug Unit (ARM's term for a small support-MCU sitting between the USB and target's SWD/JTAG interface) to facilitate the HID endpoint.
Freescale offers their OpenSDA for this purpose. NXP offers LPC-Link2/LPCXpresso thing. Segger chimes in with the J-Link. And ARM has CMSIS-DAP to show.
Now, I've found that the HDK sports a CMSIS-DAP firmware: http://developer.mbed.org/handbook/cmsis-dap-interface-firmware This leads me to believe CMSIS-DAP compliance is part of the requirement for 'mbed enabled'-enabling our board.
But that's not enough, right? Some sort of BSP/library-thing defining available ressources like IO, onboard devices and so on must also be made...
A pointer to info regarding this process would be most welcome - I don't seem to be able to locate it myself.
To get started right now, would I be able to take one of the many non-'mbed enabled' evalkits out there and define the BSP, so it can be used directly? As long as the board offers a CMSIS-DAP compliant USB-interface, hardware side of things should be okey-dokey. Right?
2 Answers
8 years, 4 months ago.
i am a beginner to mbed platform, so if you could explain precisely how a ARM-cortex M4 processor based IoT platform can be made mbed compatible.
precisely is a big request. mbed is creating 'Mbed 3.0' for the IoT field. Last I checked they had 3 platforms that they were getting ready for the mbed IoT ecosystem. So it is not very defined (precisely) at this point in time. It is also known as Mbed OS, search google for that to give you an idea !! Gary
posted by 12 Dec 2015
9 years, 2 months ago.
I pointed to some sources where you commented also, https://developer.mbed.org/questions/6508/mbed-on-Texas-Instruments-C3200-platform/
As I understand mbed-enabled - interface chip provides usb virtual disc, COM port and CMSIS-DAP debugger (-these 3 are covered by mbed cmsis-dap, sources available on github https://github.com/mbedmicro/CMSIS-DAP), SDK port (HAL and cmsis) (sources available on github https://github.com/mbedmicro/mbed), tested using testing tools, means once adding a new platform, the test report is part of the pull request (workspace_tools in the mbed SDK).
Start with mbed SDK github, clone it, try to build mbed library for a board, run a simple test for a targe which is currently supported.