PSoC™ Creator & Designer Forum Discussions
Hi,
I am working on small project where porting STM32+ChibiOS application into PSoC4 4200
I pretty much converted most of them but having some issue with setting up GPIO
init
{
palSetPadMode(GPIOD, 1, PAL_MODE_INPUT_PULLUP);
palSetPadMode(GPIOB, 0, PAL_MODE_OUTPUT_PUSHPULL);
}while(1)
{
palClearPad(GPIOB, 0);
wait_us(50);
palReadPad(GPIOD, 1);
palSetPad(GPIOB, 0);
}
Above code is from original project and I need to port them into PSoC Creator.
"while" section, I think I can convert them by using per pin api like
CyPins_ClearPin()
CyPins_ReadPin()
CyPins_SetPin()
However, I dont know how to set init pins.
PAL_MODE_INPUT_PULLUP:
PAL_MODE_OUTPUT_PUSHPULL:
I configured eachpin this way but doesnt seem to be working.
What am I missing or incorrectly setup?
Thanks
Show LessHello,
I am trying to establish basic USB communication between my board pSoC5LP and a c# application on visual studio.
As you can see in the attached files. My target is to verify if my soft is able to make 1 reading (switch SW2 state) and 2 writings (led SW1 state and led SW1 pwm duty cycle updating).
I starting thanks to your example AN82072 that I modified a bit (no LCD display and no adc readings).
On my windows 10 x64 host PC, the application works very well as expected.
When I try to use it on another host pc, windows 7 x86. Something strange is happening : once the psoc program is downloaded on the psoc5LP (exactly the same program than when it works on the other pc), I connect it with microUSB and a strange message appear in psoc creator : "Warning Number of Bytes to read is bigger then Input Report Try to Upgrade Firmware". Also the phenomen when I use the App is I have to click several (randomly) times on "Upgrade" button so that the change comes into effect on the LED".
I tried to "upgrade firmware" in utilities page on PSoC Programmer application but nothing evolved... the kit prog is state to the date (version 2.21) !
However, my input report_count and report_size values (in USBFS function) are 8 so I don't understand why this warning...
Could you help me please ?
By the way, I saw you tell on other questions that the CyUSB library is obsolete on windows 10 but the fact is it works very well on my windows 10 x64 PC. And this warning appears just when I try the project on my windows 7 x86 PC...
SO what's going on and what does this warning really mean ?
Thanks, I really look forward to hearing from you,
Antoine
we are automating PSOC miniprog3 using Bridge control panel using python . Can you share the python library for python sample code. so that we can directly give control to programmer. we are using I2C protocal and its code is given below
our I2c code is:
w 68 82 25 p
r 68 x p
w 68 1b 81 p
r 68 x p
Hi, there
I took for starting PSoC3_SW_Sin_X and adapt it for CY8CKIT-059.
Packet received by BCP has MSB always = 0 (it has to be 0x41) and received sin variable values are always = 40.
Other bytes are correct.
(Bytes 0x55 0x55 for serialplot sync)
For control I duplicate output values to UART and got correct results.
Pictures and archive applied.
Show LessI 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) */
}
}
/>
Show LessIt seems like every time I make a change to a schematic, the .cysch.cyvis file gets a raft of meaningless tweaks to component locations at the same time for no reason:
These clutter up the git history and make it hard to find the actual meaningful changes. Can this behavior be fixed?
(I don't understand why these are even saved as floats when the wires and components are always snapped to a grid.)
Show LessHi
I've just started trying to use a PSoC 5LP for the first time. The green LED is on and the display shows the 3.3V input but Creator can't port acquire when I try to program it. I've tried power cycling, reinstalling, restarting my computer but I haven't been able to get it to work.
Any suggestions would be welcome!
Show Less