PSoC Creator News and Information | Cypress Semiconductor
I collected all the questions that you asked us at Alan's video workshop the other day, made sure the answers made sense, reordered them into a somewhat sensible arrangement, and put them into an FAQ. It is attached, below, in the downloadable file "Bluetooth Mesh Video Workshop FAQ.pdf". Hope you find it useful!
We had a really successful workshop on Wednesday this week. Plenty of people attended and Alan kept them all engaged with his knowledge, humor, and famous dancing skills. He programmed a bunch of Cypress CYBT-213043-MESH kits to be lights and switches, created networks and rooms (aka groups), then controlled LEDs via buttons on the (switch) kit
Back in February I committed to write about peripheral setup using the ModusToolbox device configurator tool. I have not done very well! We have had another release since then - ModusToolbox 1.1 - and I have been buried in planning for the 2.0 release and training our internal teams. But that is real work and I've had enough of it. It's time to
Here's another tidbit from the Embedded World show. Zerynth have ported their Virtual Machine to PSoC 6 and it opens the world of IoT to millions of Python programmers. And we are not talking about a watered-down
Last time I blogged (is that really a word? what a strange world this is) I wrote about the ModusToolbox device configurator. We set up a pair of pins, one called "LED" and the other "SW" (because, it turns out that I am too lazy to write "Switch" or "Button"). Anyway, I mentioned that the configurator generates the setup code for the pins and
I have recently shown you two of the most helpful starter templates in ModusToolbox - PioneerKitApp and PioneerKitAppFreeRTOS. Just as an FYI, if you have the PSoC 6 prototyping kit instead, there are equivalent templates for that kit called ProtoKitApp and ProtoKitAppFreeRTOS. All of these templates set up some kit basics for you so that you
No fibbing here... last night I woke up around 4am thinking "they're words"!!!!! As in 32-bit words, not 8-bit bytes. Yesterday I wrote about increasing the FreeRTOS stack size "for the OS to do anything interesting". It turns out that the 1kB stacks I was using were actually 4kB. And the original 16kB allocation of SRAM to FreeRTOS is actually
- 1 of 2
- next ›
ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.
Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.