Thanks, @mbedNoobNinja .

• I tried building and faced following error happend due to missing #endif in vector_data.c. I could build it by adding #endif.

...
GEN build-VK-RA4W1/genhdr/qstr.i.last
boards/VK-RA4W1/ra_gen/vector_data.c:4: error: unterminated #if
    4 | #if VECTOR_DATA_IRQ_COUNT > 0
...

• Regarding the board directory name, @dpgeorge guided me before that "we use underscore instead of hyphen in the directory name". So it would be necessary to change it to VK_RA4W1.

Hi @TakeoTakahashi2020, I changed the name of the board, as you and @dpgeorge mentioned, and fixed the file in question vector_data.c. Following the Contributor Guidelines and more specifically the commit one, they reccomend running codeformat.py beautifier before Pull request. Which I did. It turned out, that tool damages the files which need to be altered. When it replaces tabs with spaces, if there is some spaces at the begining of the row, sometimes the content after those spaces is dropped and the code breaks at compilation stage. Most of the FSP generated files's rows begins with TABs, but some spaces appeares here and there and that obveously bugs the tool. Anyway, I somehow managed to make the both happy (compiler & codeformat.py) and now VK_RA4W1 should be compilable.

Hello @mbedNoobNinja, Thanks. I could build successfully for all boards including VK_RA4W1. I do not have this board, so did only build check.

I sometimes faced codeformat issues too and confirmed workflow result of Github Actions to investigate the detail.
Regarding bonus drivers, I condier to apply them for other boards in the future. As for FSP API utilizing, thanks for your comment described in source code.If possible, like to use, but some pin conflicts for FSP configuration.

Hello @TakeoTakahashi2020, Thank you for your time cheking the new board. If you tell me an address, I could send you 3 sample boards (VK-RA4W1, VK-RA6M3 & VK-RA6M5). My plans are to make micropython ports for the other 2, but I find difficulties making the MCU's family csv file (ra6m3_af.csv & ra6m5_af.csv) because they do not exist yet and I am unaware in what pin count & alt function variety they possess. (Sure, I probably can find that info in a specified mcu's datasheet, but it seems to me, it is alot of work, It must have an easy way) Could you enlighten me how to generate or create them? Can FSP help me and do that for me? If Yes, is it mandatory for the board to use FSP v2.3.0, because RA6M5 is not included in it yet, and should be newer than that used in the micropython (which is v2.3.0). All that will generate alot more work for all RA boards, if updating the FSP is needed only for the M5 !

Hello @mbedNoobNinja, Thank you for additional info. I will send you an email.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
        rp2:    -8 -0.002% PICO

Hello @mbedNoobNinja -San,

You can specify "VK-RA4W1" of the product name for this macro definition.

Hi @TakeoTakahashi2020 -San,
I fixed MICROPY_HW_BOARD_NAME. Should build_all_boards.sh be change in some way.

This is an automated heads-up that we've just merged a Pull Request
that removes the STATIC macro from MicroPython's C API.

See #13763

A search suggests this PR might apply the STATIC macro to some C code. If it
does, then next time you rebase the PR (or merge from master) then you should
please replace all the STATIC keywords with static.

Although this is an automated message, feel free to @-reply to me directly if
you have any questions about this.