PSoC™ Creator & Designer Forum Discussions

Hi, Supporters

I saw an article that UART sense tuner is not available in Miniprog3.

<https://community.cypress.com/t5/PSoC-4-MCU/CapSense-Tuner-%E3%82%92-MiniProg3-%E3%81%AE-UART-RX8-%E3%81%A7%E6%8E%A5%E7%B6%9A%E3%81%99%E3%82%8B%E6%96%B9%E6%B3%95/m-p/215183>

Can Miniprog4 use a sense tuner with UART?

I use  a PSoC 4000S for the MCU.

When it comes to using PSoC creator, usually I use C language. If using python is possible in PSoC creator, I want to use it some situation. Please let me know the information about this question.

I use PSoC version 4.2 and the example of capsense V5.0  work normally,  I want to use capsense v7.0, but it always report an error.  Build error: The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.

Is my PSoC version inappropriate?

What is the improvement of v7.0 compared with V5.0?

Target : Developing HID Device with CYBLE 222014-01

we are developing HID Device and BLE connectiong with PC or Other Central Devcie

We'd like to know which function handle BLE Request from PC

or,  If there is sample code to handle this operation, Please let me know.

Many Thanks

I used Psoc creator 4.3 for a log time with out getting such a issue. Since some days the creator freezes when trying to start debug. I updated to version 4.4 but the issue still exists. Psoc creator freezes for about 120 sec and  then continue, windows give a sound. Today each debug start suffer from this delay.

WIN 10, MINIProg4, only 20GB free SSD space left.

What can I do to get rid of this pause?

I’m using CYW9P62S1-43012EVB-01.
I use PSOC6, but when I heard that PSOC6 generally uses modustoolbox I was curious for some reason, so I asked a question.

For example 
# pragma abs_address: 0x4000
static const uint32 MASTER = 0x22222222;
 # pragma end_abs_address
I expect to read the memory with a PSoC programmer and see 22222222 in cell 4000, but the value puts into another cell.
Or so

uint8 ram_array[16]={0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,0x11,}; 
static const uint8 CYCODE eepromArray[]= {0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88,0x88 }; 

int main()
{
CyGlobalIntEnable; 
EEPROM_Init(0x4000);
CyDelay(20000);
EEPROM_Write(ram_array,eepromArray,16);
}

I expect to read 888888 ..., turn on the device for 20 seconds and then read 1111111 ...
But I read 888888 in both cases ...

I'm trying to learn if I can make a very slow clock without using up UDB/counters, etc.  The PSoC® 3: CY8C34 Family Datasheet says:

Each clock divider consists of an 8-input multiplexer, a 16-bit
clock divider (divide by 2 and higher) that generates ~50 percent
duty cycle clocks, master clock resynchronization logic, and
deglitch logic. The outputs from each digital clock tree can be
routed into the digital system interconnect and then brought back
into the clock system as an input, allowing clock chaining of up
to 32 bits.

I can make a Clock component and it will use one divider up to 65536 to produce it, but how do I then route it back through another divider?