PSoC™ 5, 3 & 1

Hi, I am wondering how to transition a design from the PSoC 5LP to the PSoC 3 with the minimal amount of changes possible (not having to redesign the hardware and software). I am wondering if there are any notable changes I must be aware of besides the specs difference. Of course, a simple change of device and copy and paste will not build or compile successfully. Any helpful information will suffice. The reason I am downgrading to an older chip is because there is a massive chip shortage with a year lead time on a 5LP chip that is currently being used in the design.

If you are using Visual Studio with Mac and PSOC5 (or even possibly PSOC6), you probably recently got several deprecated messages, one for the compiler, one for the Cortex-Debug.

The new compiler is available at https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads

The Cortex-debug requires an update to launch.json, replacing  runToMain: true with "runToEntryPoint": "main"

You can find more information on how to configure these updates at https://socmaker.com/?p=1093

Hey all,

I'm looking into interfacing a PSoC5LP to a bit of a strange I2C Master.  Rather than being designed to run on a bus, I have to interface using SDA/SCL and an INT pin in a "point to point" configuration.  The idea is easy enough, it gives a edge on the INT line, I catch it with the PSoC, and read the 9 data bytes that it sends, but there's a twist. 

The catch is this device does not send an address, just the raw data bytes.  How can I adjust the SI2C to account for this?  I see I can use either Software/Hardware address decoding.  Hardware is probably out of the question since there's just no address at all.

This leaves me with software decoding, in which case it seems like modifying the ISR in SI2C_INT.c to just drop bytes immediately into the buffer rather than doing a check on the address might work.  Maybe some custom code placed in the SI2C_SW_ADDR_COMPARE_interruptStart code block in the ISR?  I could maybe set the "expected address" to something that should never occur as the first byte received (would need to see if this is possible, it only has 1 bit of data, the rest are "Reserved", so maybe they'll read all 0?  That would make it easy.) so it will drop into the address compare where I can drop my custom code to place the data in the receive buffer rather than use it as an address?

An easier option after looking further may be just to use the SI2C_ISR_EntryCallback(); and have it perform essentially a modified version of the stock Slave I2C code.

I'd be interested if anyone out there had any better options, maybe even something that just works in hardware?

Thanks!

Hey all,

I'm trying to track down the cause of some PSoC5LP firmware running into the default interrupt with errno==ENOMEM.

The only way I've been able to reproduce it is to power cycle the PSoC quickly enough after powerup to catch it, and even then I've only been able to get it to occur maybe once every 50 or so cycles.  This makes using the debugger to track it down basically impossible from what I can tell.  It almost seems like it might be occurring when the PSoC is undervolted due to very quick loss and re-application of main power, so some "undefined behavior" might be occurring.  I know PIC MCUs I've worked with have a "Brownout Reset" function to automatically put the MCU into reset when VDD falls beneath a certain configurable voltage.  Does PSoC5LP have anything comparable?

I am running some BIT test on bootup in this firmware and *suspect* it occurs when I manage to power cycle/brownout the system while it is in progress of running these tests.  Specifically, I am running an SRAM March Test, a Stack March Test, and a Flash ECC Test on bootup.  The code for all these tests was taken from the examples in AN78175 (I made a thread about it months ago, actually: https://community.infineon.com/t5/PSoC-5-3-1/PSoC5LP-Using-SRAM-test-functions-from-AN78175/m-p/283692#M45177).

Right now when I manage to trigger the problem and enter the trap ISR for ENOMEM, I simply have it infinitely loop and blink an LED.  I wonder if it would be worth it to try and hunt the exact error cause down.  My other thought is that this occurs so infrequently and might be unavoidable enough, to just perform a software reset in the handler and call it a day?

I'd love a second or third opinion on maybe how I should track this down/handle it.

Thanks!

I'm making improvements to my custom Term component.

I've got a modest work-around to determine if the host port is open.  I'd like to improve upon that.  

The goal:  Quickly determine if the Host port is open and ready to comm or if the host port is closed and DO NOT try to transmit.

Note: USBUART_CDCIsReady() will not work in this instance since it will always return 'not ready' if the Tx buffer is full OR if the HOST port is NOT opened.

I've gone through the datasheet, the USBUART component source code, and made some experimental code.  All to no luck.

Is there an API or Global variable that indicates whether the Host port is open?

Thanks in advance for your help and suggestions.

We have purchased the above IC from one of the open source as there were huge leadtime.

The IC snapshot is attached.

The IC part number/Body mark is CY8C3246AXI - 138 but in PsOC programmer it detects as CY8C3246AXI - 131. So we are unable to load the hex file of the program.

Can you help us?

Hi there,

In my project(program in attached file), I am using a MPU6050 for selfbalancing purposes. I got the raw MPU data, processed it, and obtained an angle. However, when I push the device, it returns a 'noise value' as shown below:

The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :-62 deg
The angle of the MPU6050 is :21 deg
The angle of the MPU6050 is :1 deg
The angle of the MPU6050 is :1 deg
The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :0 deg
The angle of the MPU6050 is :0 deg

Usually a kalman filter is used for this (I think), but I don't know how to do this/I don't understand it. Does anyone know how to do this?

Thank you and have a nice day.