Actions
Forum Thread Details
  • Replies 27 replies
  • Subscribers 33 subscribers
  • Views 6892 views
  • Users 0 members are here
Related

PSoC 5LP Programmer Firmware

cy.wbz

Hello!

 

Today I would like to post an extra project for you guys. Attached to this post is the firmware for the PSoC 5LP device on the Pioneer kit. If you are designing a board and need a programmer and debugger for the board feel free to copy the PSoC 5LP layout on the Pioneer board and use this firmware to enable programming and debugging. The layout files are on the Cypress Pioneer Kit web page:

 

www.cypress.com/cy8ckit-042

 

This will allow you interface your custom board with our PSoC Creator and PSoC Programmer development tools.

 

In the example attached we have two projects, the source code for the PSoC 5LP and a base bootloadable project. To build the project you will need to perform the following actions:

 

1. Make the project KitProg_Bootloader active and build it first.

2. Open the KitProg project TopDesign.

3. Doube click the bootloadable component to open the bootloadable configuration.

4. Select the tab 'dependencies' and select the browse button.

5. Browse to the folder where the KitProg Bootloader.hex file is generated and select this file. Click Ok.

 

Good Luck!

Matt

Attachments:
KitProg version 2_03.zip

  • Hi Matthew~

    Could you describe the process in detail? I don;t understand something there.image

  • Is there a changelog available? There were mentions of some issues, and I want to know whether to update or not...

     

    Thanks,

     

    hli

  • First, thanks Matthew for pointing me to this - just what I was looking for.

     

    Anyone having any luck building this in Creator 3.0? I loaded the workspace and let it update the components when offered. Then I built the bootloader project, set the paths in the KitProg bootloader component and tried to build the KitProg project. This gave the following error:

     

    sdb.M0013:Extra schematic terminal that does not appear in symbol: (sof).

     

    This is connected to the "sof_int" pin on the USB component on USBFS_v2_51.cysch.

  • in reply to Former Member

    John,

     

    try this:

     

    1. When openeing the project in Creator 3.0, select the option to update all your components to the latest version.

    2. Ensure you have set the correct dependencies for the bootloadable project as described in Matt's 1st post

     

    let us know if that helps!

  • in reply to cy.gul

    Gagan,

     

    I thought I had done all that (as described in my OP). Can I be impertinent and ask if you have actually tried compiling this in Creator 3.0 yet? I did some more testing and it looks to me that there are some fundamental problems.

     

    I was getting very confused between the two projects, so I unpacked a new copy and this time on opening the workspace I cancelled out of the component update, removed the "KitProg" project and manually invoked "component update" on the "KitProg_Bootloader" project. During this the "sof" error message appeared. Exploring the "components" tab, I find a USBFS_v2_51 component (in addition to TopDesign). I assume this is redundant because the USBFS component has updated to v2_60, so I remove it. Now the "sof" error message disappears.

     

    However on building I still get four errors:

     

    image

    I've tried to bottom this out, but there is a tangle of compatability macros that I've not yet been able to fathom.

     

    - John

  • in reply to Former Member

    Hi John,

    Thanks for the detailed explanation.

     

    After some testing on our end, we've identified a possible issue with the latest version of the "Bootloader" Component.

    To work-around this, please try the following:

     

    1. Open the project in Creator 3.0 (start with a fresh download of the .zip from here)

    2. Chose to update all Compnents, EXCEPT the "Bootloader" Component. "Bootloader" should be forced to stay at v1_10 (do not update to v1_20)

    3. Apply correct dependency to the Bootloadable Component (point to the .hex file from the Kit)

    4. Build you project - it should now be free of the bootloader erros you were seeing

    5. In case you notice a DRC error related to "SOF Terminal", you can ignore that without any impact on the design. Alternately, you could close any .cymacro files that open up after the build proceess to ignore this DRC.

     

    We're continuing to further investigate this issue on our end, will keep you posted. Thanks!

  • in reply to cy.gul

    Hi Gagan,

     

    Just a note to say;

     

    The Pioneer Kit Guide is geared up for PSoC Creator 2 and not for PSoC Creator 3 and there is a difference with the System Tab screen between versions thus it is impossible to match the screen shot with the screen.

    (It's the Require XRES pin Checkbox option - It's missing from PSoC Creator 3.)

     

    The procedure works perfectly with PSoC Creator 2.2 (CS6) but I have had no success with using PSoC Creator 3.

    I get "The command 'cyelftool.exe' failed with exit code '1'.

    I've tried various suggestions such as using Bootloadable component version 1.10 and clean build environments (i.e. only with the nominated GCC version) with no success.

     

     

    Very Compact

  • I was looking for this for a while and has been here since September! oh my god. Today is Christmas eve so I would see this as my Christmas present. Now I'll do my testing to see if my wish can be a reality.

    Great post, thanks.

  • in reply to camuyano

    Compiling the project is not a issue for me, however after flashing the PSoC5 on the Pioneer kit is not beeing recognized by the PC as a KitProg. Tried to browse for the drivers to have windows install it as a kit prog like when has the KitProg from the kit firmware. But without any luck. Will resume trying on it latter. If anyone has any update with this please comment bellow.

    I tried upgrading and without upgrading the bootloader component.