I use PSoC 4200 BLE and RTC module with DTS correction and it only works correctly if the module is initialized in the same year.
When next year comes, the correction no longer works.
If I initialize the module at the end of the year, the correction will not work at all.
This is because the calculation of the Unix time value of the correction time occurs at the moment when it is applied, and it would be necessary to increment the value of the year so that the value of the Unix time corresponds to the next year.

</

void RTC_Update(void)
{
static uint32 RTC_currentTickNumber = 0u;
RTC_currentTickNumber += RTC_updateTimePeriod;

if(RTC_currentTickNumber >= RTC_tickRefOneSec)
{
RTC_unixTime++;
RTC_currentTickNumber =
(uint32) RTC_currentTickNumber - RTC_tickRefOneSec;

#if(0u != RTC_INITIAL_DST_STATUS)
if(RTC_unixTime == RTC_unixTimeDstStart)
{
RTC_dstStatus = 1u;
RTC_dstTimeOffset = RTC_SECONDS_PER_HOUR;
}

if(RTC_unixTime == (RTC_unixTimeDstStop - RTC_dstTimeOffset))
{
RTC_dstStatus = 0u;
RTC_dstTimeOffset = 0u;

Here must be an increase of year value in RTC_dstStartTime struct and RTC_dstStopTime struct
RTC_unixTimeDstStart = RTC_GetDstUnixTime(&RTC_dstStartTime);
RTC_unixTimeDstStop = RTC_GetDstUnixTime(&RTC_dstStopTime);
}
#endif /* (0u != RTC_INITIAL_DST_STATUS) */

#if(0u != RTC_INITIAL_ALARM_STATUS)
if((RTC_unixTime + RTC_dstTimeOffset) == RTC_unixTimeAlarm)
{
RTC_currentTimeDate.status |= (1uL << RTC_STATUS_ALARM_OFFSET);
RTC_alarmCurStatus = RTC_alarmCfgMask;

RTC_unixTimeAlarm =
RTC_GetNexAlarmTime(RTC_unixTime + RTC_dstTimeOffset,
(uint8)RTC_alarmCfgMask);

/* Call callback function only after new alarm time is obtained.
* Cypress ticket #264756
*/
if (RTC_alarmCallbackPtr != NULL)
{
RTC_alarmCallbackPtr();
}
}
#endif/* (0u != RTC_INITIAL_ALARM_STATUS) */
}
}

/>

https://youtu.be/cqfrZvlawEo

Hi there,

Recently we are trying to develop a prototype using the CY8CMOD-062S2-43012, once we downloaded the hardware info, we realized that there is no pin diagram for the carrier module footprint, in that sense, we don't know what's pin number 1 so we are tempted to follow the standard pin distribution, just like the CY8CMOD-062S2-4343W ( Schematics can be found https://www.cypress.com/file/457816/download) as shown in sheet 7.  So, we would like to have a confirmation on which one is the pin 1 in this module because the schematic for it does not show the pin arrangement for the castellated pads, and the info is not present in the gerbers files as it is for the 4343W module.

Any help would be appreciated.

Many thanks,

Ernesto G.

Hello everyone,

I am sharing a project that shows a basic example of how we can use the SCB UART block to wake up the PSoC 4 from DeepSleep mode. I have seen multiple examples of using the I2C for waking up PSoC 4 from DeepSleep. The example with UART is a useful one that can be used in various projects.

Kit used: CY8CKIT-145-40XX PSoC 4000S Prototyping Kit (Link)

Softwares used: PSoC Creator 4.4, Tera Term

Documents referred: PSoC 4 Serial Communication Block (SCB) Component Datasheet (Link)

Method:

• Select an empty project
• In the TopDesign add the UART component (Make sure it is SCB version of UART not UDB) 
• Mark the option “Enable wakeup from Deep Sleep Mode” in the configuration window option for the UART SCB block component
• I have attached the screenshot of what configuration I have done for the UART 

• Also, add a Digital Output pin in the TopDesign which will be used in connecting an LED that will indicate in which mode PSoC 4 is currently in. 

• The next step of the project is the Pin Assignment
• Attaching the screenshot of my pin assignment for the project attached. You may change it according to the board used by you

Code:

int main(void)
{
CyGlobalIntEnable;
UART_Start();

for(;;)
{

LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);
LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);
LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);

