Hi,

I have started having an issue on my main pc (this did not occur until today and does not happen on other pc).

When I attempt to debug, I get the error below. If I "continue" I can step through code but this error dialog comes up at each step.

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 Support Team,

We are trying to evaluate the cypress board part number CY8CKIT-062S2-43012. for that we are using the AnyCloud_WLAN_Low_Power example. 

Version : Kittprogramming3. 

IDE : Eclipse Modus Toolbox

In this example, the cypress module takes the DTIM interval and beacon interval from the AP.

But now we want to change the DTIM interval and beacon interval in the code itself. we don't want to take from the AP.

Can you tell us "How to enable the DTIM interval and beacon interval" in this example?

------------------------------------------------------------------------------------------------------------------------------------------------------------

In the Readme file below point has mentioned: can you please elaborate on this sentence more?

As per our understanding, first, we have measured the current at the J17 jumper and then measure the current at the J8 jumper. after that we have added both currents. and assume that the final current. Is this our understanding correct?

--------------

For CYW43xxx:

1. Measure the current at VDDIO_WL across VDDIO_WL and VCC_VDDIO2 at J17.
2. Measure the current at VBAT across VBAT and VCC_VBAT at J8.

Note: The level translator, U17, consumes approximately 110 uA and adds this leakage when measuring across VDDIO_WL. So, remove U17 which is on the back of the board below J3.1.

-------------

In the below table we follow the 2nd point (CYW43012 (VBAT)). but we are getting approx. ~700-800uA current. do we need to enable any setting parameter in the code to get the below-mentioned current?

Regards,

Kanaiya Sharma

I have a startup problem with the PSCO4 BLE module, here is the functionality:

1. It is a sealed unit, with an internal LiPo battery, and externally I can only provide 5V to charge
2. It appears that from a dead battery, if you start charging there is maybe 1 in 20 chance, PSOC4 hangs and doesn't start up properly
3. The battery now has some charge, and I can't access XRES pin easily (you have to remove a few things to get to the signal). It looks like you need to let the battery fully discharge and then try again to power up the next day
4. The external way you know it's charging is if the firmware checks a GPIO from the charging IC, and then turns on an LED, I can see the charge current going into the battery (charging IC is working), but firmware is not working
5. The project supports an OTA update (fixed stack bootloader)

So my question is this:

• If I enable the Watchdog timer Hard reset in the firmware image -- is that enabled at power-up,  or is it still a firmware step to enable the watchdog per the FLASH image?
• I had this slight hope that the watchdog could help if the firmware hung, and issue the reset to the device -- but if it requires firmware to enable the watchdog, it may never get to that step.
• Same question with the brown-out detection circuit, does that require a firmware step to program at power-up
• Is it possible that it is hanging in the bootloader section first 

I already have many units built, and I have no real ability to redo HW right now (very painful). I can easily update the main firmware image, but changing the bootloader is also very hard. 

Any thoughts on the firmware watchdog solution?

Is it possible to use CY5677 CySmart as USB Bluetooth dongle for PC.

Command

`btattach -B /dev/ttyACM0 -S 115200`

don't work with it.

Hi, 

I am using AnyCloud Mqtt Client with CY8CKIT-062S2-43012.
And trying to add https client to the project (I need to get some data before connect to mqtt server).
How do i add it?

And now aws-iot-device-sdk-embedded-C is using v4_beta release, is that stable or usable for product?

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 mast 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