I am trying to generate an output frequency of 6 MHz using a PSOC 6 prototyping board but every time I measure the output pin using an oscilloscope its only giving 50 Hz which means no frequency is being generated. I want to get 6 MHz when I measure the output pin. I have attached the project. Can anyone help please?
Thank youShow Less
Is it possible to create an SDIO interface on a PSoC 63 in a WLCSP?
Specifically; is it possible to either split the SDIO to multiple ports or route a UDB based SDIO interface to one of the ports with six or more signals?
There is support for creating a UDB based SDIO interface @ https://github.com/Infineon/udb-sdio-whd
The available library supports an SDIO interface on one of three different ports: P2, P9 or P12. The SDIO interface requires six (6) signals on whichever port is selected for SDIO. Reference the table under "Whats included" @ https://github.com/Infineon/udb-sdio-whd
It appears only a maximum of five (5) signals are available for any of those three ports on a PSoC 63: P2, P9 or P12.
Other ports on the PSoC 63 in a CSP have six or more signals including: P0, P5, P6, P7, P8, P10 and P11.
Reference Table 7 in PSoC 63 CY8C63x6, CY8C63x7 Datasheet @ https://www.infineon.com/dgdl/Infineon-PSoC_6_MCU_PSoC_63_with_BLE_Datasheet_Programmable_System-on-Chip_(PSoC)-DataSheet-v16_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ee4efe46c37
Issue with using user pipe on PSoC 6
I already have the pipe set up and the endpoints registered according to CE223820 example code.
On CM0+ I call this function every 32ms:
CM4_IPC_CALLBACK_ENCODE_AUDIO is 2, which corresponds to the index of the callback function that I am calling on CM4.
Here is the definition for pT_ipcSendToCm4()
On CM4 this callback function gets called
I have a global int named i which is initialized to 0.
If I have the following code in the callback function:
I see the light on the device flashing blue and green, which is as expected, since i is incremented every time we send a message from CM0+.
However, if I have this code in the callback function:
And this code in the main loop of CM4:
The light on the device stays green and does not change, as if i is not being changed at all. I tested changing different global variables inside an ipc pipe callback function. I observed that the changes to the variable are reflected in the callback function but nowhere else within the scope of CM4.
Why is this happening? Is there something different about the IPC pipe interrupt from other interrupts? How is the memory being handles in this case?
UPDATE: I worked around this issue by declaring all of the memory on CM0 and passing pointers to CM4. So all the memory that M4 uses are statically declared on M0.Show Less
We have discovered a problem with the lwip library in ModusToolbox 2.0, 2.1, 2.2 and 2.3. It occurs when creating a new Wi-Fi project or updating the lwip library in an existing project. The problem is reported as a fatal error.
fatal: unable to access 'https://git.savannah.nongnu.org/git/lwip/': SSL certificate problem: certificate has expired
There is a defect in versions of OpenSSL prior to 1.1.0 which, as of September 30, causes web accesses with the Let's Encrypt intermediate certificate (Let's Encrypt R3) to fail. Let's Encrypt R3 contains signatures from two roots: DST Root CA X3 and ISRG Root X1. As explained by Let’s Encrypt (DST Root CA X3 Expiration), the former certificate has expired but the latter remains trusted. The defective versions of OpenSSL require both certificates to be trusted and erroneously deny the access.
OpenSSL 1.1.0 is used by the modus-shell utility on Windows hosts in all versions of ModusToolbox. The soon-to-be released ModusToolbox 2.4 shall include a newer version of OpenSSL to correct the problem.
To safely and reliably access lwip from ModusToolbox 2.3 and earlier, follow these steps to remove the expired certificate.
- Open the file ~\ModusToolbox\tools_2.x\modus-shell\etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem in a text editor
- Search for the line beginning with the comment "# DST Root CA X3"
- Delete that line and the associated certificate - including the "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----" lines.
The Open Documentation Team is looking for a few great beta testers. People interested in a single place to find their documentation and a place where it will be updated on their feedback. The Cypress Community has always been a place of collaboration with you, our users, and we’d like to extend an invitation to give us feedback on this new platform between now and January 10th, 2021.
The first documentation platform we’re opening is for PSoC 6 and AnyCloud customers and offers all the documentation you, the developers, need in one place. The Open Documentation platform allows users to find all the development documentation in one place, complete with real-time updates from our software and support teams based on inputs and questions from our developer community. This creates a responsive, easier to use platform for you to find everything throughout your development process.
This platform will host the latest version of the documentation along with continuous updates from our support organization based on questions from you, our Community members. We look forward to hearing your feedback on this beta PSoC 6 and AnyCloud book and collaborating with you on better documentation going forward.
Jump over and test out the PSoC 6 and AnyCloud platform here.
Let us know here what you think of the platform. Test out the in-documentation feedback tool too. We’d love to hear any other documentation books you would like us to build.
Thank you for being a part of our commitment to continually improving our developer experience! I appreciate your help in making this the best tool we can.
Digital Technologies TeamShow Less
we want to updated the firmware though the UART interface , can you help to provide the IAP demo code of PSOC62? TKS;Show Less
it’s been noticed that we cannot seem to “Export to IDE” these projects. I suspect this might be because of the use of the PDL for the PSoC 6 units. Our customers will require that we meet MISRA-C requirements and be able to prove it, thus we need to use a static code checker. We use the IAR Workbench to run our static code analysis on our projects. We have been able to export projects just fine with the PSoC 5, but the PSoC 6 projects gives us the following message no matter what I’ve tried:Show Less
The latest version I see is V2.20 in PSoC Creator. Is there a newer version with Simple Mode which doesn't use 2x the amount of flash requested as stated in this post 1 year ago?Show Less