UART_Sleep();  // required to be used to use the feature of UART to wakeup the device from DeepSleep
CySysPmDeepSleep();
UART_Wakeup();

}
}

Observations:

The program is written such that the LED will remain off in the deep sleep mode but when the device enters the active mode it will blink 3 times after which the device enters the deep sleep mode again.

After configuring any terminal software(I have used Tera Term) you can connect to the PSoC kit with UART. After which entering any character which will make the device Wakeup from the DeepSleep mode. Thus any character entered in the terminal will lead to the LED getting blicked 3 times.

Attaching the project here

Thanks and regards,

Ronak H

Hello, 

I am trying to use the notificationlogger from the C# cysmart API to analyses the log out of my PSoc6 BLE prototyping kit. 

Firstly I had the error message saying "Not a valid CySmart dongle!"... By looking a bit into the forum I found the solution to solve this : replace the .dll files with the ones from the current CySmart application (version 1.3).  

Once done, I have another issue : The application fall into the "stop mode" and the following message is displayed : 

"It is impossible to load the file or the assembly 'cybledonglecommunicator,  Version= 1.3.0.8, Culture=neutral, PublicKeyToken=null' or one of its dependencies "

How can I fix it ? 

Thank you in advance for your help, 

Regards, 

ThDe_4683671

Hi All,

I am using CY8C5467AXI-LP108 chip.

I am having difficulty to compile these analog pins:

P4_3/PIN81

P15_4/PIN93

P15_5/PIN94

Receiving this error message:

"apr.M0003:Unable to find a solution for the analog routing."

I have looked up in the datasheet and didnt see any problem using these pins as analog pins.

This is my schema, all the other analog pins are good and fully functional:

@MotooTanaka 

Thanks,

Roy Roif

Hi All,

I am developing software for the Trackpad.

For this i have referred following two examples.

CE195394_HID_Mouse  - In this example 3 Bytes mouse data is sent over USB.  Byte1-Button, Byte2- X data, Byte3- Y data

CE216892 USB-HID Trackpad - In this example algorithm is developed to use trackpad and five bytes data is sent over I2C. 

 Byte1- Button Data, Byte2- X data, Byte3 - Y data, Byte4- 0 (Scroll), Byte5 - XY negative sign data.

What changes i will have to do in the following descriptor to send 5 Bytes of data over USB.

Report Count should be 4 Bytes where the arrow is shown. How do I add USAGE for XY negative sign data? What item should I select here. 

Any help would be appreciated. 

Thanks.

Hello,

I have a question related to the proximity consumption.  I noticed that the proximity consumption is similar to scan 12 buttons at 200 ms.  Is it possible to find a spec somewhere describing proximity current?

My board with 1 button scan only, I measured ~40 uA.

Board with 12 buttons, no proximity enabled : ~110 uA.

Board with 12 buttons, proximity CS1 activated : ~105 uA.

So, I'd preferred to have consumption with around 40uA like one button.  It's why I am confused about this... bad configuration?

Thanks

Env: Ubuntu 20.04, SDK1.3.4_linux

The thing is no matter use cyusb_linux or download_fx3, flash programmer can be loaded to RAM successfully, but the SPI part failed. the terminal log is as below

```

➜ cyusb_linux_1.0.5 ./bin/cyusb_linux
Found FX3 flash programmer
SPI sector erase failed
Failed to erase SPI flash

Thanks in advance!

Hello,

I have probed address line 25 and 26 to see it toggle between bank 0-3. I am able to write erase and see the device ID up to sector address 3FF0000H which shows the first flash in the block diagram, yet when I try to write anything above or even read device ID above, I cannot read any device id, is there a algorithm or something that chooses which flash block it uses besides bit 26 and 25 on the pin side?

Thanks,

George M.