Dear List, *Context:* As I am extending our projects/work from usual SAM platforms for both the SAM V71 <https://www.microchip.com/en-us/product/atsamv71q21> & E70 <https://www.microchip.com/en-us/development-tool/ma320203> (respectively Xult <https://www.microchip.com/en-us/development-tool/atsamv71-xult> & MCLV2 <https://befr.rs-online.com/web/p/power-motor-robotics-development-tools/7989578> boards) to its Radiation-Hardededned (RadHar, RH) equivalent, the SAM RH707 <https://www.microchip.com/en-us/product/samrh707> on its (very expensive) evaluation kit <https://www.microchip.com/en-us/development-tool/samrh707f18-ek> board (I have here next to me), I would like to understand from you guys if there is any room/need/willingness for converging efforts.
*Status:* Typically, I dig into your existing openocd/src/flash/nor/atsamv.c and fork it into atsamrh.c, which is now quite stable and allow to enter programming mode...but no joy so far. All I have as a starting point (not so bad...) is the dedicated RH707 flashing python script from Microchip MPLAB IDE dev. env.: this is a bit of a nightmare to run on itself, but at least the code is there to be reverse engineered in order to deduce the flashing sequence. So, nothing mature enough for a PR, but I would be already super happy to have your bless (and hints?) about the official process to get my SAM RH707 support officially covered within your beautiful (and powerful) tool. *Question/request:* nothing fancy, I believe this is a 'show me the code first' approach (fair enough), so I'll make sure to come with a patch. Gerrit being the place for the PR (if such thing) ? In the meantime, just your hints/guidelines/advice/ack would already make me super happy ! :) Sorry if this is the wrong place to ask these points: please rick-roll me to the appropriate Matrix channel (is the RTIC channel on Element the right place to discuss this as most of you guys pop-up over there ?) Thank you, Have a good one ! Cheers, Ben
