PSoC™ 6 Forum Discussions
Hi,
I have a device with a Cypress PsoC4 that is running the UART_to_BLE_Central project in PsoC Creator. And I have a device with Cypress CY8CKIT-062-WIFI-BT kit that is running BLE_Hello_Sensor in WICED Studio. However, the devices do not pair. I can connect to the BLE_Hello_Sensor project from the phone.
What can I do to fix the problem?
Thanks.
Show LessI see a number of similar posts regarding this question, but they all seem to be from several years back and was hoping for more recent information. I recently became very interested in PSOC 6 devices due to hardware capabilities and software development tools (Modus Toolbox utilities, video tutorials, forum support, etc.). I was considering migrating my future designs to PSOC 6 devices, but ran into some confusion when looking into part availability. Specifically, I am interested in PSOC 61 and PSOC 63 devices in QFP and QFN packages (so the soldering can be visually inspected). My first question has to do with conflicting information on the PSOC 61 product page. I initially saw that the PSOC 61 only came in BGA and WLCSP packages on the overview tab.
However, when using the product selector guide, I saw that there were several PSOC 61 options for both QFP and QFN packages, and was confused by the discrepancy. The PSOC 63 doesn't have an I/O Subsystem & Packages section on its overview tab, but the product selector guide does show a few QFN options. When searching for PSOC 6 parts on Digikey, I noticed that there was only stock for BGA packaged parts despite what the product selector guide led me to believe. Are the PSOC 6 QFP/QFN packages going to be made available in the future or are they being phased out? If they are going to be made available in the future, when can we expect them to be released? Additionally, there only seemed to be about 7 parts in stock across all PSOC 6 devices irrespective of package type, giving me concerns about part availability in general.
Show LessPSoC 6 BLE Prototyping Board Guide, Doc. # 002-24993 Rev. *A says
Connect the Prototyping Board to the PC through the USB Micro-B Connector (J8) as shown in
Figure 3-2. The kit enumerates as a composite device. If you are plugging in the PSoC 6 BLE
Prototyping Board to your PC for the first time, the kit drivers will get installed automatically.
Is there any other way to install the kit drivers? We're thinking of buying the CY8CPROTO-063-BLE, but want to explore it in PSoC Creator first, to make sure it meets our needs.
Show LessI am following "Snippet 2: PDM/PCM Asynchronous Receive" from the link below:
https://cypresssemiconductorco.github.io/psoc6hal/html/group__group__hal__pdmpcm.html
The pdm_pcm_event_handler never gets called but when I comment out the line below it starts working.
Hi,
I have a PSoC 6-BLE Pioneer Kit (CY8CKIT-062-BLE). I would like to display the status of PSoC6 with (TeraTerm) on the UART of the PC, but I would like to display it using the BluleTooth (BLE4.2) built into the PC instead of using the dongle. Is there any samplea close to this?
Especially for the development on the PC side, it would be helpful if you could give me advice on whether to take the same approach.
Thanks,
Kenshow
Hi.
In cyhal_i2c_master_read() (and cyhal_i2c_master_write()), a failure returned by Cy_SCB_I2C_MasterSendStart() (or Cy_SCB_I2C_MasterSendReStart()) will cause the value returned by cyhal_i2c_master_read() not to be a legal cy_rslt_t.
Cy_SCB_I2C_MasterSendStart() returns a cy_en_scb_i2c_status_t, and if this value is anything other than CY_SCB_I2C_SUCCESS, it will become the return value of cyhal_i2c_master_read(), which is defined as returning a cy_rslt_t.
cy_rslt_t cyhal_i2c_master_read(cyhal_i2c_t *obj, uint16_t dev_addr, uint8_t *data, uint16_t size, uint32_t timeout, bool send_stop)
{
if (_cyhal_scb_pm_transition_pending())
return CYHAL_SYSPM_RSLT_ERR_PM_PENDING;
cy_en_scb_i2c_command_t ack = CY_SCB_I2C_ACK;
/* Start transaction, send dev_addr */
cy_en_scb_i2c_status_t status = obj->context.state == CY_SCB_I2C_IDLE
? Cy_SCB_I2C_MasterSendStart(obj->base, dev_addr, CY_SCB_I2C_READ_XFER, timeout, &obj->context)
: Cy_SCB_I2C_MasterSendReStart(obj->base, dev_addr, CY_SCB_I2C_READ_XFER, timeout, &obj->context);
if (status == CY_SCB_I2C_SUCCESS)
{
while (size > 0) {
if (size == 1)
{
ack = CY_SCB_I2C_NAK;
}
status = Cy_SCB_I2C_MasterReadByte(obj->base, ack, (uint8_t *)data, timeout, &obj->context);
if (status != CY_SCB_I2C_SUCCESS)
{
break;
}
--size;
++data;
}
}
if (send_stop)
{
/* SCB in I2C mode is very time sensitive. In practice we have to request STOP after */
/* each block, otherwise it may break the transmission */
Cy_SCB_I2C_MasterSendStop(obj->base, timeout, &obj->context);
}
return status;
}
-Nick
Show LessHi,
I've selected a New Application for PSoC 6 Wi-Fi BT Prototyping Kit and I selected GPIO_Interrupt. After the project is created I see only one project. Where is the project for CM0? As far I know PSOC62 always require two project on for CM0 and one for CM4.
Show Less
Hello,
I am learning PSoC6 from the PSoC6 101 video tutorial series . From the PSoC 6 - 1-1-Introduction Alan Hawse told that PSoC6 chapters contains 4 parts.
I have downloaded the 1st,2nd and 3rd parts. And the last part is "connecting with WiFi & Cloud services".And I do not know the hyperlink of it. How can I get it?
Thanks in advance.
I've been trying to get my BLE over-the-air (OTA) device firmware update (DFU) to work. My bootloader is just a stripped down version of the CE16767 example code. I am fairly sure that it is working right because CySmart has no problem downloading my code and then after the download the system gets through the soft reset all the way the call to SwitchToApp(stackPointer, resetHandler) in Cy_DFU_SwitchToApp(uint32_t appId). The system then seems to lock up in the assembler code in Cy_DFU_SwitchToApp.
In Cy_DFU_SwitchToApp, stackPointer gets set to 0x08008000, which just doesn't seem right. To the best of my understanding, 0x08008000 is the starting address of core1 of the bootloader and the stack start for the main app should be at the end of the ram allocated to App1.
So my best guess is that I've somehow botched the updates I had to make to the 4 dfu_cm*.ld linker scripts. I have attached those scripts. Can anybody spot anything I bungled in them? Or do they look like they should be fine as is and I should look elsewhere?
Thanks for any and all help,
Ed H.
Show Less