PSoC 6 MCU

Hi everyone,

I am currently tranfering a project from an older Cyble to the newer Cyble-416045-02. As part of this project there is a Bootableloader block in there which needs dependencies to the BLE_OTA_Laucher files. (.elf and .hex)

Has someone an idea where I can find those for the mentioned cyble 416045-02 module?

Thanks a lot!

Hello everyone,

I am currently working on Psoc 6 BLE PIONEER KIT and wanted to configure debug in PC terminal. After initializing UART and sending data frame some weird characters appear on computer. Additionaly I've used Basic Uart Implementation project from Cypress YT channel (https://www.youtube.com/watch?v=ZJOF2f423nI&t=297s) - in which messages sent from PsoC Creator are weird but part:

c = getchar();
if(c)
{
printf("%c\r\n",c);
}

works fine...

I've tried changing baud rate but it didn't help...

Few weeks ago everything worked fine. Do anyone have idea what may cause the problem?

Dear Cyprerss/Infineon Support,

Wrong configuration for TX-Enable pin (RS-485 Support) is generated using the Device Configurator 3.0.

I had a problem using the configuration generated with that tool. If I select  a TX-Enable pin it generates a configuration like this:

#ifndef ioss_0_port_3_pin_3_HSIOM

#define ioss_0_port_3_pin_3_HSIOM HSIOM_SEL_GPIO

#endif

But it must be like this to have a signal coming from CTS pin:

#ifndef ioss_0_port_3_pin_3_HSIOM

#define ioss_0_port_3_pin_3_HSIOM HSIOM_SEL_ACT_6

#endif

Regards,

Gintaras

This is a follow up from https://community.cypress.com/t5/PSoC-6-MCU/MCWDT-Interrupt-not-working-as-Deep-Sleep-wakeup-source-in/td-p/120769. I work with @RaMu_4639021  and we're continuing to track down the same issue, but I can't reply on that post. Our idle thread looks roughly like:

uint32_t int_status = Cy_SysLib_EnterCriticalSection();

eSleepModeStatus eSleepStatus = eTaskConfirmSleepModeStatus();

if (eSleepStatus != eAbortSleep )
{
    Cy_SysPm_DeepSleep(CY_SYSPM_WAIT_FOR_INTERRUPT);
}

Cy_SysLib_ExitCriticalSection(int_status);

It's important that interrupts remain disabled between the calls to eTaskConfirmSleepModeStatus and Cy_SysPm_DeepSleep(). However, if we execute Cy_SysPm_DeepSleep() in a critical section, the device will hang while executing Cy_BLE_DeepSleepCallback(). If we never start the BLE component (so the BLE component never registers a call back with Cy_SysPm_RegisterCallback()), then the device sleeps and wakes up as expected. Is it possible to configure Cy_BLE_DeepSleepCallback() so that it can be called in a critical section?

Hi there,

My problem is I need to drive a VGA monitor with a PSoC6. My solution is to use DMA transfers from an image buffer to a GPIO Port. The GPIO Port is connected to an external high speed DAC to convert the digital 8 bit signal into an analog signal for the monitor. 

I've achieved this reasonably well with my PSoC5 LP, PSoC Creator, and the UDB Control Register. The PSoC5 LP would DMA transfer byte-by-byte to the control register block, and this block would be connected in the schematic editor to a bunch of GPIO pins. The pins would update their state at a fixed frequency and according to the value of the incoming DMA byte. This worked very fast and without problems.

However, I've now switched to the PSoC6 MCU, specifically I have the CY8CPROTO-062-4343W (2MB Flash). This board is not supported in PSoC Creator as far as I can tell (I have no idea why, but it is what it is). Since I'm now using Modus Toolbox, I can't create the UDB Control Register I did with the PSOC5. Instead, I looked at the TRM manual and found out you can directly write to the memory mapped GPIO Ports and update their state that way.

I figured out this is how to get the address of the port:

uint32_t* port9 = (uint32_t*) Cy_GPIO_PortToAddr(9);

and you can write an arbitrary byte to it like:

*port9 = 0xff; 

After figuring this out I was relieved, because I thought I could now just do the same thing: set-up a continuous byte-to-word DMA transfer from my source buffer to this peripheral address. I looked at DMA examples for PSoC6 and managed to get it working. Here are some relevant snippets:

// Configure descriptor source. Buffer_a = framebuffer to read from.
Cy_DMAC_Descriptor_SetSrcAddress(&RDMA_Descriptor_0, (uint32_t *) buffer_a);
Cy_DMAC_Descriptor_SetDstAddress(&RDMA_Descriptor_0, (uint32_t *) port9);

// Standard Channel Config
Cy_DMAC_Channel_SetDescriptor(RDMA_HW, RDMA_CHANNEL, &RDMA_Descriptor_0);
Cy_DMAC_Channel_SetInterruptMask(RDMA_HW, RDMA_CHANNEL, CY_DMAC_INTR_MASK);
Cy_DMAC_Channel_Enable(RDMA_HW, RDMA_CHANNEL);

// Start DMA listen for signal
Cy_DMAC_Enable(RDMA_HW);

RDMA is what I named my DMAC channel 0. See the attached image for the exact configuration.

I was very happy because it seemed to work fine. But under closer inspection I realized a huge problem. The generated signal was not consistent.

The source buffer looks like this: All zeros with three consecutive 1's. It gets initialized at the start of main, and never edited again.

for (int i = 0; i < 640; i++) buffer_a[i] = 0x00;
buffer_a[200] = 0xff;
buffer_a[201] = 0xff;
buffer_a[202] = 0xff;

 Thus, on my oscilloscope I'm expecting to see a bunch of zeros followed by a 3 pixel bump.

