PSoC™ 6 Forum Discussions
Hi,
I am learning the BLE bonding and pairing by studying the code example "CE212742".
In the StackEventHandle in the example code, there is the following code:
/* Generate new private address automatically */
Cy_BLE_SetResolvablePvtAddressTimeOut(CY_BLE_PVT_ADDRESS_TIMEOUT);
My question is:
1. Will the BLE API automatically renew the private address after this "CY_BLE_PVT_ADDRESS_TIMEOUT"?
2. Will the StackEventHandle receive an event after this "CY_BLE_PVT_ADDRESS_TIMEOUT"? If yes, what is the event?
Thank you very much for reading the question and providing any comments or suggestions.
Best regards,
Jiabin
Show LessHello,
I'm investigating ECC support for internal Flash / SRAM in the PSoC64 family.
I found the below link.
https://community.infineon.com/t5/PSoC-6/Does-PSoC6-support-Error-Correcting-Code-for-memory/m-p/216379#M8011
Ans: PSoC 6 BLE devices do not support ECC on either Flash or SRAM.
Does PSoC 64 family also not support ECC either Flash or SRAM?
Best Regards,
Naoaki Morimoto
Show LessHi.
Could you please let us know Infineon recommended free viewer to open gerber file(.art, .drl and .ipc file)?
Best Regards.
Yutaka Matsubara
Show LessI am using a PSoC BLE Pioneer board (PSoC 63) with PSoC Creator 4.4 and using the built in GNU C Compiler.
I am currently getting the RTC working and started by porting code from CE218542 - PSoC6 Custom TickTimer RTC to my test app (tests various hardware using a simple menu-friven system via the terminal). The RTC and Alarm worked, sleeping and waking at the specified intervals. I wanted to make a few changes to the example code and then put it as a wrapper into a driver file that later I will port into my main project.
I created c and h files to house this code in the Shared Files virtual folder, then copied the code from main.c over to my new files. But now, I get the fatal compiler error "Build error: 'RTC_RTC_IRQ_cfg' undeclared (first use in this function)".
I am including "project.h", "RTC.h", "cy_rtc.h" in my new files, which is all I had added in main.c.
I have come across this sort of issue before while developing drivers for other hardware: if my files are located in Shared Files, some things like these xxx_xxx_cfg structures cannot be found outside of main.c, or ISRs don't work if placed in my own files and need to be placed inside of main.c. I found this with initialising the SPI, too.
No doubt it is something obvious to people who are more familiar with this platform and toolchain, so please help me to understand it.
Thanks, Simon
Show LessMy program has exceeded the flash capacity of the chip. How can I optimize the library. How can I remove some unnecessary things, such as CapSense? I can't tick off CapSense in library manager。How can I only use PDL ? thanks!
Show Less
Hello, I am a developer who is developing PSOC6 WIFI-BT Pioneer Kit.
While implementing the method of extracting unique IDs, I am asking because I have a question.
I have got the Pioneer kit working with various peripherals. In a testbed program I make extensive use of the virtual com port to the PC to carry debugging information and to select various hardware tests to run. Everything has been running nicely.I am using PSoC Creator 4.4.
I have just added a new hardware module to this testbed which consists of a hardware board connected by the Arduino connectors and a code library from its manufacturers, for which I supplied a port for the PSoC 63. On its own in an app, this code seems to work very well, and it seems to be working in my testbed, except:
After I have run its initialisation routine, the virtual com port continues to send more data to the PC, but no data is received from the PC. Pressing the Reset button on the Pioneer board resets the program but the RX from the PC still doesn't work. The only way to restore full function seems to be to unplug the USB and plug it back in again, which works every time.
The new routines do make some use of the com port, but only using printf(). My input function just uses getchar().
Can anybody suggest what is happening to "lock up" the RX function?
Show LessHi Team,
We are designing with CY8C6247FDI-D32T.
The design has.
1*SPI - MISO - P6.1 - scb[8].spi_miso:0
MOSI - P6.0 -scb[8].spi _mosi:0
SCK - P6.2 - scb[8].spi _clk:0
CS - P6.3 - scb[8].spi_select0:0
2*ADC - P10.0, P10.1, P10.4, and P10.5
1*DAC - P9.2
8*PWM - PWM1 - P8.0 - tcpwm[0].line[0]:2
PWM2 - P8.2 - tcpwm[0].line[1]:2
PWM3 - P8.4 - tcpwm[0].line[2]:2
PWM4 - P11.4 - tcpwm[0].line[3]:3
PWM5 - P5.0 - tcpwm[0].line[4]:0
PWM6 - P12.2 - tcpwm[0].line[5]:3
PWM7 - P12.4 - tcpwm[0].line[6]:3
PWM8 - P5.6 - tcpwm[0].line[7]:0
2*I2C - I2C1 - SCL - P7.0 - scb[4].i2c _scl:1
SDA - P7.1 - scb[4].i2c_sda:1
I2C2 - SCL - P11.0 -scb[5].i2c _scl:0
SDA - P11.1 -scb[5].i2c_sda:0
3*UART - UART1 - RX - P1.0 - scb[7].uart _rx:0
TX - P1.1 - scb[7].uart_tx:0
UART2 - RX - P0.2 -scb[0].uart _rx:0
TX - P0.3 -scb[0].uart_tx:0
UART3 - RX - P12.0 -scb[6].uart _rx:0
TX - P12.1 -scb[6].uart_tx:0
SWD is the debugging interface. -
SWDIO - P6[6]
SWCLK - P6[7]
XRES
SWO - P6[4]
32KHz RTC OScillator - P0[0], P0[1]
Part Number - CM9V-T1A-32.768KHZ-12.5PF-20PPM-TA-QC
Load Capacitor 22pF
High-speed oscillator - P12[6], P12[7]
Part Number - LFXTAL063075BULK
Load Capacitor - 12pF
The schematic is attached herewith.
Please let me know if there are any mistakes.