There is experimental support for Renesas parts thanks to @perigoso's #1133, we'll take their lead on how to deal with that. v1.9 is currently in a feature freeze pending release of v1.9rc1, so this will get targeted to v1.10.

that should mean the part actually got probed, it just used the brute force method as it doesn't have that id in the "database", does it not show up as an attachable target?

I don't know what WARNING: "Debug component" !match expected "Generic IP component" is about, I don't remember if it is expected, but the 0x80000000: 0x00000004000a3004 Non ARM component ignored is about the secure access on those parts and can safely be ignored provided you don't expect to debug a part with debug access locked

does it not show up as an attachable target?

(gdb) mon s
Available Targets:
No. Att Driver
 1      R7FA2A1AB3CNF    M23
(gdb) att 1
Attaching to program: /tmp/ra2a1-main/blinky/main.hex, Remote target
0xeffffffe in ?? ()
(gdb) load main.hex
Loading section .sec1, size 0xc0 lma 0x0
Load failed

ah, that means that target is probably suffering the same as #1222, you won't be able to flash the target, but you should be able to attach and debug

In the meantime, we can add the ID and close this in favor of that issue

I meant to have this closed with the addition of the ID, but that is fine, I'll PR that in a sec anyway

As per my comment on #1222, I originally did a misdiagnosis of the issue, this part uses the MF3 Flash architecture, which I did not originally implement, only the RV40, so this issue should be reopened or a new one of the likes of "Renesas MF3 Flash support" should be created @dragonmux

For reference on which part uses what flash type, see this comment

We have re-opened the issue and will modify the tittle accordingly.

@dragonmux, not a bug, enhancement i suppose?