Custom BSP

Ref: r11an0132eu0101-synergy-ssp-module-development-guide.pdf

 

I want to make full use of the Export Synergy User Pack option to provide initial configuration for custom boards using custom packages.

Perhaps you could provide some clarity as to how this feature should be properly used.

I am able to create a board pack to include project files and pin configuration.

How do I include a Thread and the associated Stacks?

Regards

David

 

 

  • Export Synergy User Pack tool wen used to create a board pack only generates custom BSP packs. You can use the Export context menu to save stacks. To do that, right click on the stack and select Export.
  • In reply to Fatih:

    Interesting to know this feature exists, however it does not answer the question as to how to use a pack file to append threads and stacks to a project.
    It must be possible because Synergy uses pack files to setup the Synergy Configuration dialog which contains the primary thread. In the case of a BlinkyThread template an additional thread is added.
  • In reply to David Burch:

    Hi David,

    There are quite a few steps to go through to create a Blinky like project template. The attached zip file contains instructions and the configuration.xml file used in the example. The configuration.xml file is the tricky one to get right but hopefully the supplied one will help.

     

    Custom_Project_Pack_Creation_Eg_Blinky_Type.zip

     

    Regards,

     

    Ian.

     

  • In reply to Ian:

    Here is the complete pack file for reference. Please change the extension from .zip to .pack (changed so it could be uploaded).

     

    Ian.Renesas.Test.1.6.0.zip

  • In reply to Ian:

    Hi Ian,

    Thankyou for such a well presented reply.

    The tricky part is the ceation of the .template configuration.xml file.
    Would I be correct in thinking the relevant sections can be copied from the project configuration.xml?

    Is there a document that descibes the XML reserved word that are used in the pack files?
    Is there a document that descibes the reserved cClass, cGroup labels?

    There appear to be a couple of gemlins in the pack generation system.
    1. The Class and Group entries don't permit spaces in the label. eg 'HAL Drivers' or 'Framework Services'
    2. Some of the files path use absolute paths which prevent BSP packs being upgraded from a new project.

    Regards
    David
  • In reply to David Burch:

    The pack files used are CMSIS pack files. The CMSIS pack definition is here :-

    www.keil.com/.../index.html
  • In reply to Jeremy:

    Hi David,

    Yes, you should be able to copy the XML from the project configuration. Actually, what I did was to copy from the XML generated when creating the custom pack file.

    Regards,

    Ian.
  • In reply to Ian:

    Hi Ian,

    When I update the source file content of a pack file the project reloads the pack and updates the source files.
    However, when I update the module definition xml, although the project reloads the pack, the files are not updated.
    For example, added properties do not appear in the configurator, Includes do not appear in the .cfg files.
    The new file content only appears when I use the pack in a new project.

    Is this the intended opperation?

    Regards
    David
  • In reply to dburch:

    If you change the XML in a pack file, the new version of the XML will not overwrite the old version. You will have to manually copy the new version of the XML to the modules folder (internal\projectgen\arm\modules) under e2studio (assuming you are using e2studio v7.x)

  • In reply to Jeremy:

    Hi Jeremy

    Overwiting the XML in the modules folder dosn't appear to update the files of an existing project.

    Regards
    David
  • In reply to dburch:

    Did you close e2studio, then update the XML, then re-open e2studio?
  • In reply to Jeremy:

    Hi Jeremy,

    Restarting e2studio does work. However this is not a practical solution.

    Is there a more sensible way of developing and testing a pack file?

    Regards
    David
  • In reply to dburch:

    The other thing that might work is to close the configuration file for the project, then update the XML file in the modules folder under e2studio, then re-open the configuration. This might make e2studio re-read the XML file.

    The creation and testing of the XML for a pack file is not easy, there isn't much in the way of debugging capability. It either works or it doesn't.
  • In reply to Jeremy:

    Hi Jeremy,

    Still a bit messy but it does update the configurator.
    Generate Project Contents is required to update the files.
    Another update coming perhaps?

    Regards
    David