PSoC™ 5, 3 & 1

hello,

I am still new to PSoC and programming in general. I am trying to make a selfbalancing robot. But richt now I am stuck with using the MPU6050 data. I fond/have a code which gives and prints the raw data (depending on the place of the buffer => see code). So the question I want to ask is if someone can help or send me in a clear derection to 'transform' the raw data, to data I can use for the self balancing robot. I can realy use some help.

Best regards,

Switten

Hello @MotooTanaka san,

Thanks a lot for your help on many previous issues of mine.

Based on the last project that you helped with me earlier, I wanted to know if it is possible to store the keypad input to a buffer and then print the buffer (instead of individual characters), if '#' is detected as input or at some interval over UART?

I did try some ways in the print_key_table() function,  but I am not able to store the data properly.

Hoping someone could provide some way for me to get started with the above method.

Regards,
Yash

Hello,

I have severe problems getting USB peripheral of PSoC5 to work. Attached are schematics and layout of my board design.

Whatever I burn into MCU, nothing works...my application, any changes to it, USB-UART CDC example. This I believe rules out  software problems. Device simply cannot be detected by computer at all. If I hard-reset USB data-line by applying external pull-up, unknown device is detected.

I have replaced MCU, ESD protection IC, series resistors, no change. I have sacrificed Cypress USB-BLE dongle's MCU, before unsoldering it was working fine. After moving to my board, it does not work.

If I disconnect computer, and burn firmware outputting clock on USB data-lines, I do not see clean square-wave (impedance mismatch to scope probe?), but I can definitively see correct frequency.

Now my question, what is happening there? I need this board to work correctly ASAP, but I am running out of ideas what to check.

Thanks in advance,

Stanislav

Hello Infineon community!

I finally received my CY8CKIT-059 PSOC5LP. I am a total beginner working with it but I'm looking forward to doing my project with it. 

Accelerometer 832M1-0500:  Supply: 3.3V Sensitivity@80Hz(mV/g)  (X-Y-Z): 3.081-2.534-2.7 Bias Voltage(X-Y-Z): 1.636 1.628 1.659

I'm willing to use the SAR ADC with 12-bit resolution to sample the analog output (60KSPS/channel) of the 3 axes of the Accelerometer. Before the input, I have to filter the signal before with -30dB attenuation at half the sampling frequency.

Can I achieve simultaneous sampling for the 3 axes with the S/H? If not I have to have a minimum sampling of 180KSPS and divide it into 3 to achieve 60KSPS. 

Then, I need to transfer the data of the Accelerometer to an ESP32 with SPI then transmit it wirelessly (UDP) (I think this will be another topic) 

So I have multiple beginner questions. (I think I will receive some replies that I need to read the datasheet😅)

1) Can I use a power bank to power the PSOC using 5V USB? What about the Vref of the ADC (VDDA VSSA etc.) can they be powered internally? If my application is to be battery powered, do you advise me to use a battery instead of the USB powering?

2) Which ADC SAR inputs (pins) do you advise me to use? Can I use the kitprog's and work only with it? Or do I have to involve the target? 

3) I have no idea about how can I filter internally the input. Can you give me some insights? 

4) In the screenshot, I need to check if I forgot something, and ask you what should I put as configuration for the ADC if I power the MCU with USB. Vssa to Vdda? 

The SPI connection and filtering are my next steps, just when I'm sure I'm on the right track

I am sorry for the beginner questions but I'm still learning so I rushed to post a thread to receive advice from experienced people in the field. Feel free to reply even if just to tell me go work on your datasheets or other constructive remarks😂

Thank you, People!

Jad
 

Hi all,

I got stuck trying to get sleep / wakeup running on a PSoC3.

It seems that the device goes to sleep correctly, as I do this:

• sleep components that have API functions to do so
• call CyPmSaveClocks();
• CyPmSleep(PM_SLEEP_TIME_NONE, PM_SLEEP_SRC_PICU);   // allow wake from PICU

I use a GPIO input pin as the wakeup source. I have set up an ISR routine associated to that GPIO. After a wakeup, I do the following:

• CyPmRestoreClocks()
• wake components
• clear GPIO pin interrupt (that caused the wakeup)

I implemented the GPIO and related interrupt as suggested in the example project "PowerManagement_Hibernate" provided in PSoC Creator (and also available as a download from the Infineon website as sample project CE95346), with the only difference that I do not put the device to Hibernate, but to Sleep.

I could successfully test the "PowerManagement_Hibernate" example project on my hardware, but only after removing the MiniProg3 debugger. When the MiniProg3 is connected, the example project does not seem to work. I'm wondering if removing the debugger is a requirement and why it is not clearly stated in the example's description??

In my project (that sends the PSoC to sleep instead as to hibernate) when I press the button connected to the GPIO pin, the device wakes up, but seems to become unresponsive (apparently executing some random code). 

I have read various documents, such as the pdfs provided in AN77900, AN66083 and many more.

But still, I have a few unanswered questions:

• In the AN77900 example, there is no ISR associated to the GPIO pin connected to the button which is supposed to wake up the PSoC. How does the PSoC know which ISR it should run when the button is pressed, therefore issuing an interrupt? There seems to be a confusion with the fact that the pin properties (in the schematic) indicate that the GPIO input pin has its interrupt enabled. On the other hand, there is no ISR handler defined and associated to it.
• I read here that apparently, it is not possible to use the debugger (MiniProg3 in my case) when debugging a PSoC3 that goes into sleep mode. There seems to be an issue with the fact that the IMO clock needs to be kept active for debugging (?). I found it very strange that nowhere in the Community the question: "Can we use the MiniProg3 with projects that send the PSoC3 to sleep (or hibernate)?" is answered. At least, I couldn't find it.
  Can anyone please give me a clear answer?
  If the answer is "NO" (i.e. debugging not possible when entering low power modes), is there a workaround (e.g. a way to keep the IMO clock alive during sleep) to have the possibility to continue using the debugger (obviously at a greater current consumption) just to debug the code and make sure that everything works ?
• Were can we find a complete documentation about the API functions provided in cyPm.c, CyLib.c, CyUtils.c, etc... and all other files provided in cy_boot in the project tree?
  I found something (but not all) in the pdf provided with AN77900, but I'm not sure if there is a better place?

Thanks for all your suggestions!

Hello,

I have a PSoC3-based project to control two motors via PWM.
Currently the PWM block on PSoC Creator is set to work with an input clock of 2MHz, and dividing the period into 100 samples gives a resulting period of 50us and therefore 20kHz.

Wanting to increase the resolution of the PWM to have greater linearity on the movement of the motors, I changed the value of the input clock of the PWM block to 48MHz, dividing the period into 2400 samples to still have a resulting period of 50us and therefore a PWM with a frequency of 20kHz.

After this modification, however, giving the same inputs the motors do not move.

Do you have any suggestions please?
Thank you very much

The suggestions window should show TMR_100ms_Start. I have reinstalled but the problem is still there.

Dear all,

We are looking on using a EtherCAT ESC chip (LAN9252) together with a PSoC5LP.

The LAN9252 chip can be connected over a host bus interface (chapter 9 of the datasheet).

I would prefer to connect it to the PSoC in multiplexed mode in which 16 lines are used for the address and data, with a single line to latch the address.

I have looked into hooking this up in the PSoC5LP and found the External Memory Interface (EMIF).

However, looking at that component I saw no configuration to multiplex the address and data lines.

Is there any standard component that could provide multiplexed address/data lines towards the LAN9252 chip?

It might be possible to create a circuit (inside or outside PSoC) to perform the latching, but I would rather not go that route.

Any thoughts?