PSoC™ 4 Forum Discussions
I've searched quite a lot for my I2C-Problem wihtout any success...now I hope you can help me!
It seems that the I2C in MultiMasteSlave-Mode has kind of bug or undocumented state:
When I use the API MasterWriteBuf and there is no slave on the bus, the I2C (actually the whole device), "dies".
Acutally it gets stuck in an endless loop calling the I2C_ISR.
Looking at the Pins, the Master sends the address, doesn't get any ACK of course, and then holds the CLK low and loops inside the ISR.
And due to the loop, there is nothing I can do...(ok, a watchdog would do the job, but that is not what we want)
Setting the Component to MultiMaster without slave, everything works properly: MasterWriteBuf returns 0x00 and then MasterStatus returns 0x22, which is "write complete" and "addr not acked" - perfect!
Does anybody has any idea what is wrong? Am I missing something or is it a component bug?
UPDATE: I think it is something like a BUG/unhandled condition. Writing to your own slave-address causes the I2C to get stuck, as the slave-code seems to corrupt the status. I know this seems strange, but I am using the I2C only as a physical layer for a protocol, where every device has the same slave-address.
WORKAROUND: before writing to the bus, change the slave-address to something safe...and after the master is done set it back to what you want!
Maybe this could be handled inside the component in the future....i.e. prevent it from reading/writing to itself...Show Less
I've included the standard UART block in my project and configured it with baud rate 115200, external interrupt, RX FIFO not empty.
I'm getting the following warning. I don't get the warning if I reduce the baud rate to the one lower. But we need the 115200 for our project. Can you please help me to get rid of this warning?
Clock Warning: (WiFi_Host_SCBCLK's accuracy range '1.333 MHz +/- 2%, (1.307 MHz - 1.36 MHz)' is not within the specified tolerance range '1.382 MHz +/- 5%, (1.313 MHz - 1.452 MHz)'.).
Thanks & Regards,
Part to program = CYBLE-022001-00
Using the MiniProg3 programmer and referencing the ppcli app notes.
Example : Programming a Chip
OpenPort MINIProg3/848E4756090B “c:/Program Files/Cypress/Programmer”
HEX_ReadFile "c:\\CYBLE-022001-00.hex" //Does this specify the device being used???????
I have purchased and received the new BLE kit but have not yet dug into the features or tried to run it up.
Just had a quick question that someone who has already worked with it may be able to answer.
Does the module support SPP and are there any sample Android apps for routines available?
ie. I want to pair smart phone with the PSCO BLE device and transfer serial data in either direction.
I currently do this with an external Sena OEM BT module but would like to investigate lowered cost using the BT built into the new device.
The Bluetooth® SIG recently announced Bluetooth 5 Spec,Nordic has released their BLE 5.0 chip NRF52840, when CYPRESS BLE 5.0 chip will be released? As far as I know, PSOC 6 is not supported BLE 5.0 is only to support BLE 4.2 standards.I believe that there will be a lot of semiconductor manufacturers to support BLE 5.0 chip next yearShow Less
Im trying to get the TFT touch screen v2.0 to work with my psoc 4 development kit but to no avail. I tried to follow both tutorials 72 and 73 but both didnt work. All i see is a white screen. I hope someone out there could share me a working code or tips to make this work.
Hello freinds: I am trying to run my first program using PSOC 4 BLE kit. I plugged in CYBC4247LQI-BL483 chip in KitProg. When I try to debug/program it fails with a message "port acquire failed". Could anybody help me. I using window 10 computer.
Some other info:
1) When I start PSOC programmer, I dont see any device appearing in its list, unless I plugin the dongle. Even when I have dongle in I am unable to debug/program.
2) I see KitProg appearing in "safely remove and eject media section". In device manager KitProg appears only in portable devices section. When I ask to update the driver, it shows all the drivers updated.
Thank you to all.Show Less
Are there any easily available Psoc4 (or 5) chips in a 48 (or less) pin package that can do eight 13 bit pwm outputs + 1 uart rxShow Less