PSoC™ 6 Forum Discussions
I can’t uplink code to my kit. I had follow all the steps to register the kit, virtualize with two version of VM available,use degins spark account, use different versions of zerynth, try windows and linux, update kitprog to version 2, etc.
The only answer i had possibly found was that my psoc 6 firmware ir out of date.
As i saw in this blog:
https://www.element14.com/community/roadTestReviews/3039#jive_content_id_Zerynth_Physical_Device_Detection_Issues
They said that:
*
Zerynth will not work with this kit if its PSoC62 mcu has outdated firmware so make sure your kit doesnt show any outdated firmware warning in PSoC programmer.
*
And when I use modustoolbox to program my PSoC or read the binaries from PSoC Programmer i get the following message:
*******************************************************************************
* Your PSoC6 KIT is out of date. Please contact Cypress to get a replacement. *
*******************************************************************************
I look for the error on other community post, https://community.cypress.com/docs/DOC-16171, and it says:
PSoC 6 MCU on some of the early PSoC 6 BLE Pioneer Kit (CY8CKIT-062-BLE) and PSoC 6 WiFi-BT Pioneer Kit (CY8CKIT-062-WiFiBT) has an older version of FlashBoot. Those development kits with the old version of FlashBoot are incompatible with the latest ModusToolbox™ IDE and may cause a programming failure.
If you are using one those early development kits with ModusToolbox IDE, and you see the below message while programming the kit, it means that the FlashBoot on your kit is out of date.
This is the only thing i can relate with this programming issue, that the FlashBoot its out of date because the version of my kit is an early one, cause i bought it two years ago.
It would be really grateful if you guys can solve this!
Show LessThe datasheet of PSoC6 describes that it is possible to execute code from the code and the sram regions.
Are there any code examples available for executing a whole program in the SRAM?
Many thanks,
Nadja
Show LessHello Community,
I've tried the I2S example(CE218636) on Psoc 6 platform (CYC8CKIT-062-WIFI-BT). It works well. I can hear 'Psoc Rocks' after pressing SW2 button. The audio file is converted to an array and is stored in wave.c file. How is this file generated?
I want to play my own sound tracks using Psoc 6 platform. I'm interested in knowing how to convert the sound files(mp3, wav) to an array to be used in Psoc 6 platform.
It would be nice to know how to reverse convert C array file to audio source to test the algorithm.
Thank you
Dheeraj
Show LessI use google translation, forgive my gibberish
I am compiling under keil5 using the following code
https://github.com/cypresssemiconductorco/psoc6pdl.git
https://github.com/cypresssemiconductorco/psoc6hal.git
https://github.com/cypresssemiconductorco/TARGET_CY8CPROTO-062S3-4343W.git
link file use:
TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct
But the link is wrong
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(106): error: L6226E: Missing base address for region LR_IROM.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(106): error: L6292E: Ignoring unknown attribute 'FLASH_START' specified for region LR_IROM.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(106): error: L6292E: Ignoring unknown attribute 'FLASH_CM0P_SIZE' specified for region LR_IROM.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(108): error: L6292E: Ignoring unknown attribute 'FLASH_CM0P_SIZE' specified for region .cy_m0p_image.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct: Error: L6630E: Invalid token start expected number or ( but found F at position 11 on line 116
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct: Error: L6629E: Unmatched parentheses expecting ) but found F at position 11 on line 116
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct: Error: L6226E: Missing base address for region LR_IROM1.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(116): error: L6292E: Ignoring unknown attribute 'FLASH_START' specified for region LR_IROM1.
..\cypress_psoc6\TARGET_CY8CKIT-062S2-4343W\linker\TOOLCHAIN_ARM\cy8c6xxa_cm4_dual.sct(116): error: L6228E: Expected '{', found '+...'.
Not enough information to list image symbols.
Not enough information to list load addresses in the image map.
Finished: 2 information, 0 warning and 9 error messages.
".\obj\awtk.axf" - 9 Error(s), 0 Warning(s).
I need a demo or help
Thanks
Hi All!
I have a very strange situation in debug mode. If I create a new project, or write new lines of code in older ones, my code looks like dead to the project. The debugger steps through my lines either i use "step into"(F11) or "step over"(F10) commands. I tried to toggle breakpoints to the new lines, but it didnt work. Never seen like this before, please help me!
Device: CYBLE-416045-02
Show LessWhat is the latest schedule for CAN bus support for PSoC 6?
Cypress' Roadmap shows CAN bus support is all four base lines of PSoC 6 starting in Q219.
Reference Slide 3 in Version T of Cypress PSoC® and Microcontroller (MCU) Portfolio Roadmap @ https://www.cypress.com/product-roadmaps/cypress-psoc-and-microcontroller-mcu-portfolio-roadmap
Note: If Cypress is planning to support CAN bus in PSoC 6, please update the response in https://community.cypress.com/thread/43517, which was written before the Roadmap was released.
Greg
Show LessHi,
I am having a hard time getting my project to compile with my desired source tree.
My source tree looks like follows
/modules
---/lib1
------/include/lib1
------/source
---/lib2
------/include/lib2
------/source
/src
----/CreatorProject (and the normal directory structure for a creator project)
I am adding additional include directories as: -I ../../../modules/lib1/include ../../../modules/lib1/source
And then I am including them in my project source as:
#include <lib1/lib1header.h>
Creator is correctly seeing the header files, and so it is getting the function declarations as expected.
The problem is that GCC cannot find the function definitions, which means it isn't compiling the /source files.
I tried adding an Include library directory to the Linker, but obviously these aren't external libraries which need to be linked, they are source files that should be compiled. There isn't any option to add additional compilation targets through the build settings as far as I can tell. And I don't think there is any way to do file globbing through the gcc command line, so I don't think so it isn't as simple as adding "../../../modules/lib1/source/*.c"
If I add the files directly to my workspace (one source file at a time) it will compile correctly. This is however tedious and cumbersome, since some of these external libraries are heavily nested with a lot of .c files in many different folders, and I can't simply add an entire directory structure as far as I can tell.
So basically I can't figure out how to get it to see the /source files of each external module and compile those.
Thanks for any input!
Show LessThe latest version of AN213924 available from cypress.com states the following for PSOC 6 DFU SDK command 'Enter DFU'
B.2.1 Enter DFU
Begins a DFU operation. All other commands except Exit DFU are ignored until this command is received. Responds
with device information and DFU SDK version.
- Input
- Command Byte: 0x38
- Data Bytes:
▪ 4 bytes (optional): product ID. If these bytes are included, and they are not 00 00 00 00, they are
compared to device product ID data.
- Output
- Status/Error Codes:
▪ Success
▪ Error Command
▪ Error Data, used for product ID mismatch
▪ Error Length
▪ Error Checksum
- Data Bytes:
▪ 4 bytes: Device JTAG ID
▪ 1 byte: Device revision
▪ 3 bytes: DFU SDK version
This should result in a command packet structure with a data length of 4 but if sent this way it is not accepted by the DFU, which returns code ERROR_LENGTH .
In reviewing the log from Cysmart when performing a firmware update, an example of the actual packet sent is as follows:
[01:38:06:00:04:03:02:01:00:00:B7:FF:17]
This shows a data length of 6 bytes, not 4 as written in the documentation. An extra 2 bytes of 00 00 is being included in the data packet. Does anyone have access to a more recent version of the DFU documentation or is this just a case of documentation not being updated?
Show LessHi ,
I found that the CY8CPROTO-062-4343W DVK have the TF card reader. The HW selection is using P13_5 (R61 default) as Card_Detect, but in the MTB1.1 Device Configure and Pinout of Card_Detect is P12_1 (R62 NC).
Do I need to change the resistor to R62 by hand work?
Regards,
Ray
Show LessHello,
I have a question about implementing a proximity sensor using a loop wire attached to a GPIO pin on the PSoC CYBLE-416045-02. I have set up a CapSense block and configured it as a proximity sensor then built the project and wrote the attached code. It is set up so that an LED turns off when the proximity widget is active. Having trouble getting the code to work. Any ideas on what is going wrong? Thanks!
Show Less