[ThomVisGdb04]

Yes, thanks, this build worked!  (using ncs 1.9.1 for nRF52840 –  it even offered the latest ncs 2.0.0, will test that sometime later).

[ThomVisGdb04]

Hi

Thanks for the valuable tips, I will try them out in the next days, once I have the priority back to this platform.

[ThomVisGdb04]

Indeed, editing the toolchain.xml and renaming the folder in ToolchainProfiles / localhost did work, correct versions are shown now and applied to projects.

Now, another point was with the newlib-nano not been offered by the New Project wizard, I had to copy some  missing parts like

<ConfigurableProperties>

from your official toolchain.xml to my new toolchain.xml  (which was generated by VisualGDB using the ‘Locate toolchain’ menu).
But now I think I have a working setup with this latest GCC toolchain.

Thanks for all your support.

 

[ThomVisGdb04]

Hi support,

Thanks for your answer.
Good hint, but the result (now using your 5.4R5) is only fine for the first part of GCC version (here 8.2.1), but for the GDB part the version is a crippled string:
‘GDB (GNU’
see attached screenshot.
Even worse, also the files stm32.xml

<ToolchainVersion>
<GCC>8.2.1</GCC>
<GDB>(GNU</GDB>
<Revision>0</Revision>
</ToolchainVersion>

and  *.vcxproj

<ToolchainVersion>8.2.1/(GNU/r0</ToolchainVersion>

are affected, putting a high risk of breaking version checking, sooner or later.

I see *GCC.exe has a nice    -dumpversion  parameter providing just the plain version string like  ‘8.2.1’ .
But for *GDB.exe, the –version call print is chatty,
for your built-in toolchain:
GNU gdb (GDB) 8.0.1
latest arm-GCC package:
GNU gdb (GNU Tools for Arm Embedded Processors 8-2018-q4-major) 8.2.50.20181213-git
Thus some smart parsing logic would be required..

Unfortunately, my first plan to manually modify FindToolchain.props  seems no solution, as the file later got overwritten by VisualGDB.

Thanks for any help.

 

 

 

Attachments:

You must be logged in to view attached files.

[Author]

Posts