PSoC™ Creator & Designer Forum Discussions

Hi,

I'm working on a custom library for PSoC 4.

It simply uses some GPIO to create Software Serial communication interfaces.

I can see the components and load them in Topdesign when using Any PSoC4 with one exception: PSoC4 BLE can't see these components.

I have a flag on PSOC Creator 4.2 that there are multiple definitions of components.  I searched, the only answered question I could find was for a revision of PSOC Creator that is no longer relevant - the option does not exist as explained.  I tried to remove the old definition under Tools>Options>Design Entry>Component Security but it had no immediate effect and after restarting the old value had reappeared.

Help?

I appreciate having the ability to extract a Unique ID from the IC being used.  This can be very helpful.

However, what is the proper way to extract the 64 bit number?  I tried two ways and get two answers.

If call CyGetUniqueID() with a uint64 array I get the following back:  74240C2109020100

If call CyGetUniqueID() with a uint32 array I get the following back:  0902010074240C21

UART port output:

Unique ID (64 bit): 74240C2109020100

Unique ID (32 bit): 0902010074240C21

You'll notice the numbers are identical EXCEPT that the each set of 32 bits are switched.  It appears to have a long-order endianess.

Attached is a archive of the project for your review.

Len

In the Logical section of the component catalog I do not have any gates. They are located in the CyPrimitives folder in my C drive but they do not show up in the catalog. I have checked the permissions of the CyPrimitives folder and made sure it is set to Full for all users. My project dependencies also have CyPrimitives 'components' and 'code' checked. I suspect I am missing other components as well.

I am using PSoC Creator 4.2 on Windows 10.

Any ideas? Thanks!

Using PSoc4 224110, seeing some issues with I2C Errors and looking to recover the bus. I'm seeing conflicting responses and wondering what the recommended method is.

Two Issues:

1. A slave device is in mid-transaction and holding the bus down. Typically the response is to manually toggle SCL until it releases the bus.

2. Of course when this happens the I2C Master is also busy and that must be reset as well. Is it sufficient to just I2C_Stop() and I2C_Start()?

Read all of the following without finding a good answer:

Trouble resetting I2C Master after glitches.

Reset I2C

I2C Master stuck - MCSR stuck with START_GEN set

I2c_BUS_BUSY

CYW20719 and CYW20735 I2C Compatible Master

I2C Discussion

Here's what I try:

/*  `#START UART_Boot` */

#include "TxEnable.h"

/*  `#end` */

cystatus UART_UartCyBtldrCommWrite(const uint8 pData[], uint16 size, uint16 * count, uint8 timeOut)

{

    cystatus status;

    status = CYRET_BAD_PARAM;

    if ((NULL != pData) && (size > 0u))

    {

/*  `#START UART_Boot` */

        TxEnable_Write(1);

        CyDelayUs(5);

/*  `#end` */

        /* Transmit data. This function does not wait until data is sent. */

        UART_SpiUartPutArray(pData, (uint32) size);

        *count = size;

        status = CYRET_SUCCESS;

        if (0u != timeOut)

        {

            /* Suppress compiler warning */

        }

/*  `#START UART_Boot` */

        CyDelayUs(50);

        TxEnable_Write(0);

/*  `#end` */

    }

    return (status);

}

ON clean and build, above mods get removed and here's what gets appended to the new generated source:

/* [] END OF FILE */

#if 0 /* begin disabled code */

`#start UART_Boot` -- section removed from template

#include "TxEnable.h"

`#end`

#endif /* end disabled code */

#if 0 /* begin disabled code */

`#start UART_commwrite` -- section removed from template

        CyDelayUs(50);

        TxEnable_Write(0);

`#end`

#endif /* end disabled code */

I have a char array, example char c[] = {0xC0, 0x02, 0x00, 0x01, ...}

I want to send it over uart to another device via a while loop and UART_putchar(*c) but I also want to send it over USBUART so I can see it over terminal but  USBUART_putchar doesn't seem to work. My guess is it's trying to change it to an ASCII character. I've found other discussions that did something similar but not quite the same thing and the same thing goes just trying to find stuff on stackexchange.

What I have so far is something like:

char str[3];

    for(int i=sizeof(c); i>0; i--){

        sprintf(&str[1],"%2x",c);

        USBUART_PutString(str);       

    }

to make sure that it has a null termination on the string but that doesn't seem to work. I just want termial to print out "C0020001...." and no matter what tweaks I've done can't seem to figure out why it's not working.

Any help would be greatly appreciated.

(using CY8KIT-050 i.e. PSoC 5LP and PSoC Creator 4.2)

I am trying to debug my project, which uses Bootloadable/Bootloader.  This has been working fine for about a year.

When Bootloadable is disabled, I can program the chip and then "Attach to running target" with no problems, so I don't think this is a hardware problem.

When I enable Bootloadable, program, and then try "Attach to running target", no targets are displayed.

"Enable Device Protection" is disabled in the application code and the bootloader.

Any ideas about what could have changed?

Thanks.