How do we interpret '@INSTANCE_NAME'

Questions about programming (not codeing) PSoCs and Encore II as well as freeware programming hardware and software are discussed here. This is also the place to talk about production programming. Programming means loading a HEX file in to the Flash, not, writing your program.

Moderator: ericb

How do we interpret '@INSTANCE_NAME'

Postby NikhilGupta » Fri Aug 31, 2012 4:11 am

I had installed PSOC designer 5.2 and was looking at one of assembly file:

USB_std.asm (this is in /Cypress/PSoC Designer/5.2/common/cypresssemideviceeditor/data/stdum/bootldrusbfse/ver_1_0/)

How do you interpret '@INSTANCE_NAME' here in this file?

Usage is:

#include "'@INSTANCE_NAME'_macros.inc"

I tried assembling this file using psoc deginer 5.2, but getting an error that

Error ---- '@INSTANCE_NAME'_macros.inc file not found

I understand that this should be USB_macros.inc file. So I had placed USB_macros.inc file in my directory. But still getting this error.

Please help to understand this type of syntax.
NikhilGupta
Newbie
Newbie
 
Posts: 1
Joined: Fri Aug 31, 2012 4:00 am

Re: How do we interpret '@INSTANCE_NAME'

Postby bobmarlowe » Fri Aug 31, 2012 7:51 am

You are playing around with a template-file that is used to create the needed sources. `@INSTANCE_NAME` is replaced with the component name (MyUSB, or whatever you name the component). This is method is used to generate the different APIs required for the different components. DO NOT CHANGE THESE FILES!!!
When you would like to know more about component creation, go to PSoC3/5 Creator 2.1 and have a look into the Component Author Guide.

Bob
User avatar
bobmarlowe
The Big Cheese
The Big Cheese
 
Posts: 1490
Joined: Thu Oct 06, 2011 2:03 am
Location: Germany


Return to “%s” Device Programmers

Who is online

Users browsing this forum: No registered users and 1 guest

cron