Apr 22, 2014
05:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 22, 2014
05:26 AM
4 Replies
Apr 22, 2014
12:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 22, 2014
12:30 PM
Sorry currently not, we only keep, legacy versions of DAVE Apps downloadable. Which DAVE version you are looking for and why you don’t want to use the latest version?
Apr 24, 2014
12:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 24, 2014
12:28 PM
Thanks for your replay. To answer your question: let's suppose you did a project some time ago with older DAvE version, and now you need to do minomal change (e.g. like one pin setting, etc..), shall I have to migrate to new DAvE and take the risk or simply reinstall the older DAvE version and just operate the desired change?
Apr 27, 2014
02:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 27, 2014
02:09 PM
So, the use case is as follows: The code generated with an older version of DAVE shall be re-generated (no new DAVE Apps) with the same old DAVE version, whereas this old DAVE version is not available any more. In this case (code generation should be exactly as before) it is not enough to only re-install the old DAVE version is also required that the original version of the device description has to be present in the used local library store. If it is allowed to use a new version of the device description then also the newer version of DAVE can be used without migration, just import the old project in a new DAVE version, and do the required reconfigurations and then re-generate the code (because the used DAVE Apps are part of the project, the same templates will be bused for code generation).
For building it is a bit different: Per default the CMSIS core and device header files are not part of the project but used from the CMSIS folder DAVE installation. The same for the used GCC version, a new DAVE version may contain a new GCC version. If it should be avoided that a newer header file and compiler version are used to rebuild the project then indeed the older DAVE version is required.
Currently we don’t have a ready setup to provide a full set of legacy versions of DAVE, DAVE Apps and Device description, but we will take this request to look for a solution (a solution for DAVE Apps is already available). We will also create a document that describes all dependencies to freeze a project along with code generation and re-build.
For building it is a bit different: Per default the CMSIS core and device header files are not part of the project but used from the CMSIS folder DAVE installation. The same for the used GCC version, a new DAVE version may contain a new GCC version. If it should be avoided that a newer header file and compiler version are used to rebuild the project then indeed the older DAVE version is required.
Currently we don’t have a ready setup to provide a full set of legacy versions of DAVE, DAVE Apps and Device description, but we will take this request to look for a solution (a solution for DAVE Apps is already available). We will also create a document that describes all dependencies to freeze a project along with code generation and re-build.
Apr 28, 2014
03:10 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 28, 2014
03:10 PM
Many Thanks!