SAMD21J18A Target Support

[0Grit]

Description

I have a product running bare metal on SAMD21J18A.
Software maintenance is a nightmare and costing customer money.

I would like to propose to my customer that we port their application over to MbedOS.

I may or may not port the target to Mbed OS myself, but wanted to start by at least posting an issue.

Issue request type

[ ] Question
[x ] Enhancement
[ ] Bug

[cmonr]

@janjongboom Fyi.

@loverdeg-ep I'm not sure I follow. Is this a request for ARM to port the SAMD21 MCU to Mbed OS?

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-285

[janjongboom]

@loverdeg-ep I'm working on the SAML21J18B target (#8658), I assume it'd be relatively similar to getting the SAMD21 working. But no plans on my side to also include the SAMD21.

[0Grit]

@cmonr Sorry, my shorthand made that confusing.

I meant I would like to propose to the customer that I port their application from baremetal to Mbed OS.

Mbed OS support for SAMD21J18A would need to happen for me to make this proposal.

Request is not for anybody in particular to do so. Though I was hoping @janjongboom might already have plans for it.

I might do it myself if I can find the opportunity to review @janjongboom's other SAM ports.

[janjongboom]

@loverdeg-ep, great! I've already added some patches to add EDBG to mbed-ls so greentea tests can run, happy to share other porting details with you.

[0Grit]

If I start this effort I will obviously need to run tests locally to start.
In order to get the board into automated testing on your end, will the SAM D21 Xplained Pro board (ATSAMD21-XPRO) be a sufficient board target?

[janjongboom]

@loverdeg-ep I think so. I'm using SAML Xplained Pro, and that can run tests fine.

[ciarmcom]

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.