Like: ______---_______ (see correct_square.jpg)

However, I'm not getting this always. Sometimes, almost every other time, the bump is messed up. Sometimes there's a pixel missing

Like: _______-_-_______ or _______--_______  (See corrupt_square.jpg and half_square.jpg)

And other times there's just a weird, very short dip.

Like: _______-.-________ (See corrupt_square2.jpg).

Also note that I'm running the peripheral clock at 100Mhz. If I divide it by 4 (run it at 25Mhz), I don't have these problems but anything >25Mhz creates this inconsistent behavior. Dividing it by 4 is not an option for me though, as that GPIO update speed is way too slow (the PSOC5 even could clock at 74Mhz without problems).

I'm at a loss of what to do. Is this a limitation of the PSoC6? Surely not? Is there a better / fast / more reliable way to update GPIO pins as quickly as possible instead of writing directly to the Register Port Address? Could I somehow use UDB like I did with the PSoC5?

What can I do?

Any advice would be greatly appreciated. It's very hard to find resources on this topic IMO, so I'm hoping someone can shed some light onto this 🙂

Thank you!

Hi,

I have custom designed a board having CY8C6137BZI-F14  chip. I have made the connection as per the diagram attached. I am using MiniProg3 programmer (10 Pin Connector). It is able to detect the power but unable to acquire the port. I have attached the reference pictures for clear understanding.

I tried all modes, SWD, JTAG, Reset Mode, Power Cycle Mode, Lowering the Frequency, nothing worked.

Can Anyone Help?

@BragadeeshV 

@Len_CONSULTRON 

-Kevin

Hello! I'm developing application which includes changing between broadcasting and observing functions. I'm using CY8CPROTO-063-BLE development board and I have configured push button to trigger interrupt:

void SW2_Handler()
{
flag_ble = ~flag_ble;
printf("button pressed, flag_ble = %i \n", flag_ble);
NVIC_ClearPendingIRQ(Pressed2_IRQ_cfg.intrSrc);
}

Depending on flag_ble value I should switch between broadcasting and observing states. So far I can change from Cy_BLE_GAPC_StartScan() to Cy_BLE_GAPC_StopScan() to Cy_BLE_GAPP_StartAdvertisement() but I cannot change back. Heres my code:

void StackEventHandler(uint32 event, void *eventParam)
{
cy_stc_ble_gapc_adv_report_param_t * advReport;
uint8_t scanState = Cy_BLE_GetScanState();
switch (event)
{
/* This event is received when the BLE stack is initialized and turned ON.*/
case CY_BLE_EVT_STACK_ON:
{
printf("CY_BLE_EVT_STACK_ON \r\n");
/* Stack initialized; ready for scan */
Cy_BLE_GAPC_StartScan(CY_BLE_SCANNING_FAST,CY_BLE_OBSERVER_CONFIGURATION_0_INDEX);
break;
}

case CY_BLE_EVT_GAPC_SCAN_PROGRESS_RESULT:
advReport = (cy_stc_ble_gapc_adv_report_param_t *)eventParam;
printf("CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT:\r\n");

/* PEER Device address type */
printf(" peerBdAddr: %2.2x%2.2x%2.2x%2.2x%2.2x%2.2x \r\n",
advReport->peerBdAddr[5u], advReport->peerBdAddr[4u],
advReport->peerBdAddr[3u], advReport->peerBdAddr[2u],
advReport->peerBdAddr[1u], advReport->peerBdAddr[0u]);

/* RSSI of the received packet from peer Device */
printf(" Rssi: %i \r\n", advReport->rssi);
printf("ADV data: %s\r\n", advReport->data);
if (flag_ble == 255)
{
   Cy_BLE_GAPC_StopScan();
}

}
break;

/* This event is triggered when the central device has started/stopped scanning */
case CY_BLE_EVT_GAPC_SCAN_START_STOP:
{
if (flag_ble == 0){
Cy_BLE_GAPP_StopAdvertisement();
 }
printf("CY_BLE_EVT_GAPC_SCAN_START_STOP, scanstate = ");
switch(scanState)
{
case CY_BLE_SCAN_STATE_STOPPED:
Cy_BLE_GAPP_StartAdvertisement(CY_BLE_ADVERTISING_FAST, CY_BLE_BROADCASTER_CONFIGURATION_0_INDEX);
printf("CY_BLE_SCAN_STATE_STOPPED\r\n");
//CyDelayCycles(150000000*2);
break;

case CY_BLE_SCAN_STATE_SCAN_INITIATED:
printf("CY_BLE_SCAN_STATE_SCAN_INITIATED\r\n");
break;

case CY_BLE_SCAN_STATE_SCANNING:
printf("CY_BLE_SCAN_STATE_SCANNING\r\n");
break;

case CY_BLE_SCAN_STATE_STOP_INITIATED:
printf("CY_BLE_SCAN_STATE_STOP_INITIATED\r\n");
break;
}
break;
}
case CY_BLE_EVT_GAPP_ADVERTISEMENT_START_STOP:
{
for (i = WS_NUM_PIXELS; i>-1; i--){
for (n = 0; n<200; n++){
//do stuff
}
}

printf("0x + i = %i\n", 0x0 + i);
printf("Advertising!\n");
break;
}

default:
break;
}
}

Interrupt seem to work since I see printf from interrupt handler but nothing else happens.

Hello, I am trying to implement a non-blocking SPI Send function with DMA on the PSoC6 with ModusToolbox. The example code ("SCB SPI Master SPI") does almost that, but transfers 12 Bytes every time.

The data that I send is stored in a buffer that 32000 Byte Buffer, and sometimes I need to send the entire context of the buffer, and sometimes just parts of it (say 500-32000 Bytes). 

Right now, I use