Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ Creator & Designer

DzNg_1446756
Level 3
First like received First like given
Level 3

Made a mistake of updating to PSoc Creator 4.0.  Now the debug does not show the variable value, just the address.  Tried to go back to Creator 3.3 but it's not compatible.  Are you guys aware of this problem?  When will it be fixed?  How can I go back to 3.3?

0 Likes
1 Solution
AnkitaS_51
Employee
100 likes received 50 likes received 25 likes received
Employee

A similar phenomenon has been reported at this link,but that correspond to the custom board,as this issue is not reproducible on Cypress kit-

   

http://www.cypress.com/forum/psoc-creator-software/empty-variables-while-debugging-psoc-creator-4#co...

View solution in original post

0 Likes
11 Replies
Bob_Marlowe
Level 10
50 questions asked 10 questions asked 1000 solutions authored
Level 10

Welcome in the forum.

   

Can you please post your complete project, so that we all can have a look at all of your settings. To do so, use
Creator->File->Create Workspace Bundle (minimal)
and attach the resulting file.

   

Probably the variable is not shown because of optimization settings, when put into a register, a variable cannot be shown. Try setting the optimization to "none".

   

 

   

Bob

0 Likes
DzNg_1446756
Level 3
First like received First like given
Level 3

I did not change any setting.  Just default out of the box.  The minimal zipped file is 11.6MB.  Your server won't allow it.

0 Likes
AnkitaS_51
Employee
100 likes received 50 likes received 25 likes received
Employee

A similar phenomenon has been reported at this link,but that correspond to the custom board,as this issue is not reproducible on Cypress kit-

   

http://www.cypress.com/forum/psoc-creator-software/empty-variables-while-debugging-psoc-creator-4#co...

0 Likes
DzNg_1446756
Level 3
First like received First like given
Level 3

We have a custom board, but it was derived from a Cypress kit board.  Not much changed between the 2.

   

Tried setting very optimization settings I can find to every choice there is.  No luck.

   

At this point, we'd like to go back to 3.3.  It worked just fine, but 3.3 can't read 4.0 project 😞

0 Likes
user_1106811
Level 1
Welcome!
Level 1

Hi dzuy_1446756,

   

have you figured out how to debug with PSoC Creator 4? What PSoC type do you use?

   

Best regards

0 Likes
DzNg_1446756
Level 3
First like received First like given
Level 3

We use PSoC5LP.  Just gave the latest 4.0 a try again, but same problem.  This is definitely a bug in 4.0.  We went back to 3.3 and will stay there until this problem is resolved.

0 Likes
Anonymous
Not applicable

I can confirm that this bug is specific to PSoC Creator 4

0 Likes
Bob_Marlowe
Level 10
50 questions asked 10 questions asked 1000 solutions authored
Level 10

When you opened your 3.3 project with 4.0 the first time, a backup was made. Search for that and open it with 3.3.

   

 

   

Bob

Anonymous
Not applicable

Hey guys

   

Have this problem been sorted out. Finding the exact same problem with a psoc 5 on creator 4. 

   

When trying to view the values in the memory view it just shows ## ## ## ## next to each adress

0 Likes
mattl_01
Employee
100 replies posted 50 replies posted 25 replies posted
Employee

Hey folks,  Sorry for the trouble caused by this issue.  It is fixed in Creator 4.1, which is due out any day now.   It happens with certain PSoC 5LP parts.

   

For future note, there should be a folder called "Archive" in your project directory which contains a version of the project compatible with the previous release.  Still, you should NEVER have to go back to a previous release. We've done an 8D analysis on this issue so it will never happen again.

   

Again, sorry about this problem.

   

--Matt

0 Likes
gica_284176
Level 2
First like received
Level 2

Dear All

   

The problem still exist with Creator 4.1, we wait for Creator v4.2 or later

   

Best regards

   

Giovanni

0 Likes