PSoC™ Creator & Designer Forum Discussions

I am getting the following error in Creator 3.2 that I was not getting in 3.1:

Warning: sta.M0017: Warning: Signal __ZERO__: No path found from __ZERO__:macrocell.q to \UART:SCB\.cts (App=cydsfit)
Warning: sta.M0017: Warning: Signal __ZERO__: No path found from __ZERO__:macrocell.q to \UART:SCB\.miso_m (App=cydsfit)
Warning: sta.M0017: Warning: Signal __ZERO__: No path found from __ZERO__:macrocell.q to \UART:SCB\.mosi_s (App=cydsfit)
Warning: sta.M0017: Warning: Signal __ZERO__: No path found from __ZERO__:macrocell.q to \UART:SCB\.sclk_s (App=cydsfit)
Warning: sta.M0017: Warning: Signal __ZERO__: No path found from __ZERO__:macrocell.q to \UART:SCB\.select_s (App=cydsfit)

It appears to reference the UART that I have configured. The UART works without any issues, so I have largely ignored it, but I am wondering why I am getting it in the first place. The SCB module is configured as UART, the options are pretty standard 8 - N - 1 with 9600 baud rate. Looks more like a SPI issue than UART, but I am not specifically using anything SPI unless there is handling behind the scenes for the block that I am not aware of. At any rate, like I said above, the code works fine, my project works fine, I'd just like to figure out why I can't seem to get rid of the error. This project was upgraded from Creator 3.1 to 3.2 - that is when the error appeared.

Maybe the weather is a bit colder today and this explains it?

I am experiencing the compiler optimizing out most of my variables. I have made almost all of them volatile and still cannot prevent it happening. In the attached the array "Sensor[sensorLocation]" does not provide watch elements for the array and when I hover over "sensorLocation" the dialog announces it is "optimized out".

I have a variable called "NumSensors" in the header file of a header file. Several other modules access the variable (which is also made volatile).

The first module initializes the sensors and sets NumSensors ok. Then the first module calls another module (which does not use NumSensors at all), then when returned back to first module, NumSensors keeps setting back to 0. I had to move the declaration for NumSensors into the first module to prevent it loosing its value.

What could be causing this behavior? I never experienced this in Creatore 3.1, then started to get some of these issues with Creator 3.2 and now it appears much worse in 3.2 SP2. Is there some compiler directive or something 3.2 , SP2 is switching on that affects the variable values being held in memory?

I am new to psoc1.  Thought there might be a way to do some custom logic in a digital block but it seems that you can only modify existing modules?  I need a simple clock recovery circuit for synchronous data but looking around I do not see anything that does what I want.  I have a circuit which uses 2 flip flops to clock a rising edge or falling edge and then triggers a counter (that resets at TC) giving me a clock.  The incoming data is NRZ and an edge determines a 0 and no edge means 1.  It has transparency (insert 0 after 5 consecutive 1's).  I can bit bang this but it would be nice if I could get a clock.  Be nicer if I could get the transparency as well.

Any help is greatly appreciated!

Keith

I'm trying to take a uint16 characteristic and store it in a local variable. This is the code:

     wrReqParam = (CYBLE_GATTS_WRITE_REQ_PARAM_T *) eventParam;
            
                 /* If the attribute handle of the characteristic written to
                 * is equal to that of the Delay_Info characteristic, then extract
                 * the Delay_Info data */
                 if (CYBLE_DELAY_SERVICE_DELAY_INFO_CHAR_HANDLE ==
                                             wrReqParam->handleValPair.attrHandle)
                 {
                      TimeSignature[0] =
                                 wrReqParam->handleValPair.value.val[0];
                      TimeSignature[1] = 
                                 wrReqParam->handleValPair.value.val[1];
                
                                 Delay = wrReqParam->handleValPair.value.val;
                 }

wrReqParam works for the uint8 TimeSignature, but Delay is a uint16 and therefore gives me an error. Is there any way around this? Thanks in advance.

I have a production programmer that can serialize PSOC 5LP while being programmed. It appears I can allocate a physical location and a start value and it will put sequentially incrementing numbers into this location each device I program.

The serial number will be 2-byte value.

I am unsure how to set up the location in the PSOC device (how to select a physical address and what declaration to use, then how to read from the address at run time. 

Thanks