PSoC™ 6 Forum Discussions

Hi,

The ADC_basic example which is present under PSoC BSPs->CY8CKIT-062S4 (device CY8C6244LQI-S4D92) is without modustoolbox GUI setting. In this example, the adc setting is done using firmware.

Could you provide a simple ADC example with modustoolbox GUI setting of ADC?

Thanks

Hi can anybody help on writing assembly code for using CY7C63813 (USB low speed peripheral controller).

I am using a Cy8cproto-063-BLE board to program other psoc 1 and psoc 4 target boards. The setup works fine, but after a while the cy8proto-063-BLE breaks. The MCU does not react to anything and is sometimes shorted fromt VCC to GND. 

When I measure my circuitry, I don't measure any signals that transcend the Absolut Maximum Ratings. The 3.3V VCC is provided by a Meanwell IRM-03-3.3. 

I think the problem might have something to do with ESD. In the "PSoC 6 BLE Prototyping Board Guide" I found This:

Is there anybody who has any tips for me?

Hello,

I have a server which has more than one Miniprog3 connected to it and multiple users use this server to connect to their own PSoC6 boards through separate instances of ModusToolBos IDE.

I tried modifying '/openocd/scripts/interface/kitprog3.cfg' to include 'kitprog_serial  <miniprog4 serial number>' assuming it would ensure the MTB instances would connect to the appropriate Miniprog4 instances, but it would alsways fail to connect. Is this the right way yo achieve this? I have taken the serial number of the Miniprog4 from it's label. Eg: 1939CN00107

In short, I would like ModusToolBox IDE to choose between multiple Miniprog4 connected in the same system to program/debug.

thanks,

Suresh

Hello, everybody.

I'm developing a mobile PSoC6 (CY8C6347FMI-BUD53) measurement system with BLE communication on Modus Toolbox (Version: 2.2.0 Build ID: 2181).

I can monitor all the BLE events for debug  by sending the message to the terminal PC through UART. My PSoC6 system have Peripheral and Observer role and have two characteristic, 'write' characteristic and 'read/notify' characteristic.

Now I have a trouble in BLE communication.

When I wrote data to the 'write' characteristic from central device (android smartphone), CY_BLE_EVT_GATTS_WRITE_REQ event arose twice every time. Contents of the event parameter variable in the both events were completely same. Other events arose only once every time. 

The firmware on this system was transported from the firmware which was developed for PSoC4 on PSoC Creator, and the system worked well, of course without duplicated WRITE_REQ events. 

I temporarily revise the firmware to ignore the second WRITE_REQ event, and it looks working well.

But I want to know how it arise fundamentally and correct the firmware not to  arise duplicated event perfectly.

Please teach me something if you have a hint or know how to solve the problem.

Thank you for reading.

Keiichi

I have a Psoc 6 I2C master.  The desired frequency is 100kHz.  The configuration window says the actual frequency is 96kHz, SCB clock 1548kHz.  With a scope, I'm measuring 49kHz on SCL.

The symptom is occasionally, there is an unexpected extra byte of data received from the slave.  Using a 3rd party I2C tool, the data received is as expected.

What might be wrong? 

Hi,

I want to write data to the external flash using the dev. kit CYW9P62S1-43438EVB-01.

QSPI is inited and XIP is enabled (linker .ld script is ok and WiFi firmware is running out of the QSPI flash with success. I want to read and WRITE my applciation data to an unused area of the QSPI flash. Is it possible to do that and how? I checked: direct writing to addresses (in runtime, using pointers in C code) of the mapped memory does not work in my code.

This is how I configure the QSPI:
const uint32_t bus_frequency = 50000000lu;
result = cy_serial_flash_qspi_init(smifMemConfigs[0], CYBSP_QSPI_D0, CYBSP_QSPI_D1,
CYBSP_QSPI_D2, CYBSP_QSPI_D3, NC, NC, NC, NC,
CYBSP_QSPI_SCK, CYBSP_QSPI_SS, bus_frequency);
result += cy_serial_flash_qspi_enable_xip(true);

Thanks in advance

Hello,

I have been referring to some thread related to how a non-dedicated pin can be used for ADC.

I would like to route the Non-Dedicated Pins (P8[0:7]) as SAR ADC Inputs through AMUXBUSA/B for PSoC 6 MCU in MTB2.2.

I see some useful code snippets here

"https://community.cypress.com/t5/Knowledge-Base-Articles/Route-Non-Dedicated-Pins-as-SAR-ADC-Inputs-through-AMUXBUSA-B/ta-p/250484" 

but I'm not clear on how the macros are used (eg: MUX_SWITCH, CONFIG_CHANNEL, etc). Also I would like to see how one can close the route and reopen it for another set of pins (I have to use 8 pins through AMUXBUSA/B). Also how do I read the ADC value on these pins. It would be better if you could share with me a working sample code. Thanks for your help.

regards,

Suresh

BDOTO as an Electric vehicle producer company starting a new project going to create a produce a gateway which  talk with wall(grid) with (PLC) power line communication and connect with his own battery management system with CAN line and alternative product of QCA7005 we want to use CY8CPLC20-48LTXIT. Can you suggest if is your PSoC has this capacity. If not can you suggest me an alternative.