[mbedmicro/pyOCD] Target Support EFM32 (#280)
Friedrich Mäckle
What are the steps to support a new platform? We do have several boards here and some are supported by pcOCD, some are not.
E.g. our EFM32 boards by Silicon labs are not supported.
How much effort is it to add support for this platform? How could one provide the support?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
moyoumos
+1
Friedrich Mäckle
@c1728p9 Do you know if there is any progress on this? Now 1.5 years later we are taking a next look at mbed os debugging with DAP-Link, but as it seems it is the same as when I left of.
Russ Butler
@flit can you provide any information on when pack targets will be supported?
Chris Reed
Hi @pfried, we typically rely on silicon partners and community members to add support for new targets. For broader target support, we are going to be moving to a CMSIS-Pack based configuration system (in addition to the existing built-in targets). The issue tracking this is #357. The goal is to have this completed by March 2019 (work has started).
Friedrich Mäckle
I think we will wait for a pack support. For our current development we "solved" this issue by using the Segger J-Link Server for gdb debugging.
Chris Reed
Fyi, version 0.16.0 added pack support. You can download a pack from http://www.keil.com/dd2/pack/ and use the --pack command line argument to make the devices it defines available to pyOCD.
James Churchill
Can confirm this works with the EFM32G pack downloaded from https://developer.arm.com/embedded/cmsis/cmsis-packs.
Chris Reed
Excellent, thanks for reporting your success!
Chris Reed
Closing this issue since EFM32 targets are now supported via CMSIS-Packs.
With version 0.19.0, you can now add EFM32 support just by running pyocd pack -i efm32. That will install quite a few packs, so you probably want to be more specific about the part number.