[whinis]

Oh I see why I missed it now, I saw the tab to switch to arm semi-hosting for a second and then it disappeared again which is whenever I noticed the dropdown arrow to the side. Otherwise I only see this at the top of the output window

So I thought that semi-hosting window had just disappeared.

[whinis]

My Issue is, I don’t see semihosting output or semihosting console here
Windows Menu” width=”303″ height=”673″ />

[whinis]

Thanks support, my current big issue with the current Atmel START framework is that it includes the config and driver_init files in the framework preventing its use in anything except the atmel start project it was created with. Furthermore if you change that atmel start project or try another one it overwrites the previous one invalidating that project. This is why I attempted to change what I did, under your current system your only choice is to import the project and then convert it to a standalone which seems to defeat the purpose of a framework in the first place.

[whinis]

crj11

I pushed the changes I made to https://github.com/whinis/BSPTools as well as a MCUList csv that contains all the MCUs it should technically work with as well as my custom BSP.
This includes changes I needed to make to have it generate a “generic” BSP and I make no claims this is the best way of doing it

How it works is you make an AtmelStart package with as many libraries as you can and extract it to a folder
Move the BSP.XML from BSPTools/SDKImporters/AtmelStartSDKImporter into that directory
Build the AtmelStartSDKImporter and debug it with the directory of your AtmelStart as its command line argument
It will generate a vgdbxbsp that you can import as a package. I have made it such that you can then make any new atmelstart package and just copy over the Config directory into your new project for everything to work.

To Sysprog I recommend you update your AtmelStartSDK importer to make a similar package because the biggest issue is 99% of the code and the library stays the same however a few files change for every project and your current package includes them as part of the library. I recommend you use my BSP as a starting point but not the ending point because its a bit hackish and I was fumbling my way through it.

PS. I would distribute the package but im not sure thats allowed.

• This reply was modified 3 years, 7 months ago by whinis.
• This reply was modified 3 years, 7 months ago by whinis.

[whinis]

I decided to play around with the BSPs and modified the tools you have at https://github.com/sysprogs/BSPTools to generate one that doesn’t reference the config files but copies them over instead allowing one to overwrite them easily. The same with all of the start files that are changing between different chips. I had difficulty getting VisualGDB to recognize the changes if I made a new folder so I also had to modify the script to produce a proper vgdbxbsp file as the atmel start generator only produces the xml.

[Author]

Posts