PSoC 5, 3 & 1 MCU

[Anonymous]

        I made a project in 2001 - 2002 with psoc CY8C26233. Now I have to update. With the windows 7 psoc designer 3.2 does not work. I found a guide that recommends to migrate to open the project with version 4.4 and then with 5.4. Unfortunately, even with the version 4.4 project does not work anymore, especially in communication uart. The modules included are: Timer16, pwm8, counter8, timer8, uart, cmprg, pga. I look for a table of the changes made ​​over the years on the modules   

[Anonymous]

        Hi marco_b   
I strongly recommend to re-design the project.   
Because, CY8C26233 was obsolete device already   
This can't write by MIniProg, Look at this...   
http://www.cypress.com/?app=forum&id=1573&rID=79423   
C24233 is recommended.   
It is difficult to re-design but no way without it.   
Regards.   

[Anonymous]

        Thanks for the reply. I agree that the CY8C26233 is obsolete, but I have to modify the products installed and I also have a warehouse stocks over 200 pieces to use. The programmer can program them and the compiler compiles the whole, but it does not work.   

[ETRO_SSN583]

You do not have to start from scratch, use your code base, cut and paste into

   

a new project. Then place modules used in old project into new project, and

   

take settings from originating Designer for each module and set up new project

   

modules with those settings.

       

Then compile and debug one functional area at a time. Should not be mount Everest

   

to climb, just a methodical determined approach.

       

Also if you run into a problem, post your new project and forum will try to help you.

           

Regards, Dana.

[ETRO_SSN583]

Apologies, completely missed the point its a legacy part. But part is

   

still in Designer catalog, so possible to move to new project, but

   

there may be issues with individual modules not operating same

   

as in Designer 3.2. But thats a debug process that should be able

   

to overcome.

       

You have a bit of a delemma, each revision of Designer fixed problems

   

in prior revison, as well as enhance. But legacy parts in future releases

   

I would posit are not retested, so there is risk by staying with old Designer,

   

and same for going to new Designer in order to use the legacy parts.

       

You could consider using services of CyPro to do the migration to a new

   

part if turn around is your primary consideration.

       

Or just try to debug old designer with Designer 3.2 and your old tools.

       

Regards, Dana.

       

Regards, Dana.

[ETRO_SSN583]

One last idea, you could file a CASE and get Cypress opinion on best

   

approach, point the case to this thread, and give Cypress your drop

   

dead constraints. Maybe ask them to talk to 233 designer to see if using

   

newer Designer may have any hidden issues.

       

www.cypress.com

   

“Support”

   

“Technical Support”

   

“Create a MyCase”

       

Regards, Dana.

   

[Anonymous]

        Thanks Dana for your answers. Per me questa cosa è incredibile. Io sto usando lo stesso disegno e gli stessi sorgenti che usavo con la 3.2 e compilo per lo stesso chip. Perché il compilatore cambia i moduli? Se i moduli sono diversi dovrebbe mantenere i vecchi. Probabilmente la cosa più semplice è usare un vecchio computer con Windows 98 ed installare la versione 3.2.   

[Anonymous]

        Dana Thanks for your answers. For me, this thing is incredible. I'm using the same design and the same sources that I used with 3.2 and compile to the same chip. Why the compiler changes the modules? If the modules are different should keep the old. Probably the easiest thing is to use an old computer with Windows 98 and install version 3.2.   

[ETRO_SSN583]

Compiler changes to modules generally bug fixes. Sometimes

   

enhancements.

       

Regards, Dana.