Hi,
Thanks for pointing this out. The Renesas devices are quite different from other device families supported by VisualGDB. They extensively rely on fairly complex code generation logic (that uses JavaScript in some cases). VisualGDB does not include a JavaScript engine and cannot replicate the original logic with 100% accuracy, however it still supports a reasonable subset of it that can still save time, while requiring occasional manual adjustments.
In this case, the incorrect syntax comes from the following line in the BSP.XML file:
<string>#define BSP_CFG_ROM_REG_BPS0 (~($$config.bsp.fsp.BPS.BPS0$$ 0U))</string>
You can work around it by patching the file as follows:
<string>#define BSP_CFG_ROM_REG_BPS0 (~($$config.bsp.fsp.BPS.BPS0$$))</string>
You can then set BPS0 to 0 via the project properties (or just hardcode 0 in the template instead of $$config.bsp.fsp.BPS.BPS0$$).
We have noted this in our roadmap for the Renesas BSP, and will look further into it when releasing the next BSP version.