[JoeWright]

Thanks for the reply.  I’m not deliberately avoiding the VisualGDB toolchain, and in fact this all worked fine in my last project.  I’m just wondering if the new function of importing from STM32CubeMX is doing something strange.  I’ve ticked ‘Add necessary library files as reference in the toolchain project configuration file’ in cubemx but the project file seems to be pointing to Cubemx versions (c:\users\joe\stm32cube…) rather than visualgdb.

When I added the stm32f3cube hal it created a lot of conflicts.  So it would appear that cubemx is producing references differently than in previous projects?  I’ve copied to the cubemx project file from before so have only made minimal changes.  Not sure why things are behaving differently.  I can only see the new import option as a change from before.

[Author]

Posts