Renesas-BSP V6.4.0

[tim]

Hi,

 

the Renesas-BSP seems to be a bit outdated.
I need Controller-Support for Targets “R7FA0E3″and “R7FA4L1”.

The Renesas BSP packages differ significantly from VGDB-BSP.

in “com.sysprogs.arm.renesas” is a DeviceDefinitions-Folder with one <devicename.xml> each.

Renesas offers Zip-Packages with Device informations, linker script etc.

e.g.
“Renesas.RA_board_ra0e3_fpb.6.4.0.pack”
“Renesas.RA_mcu_ra4l1.6.4.0.pack”

Is there a easy way to import these packages to VGDB?
Is there a possibility to import the packages mentioned above by hand?
Is there a timeline from sysprog to update renesas to version 6.4.0?

Kind regard
Thomas

 

 

 

• This topic was modified 2 months, 3 weeks ago by tim.

[support]

It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey

[tim]

OK understand…

We renew the Licence today and Sysprog provide the “Renesas “R7FA0E3″and “R7FA4L1” Target.
Deal? 🙂

Sincerly
Thomas Timme

• This reply was modified 2 months, 1 week ago by tim.

[support]

Hi,

Sure, feel free to renew, and we will rebuild the Renesas BSP based on the latest packs.

[tim]

Hi, sorry for my late reply…
We have updated our Licence

As stated above: the RA4L1-Package is important to us.

Kind regards
Thomas

[support]

Thanks for renewing your license.

We have looked into the new Renesas BSP and there is a major change in it. Renesas switched from shipping pre-generated linker scripts and header files to generating them during project initialization.

We are currently looking into creating a workflow similar to the Advanced STM32CubeMX Projects, that will use the VisualGDB’s project framework on top of the Renesas low-level tools for managing the project configuration.

We will post an update here once we have a preview. As a temporary workaround, you can try creating a project with the Renesas VS Code Extension, and importing it into VisualGDB. The new advanced project workflow will use a similar approach with some additional usability layer on top of it.

[tim]

as I statetd above “The Renesas BSP packages differ significantly from VGDB-BSP.” 🙂

OK, thanks for the Update.
I will try your suggested workaround with VS Code.

Sincerly
Thomas

[support]

OK, we got it working: VisualGDB-6.2.0.5606.msi

You can now create projects using the Renesas Smart Configurators by selecting “Smart Configurators” in the Embedded Project Wizard:

You can use 2 layouts:

• Without Sysprogs Embedded Framework, it will fully match the VS Code layout (device settings + project settings all defined together). The project will be 100% interoperable with VS Code.
• With Sysprogs Embedded Framework, the main CMakeLists.txt will look much smaller, and will support multiple executables (e.g. main + unit test + static libraries). But, using it without VisualGDB would require manually deploying our embedded framework.

You can also switch a project from the compatible layout to the Sysprogs Embedded Framework via context menu:

For both options, you can launch the Renesas configurator via VisualGDB Project Properties.

Attachments:

You must be logged in to view attached files.

[tim]

thanks a lot.
will test it (and report)

kind regards
Thomas

 

[Author]

Posts