I am using PSOC5 LP in my design and have USB interface with external Windows based application.
Is it possible to use Python script to access to PSOC resourcing (GPIO/I2C/UART) by Python script?
I have found myself with a problem that seems to be more easily solvable with PSoC 5, but not with 4 or 6 due to just enough UDBs and much more capable analog side, which is crucial. I was almost ready to jump into the ecosystem, but I've noticed that PSoC 4 and 6 are listed "normally", while 5 has been moved to "legacy" section, but I cannot seem to find any document marking this series as obsolete or NRFND. Is PSoC 5 a good choice for new design, or should I look for something else that has similar analog capabilities?Show Less
I reviewed the datasheet associated with the AN2344 and noticed that on the Battery Pack Management System side there are no capacitors (pg. 2 of the attached datasheet). Is this accurate? The BMS appears to achieve the necessary balancing and cell protection on the battery assembly via MOSFET's and resistors. I'm hoping to receive confirmation that by using the AN2344 balanced charger that capacitors are not used in the battery assembly BMS. My application requires the presence of zero capacitors.
Any help will be greatly appreciated.
Joe DeWitt PE, PMPShow Less
I have seen many others having a similar issue, but wanted to post in case my issue is slightly different.
I am using PSOC5LP I2C Master Mode with a DS2484 I2C to 1-Wire Converter.
Everything is working fine - I2C writes and reads, but there are times where something happens (Not sure what is causing this) and the PSOC hangs up in the below infinite while loop
I have implemented a simple watchdog using a 1ms timer interrupt - when the watchdog counter fails to reset, I attempt to reset the I2C peripheral using the following lines. This does not work, and the code continues to sit in the while loop.
The only thing that actually works is calling for a SW reset....Not ideal at all.
Perhaps I'm not calling the right API to actually reset the I2C peripheral, if this is the case, please advise on the proper way to reset the peripheral so that I can break from the while loop.
From a logic analyzer standpoint, when this occurs, SCL and SDA are both logic High and remain at logic High
Ideally we do not want to call a software reset for something as small as this. Can anyone provide any input on what can be done to get "unstuck" from this infinite while loop?
I could implement a timeout inside the while loop, but I fear that this will be an issue when regenerating code, is that correct?
Please let me know what the best course of action to take is.
Can someone tell me where to find a document describing what the markings mean on the top of a PSoC3 microcontroller? The specific part is CY8C3866LTI-030.
i'm trying to program a PSoC1 device [which works at 5V] in an old project using a MiniProg3 device but it doesn't work. Why? Which is the best programmer to use for a PSoC1 device?Show Less
I noticed, that programming an PSoC 5LP (CY8C5268LTI-LP030, 256kB Flash) using the ppcli.exe takes about 70s, whereas the PSoC Programmer takes only about 11s (even after an "Erase all", same Settings).
For the PSocProgrammerCLI(ppcli.exe) I was using the example script in the KBA-ppcli-Article.
The only changes I made, were to adapt the programmer(Miniprog4) and hex File and calling:
"ppcli.exe --runfile example_script.cli"
Is there a way to get the ppcli.exe(v3.29.1) to work (nearly) as fast as the GUI based PSoC Programmer(v3.29.1)?
Or is there a way to program the PSoC5LP without iterating manually over these 4x256 rows?
Our goal is to have a custom user interface, where programming settings are applied, based on the selected device, which should be programmed. Our custom interface works as expected, but the 70 seconds for programming are unacceptable for us.
We use your CY8C3446LTI-085. We recently received a batch of these parts, with the same major part number as just stated, that will not flash. Looking for guidance as to why.
Good parts stamped as follows:
1401 A 04
Bad batch stamped as follows:
1430 A 04
according to the 5LP reference manual the datapath outputs are registered, but it's also possible to use the combinational signal. Unfortunately, I can't find any information about how to enable the combinational output on the device.
For simulating the component, I figured out that it seems to be enough to override a parameter, e.g. so_sync, etc.
But I doubt that this is the correct way to enable combinational output on the PSoC device. Digging deeper into the device manuals shows that this feature seems to be bound to the corresponding UDB config register #8. The default value of this register within the component definition is 0x00.
But here the user can't know which bit is assigned to the output which should be combinational. So, how to correctly enable combinational output for datapath output mux?