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".
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.
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-
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 :(
1 of 1 people found this helpful
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.
have you figured out how to debug with PSoC Creator 4? What PSoC type do you use?
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.
I can confirm that this bug is specific to PSoC Creator 4
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
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.
The problem still exist with Creator 4.1, we wait for Creator v4.2 or later