Release an open spec to write target support
Not planned
I know that writing target support in crossworks may not be profitable for complex targets/small audiences but publishing the target DLL api may fill the gap delegating the target support development to the interested users.
For targets requiring only config parameters, a XML solution would be very nice. For really complex cases, a custom dll would be needed, provided a public target plug in api was available.
We think that the small but powerful nature of Crossworks is really nice and we would like to use in our "big ARMs" projects here too. They are currently not supported and maybe they won't ever be, but We'd like to try ourselves.
-
We would like to add support for devices which include supported cores (ARM9) but are not currently supported because of debug capabilities are missing, so We are not sure of the way to go in extending the Crossworks debugger, the JTAG link way or the device support way.
We'd like to make kernel/low level driver debug on TMS320 devices with include a JTAG router (ICEPick-C) and a ARM926EJ-S core.
It's not a new debug cable we want to support (any of currently supported should work) but it's very much JTAG link related, not a new ARM core. Afterwards, using ARM11 or Cortex Ax would be possible but the amount of work of supporting a new core currently doesn't justify the work for us, either. Getting access to the ARM9 is lot easier, we presume.
-
We have a basic CPU support for TMS320DMx - no memory map/header files and I recall that I couldn't get the part to reset and stop using the ICEPick-C. We don't have any board support so the SDRAM initialisation and flash loader will need to be written. If you raise a support request ticket I can send you the files we have. You'll need to use v2.1 - we had to make a number of changes to make CrossWorks work with the ICEPick-C.
Please sign in to leave a comment.
Comments
4 comments