PSoC™ 6 Forum Discussions
Hello,
I am trying to reprovision the CY8CKEY-064S0S2-4343W for the AWS_IoT_OTA_MQTT Example and continue with the next commands.
I have ran the
cysecuretools -t CY8CKIT-064S0S2-4343W -p policy/policy_multi_CM0_CM4_tfm_dev_certs.json re-provision-device
and have received
"RE-PROVISIONING PASSED"
Can you please take a look at the Log File attached and let me know how to fix it ?
Thanks
Show Less
Hello everyone,
We have a product based on CY8C6347LQI-BLD52 module and the application is a dual core application with OTA support (has Laucher, Stack, and Application projects), developed in PsocCreator (with custom modified PDL files). We start again working on this project, but to my surprise, PSOC Creator is no longer able to load the project and of course the support for LQI chip is no longer there. Thus, I started to port the project to ModusTool box under Mac OS distribution. As I have read on the forum, the recreation of an OTA application with all 3 projects in Modus Toolbox is another challenge, but so far I wanted to make a simple application compilable and to try and run it on our custom board.
I have created a project with a custom BSP based on the CY8C6347LQI-BLD52 chip, I have selected PDL and not HAL for the drivers support and basically all the libraries that are added with an Empty Dual Core project. When I compile the project, I just get flash overflow error from the linker (even if the app has only the main.c) and I am not sure what to do. I have attached the project, but basically is the empty dual core example and the log from modus.
Can someone point me to a direction regarding this error? Is it a better idea to maybe use the BZI chip and try to load the code on the LQI one? (I can confirm that the BZI chip complies successfully with the empty app).
It seems that this is one of many questions that I will ask regarding the modus toolbox.
Thanks in advance,
Marian
Show LessMy project is using PSOC 6, PSOC Creator 4.4, and PDL 3.1.7. CM0P is running BLE and MCWDT. CM4 is running a few SCBs, ADC, MCWDT, PDM_PCM, and DMA.
I need to generate true random numbers, so I have just added the crypto initialization sequence just as demonstrated in the example project CE221295
I want this IRF5803D2TRPBF. Can you tell if it's a 1039+or 2039+through screen printing?
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-6/I-purchased-this-IRF5803D2TRPBF-Can-you-tell-if-it-is-a-1039-or-2039-through/td-p/645352
Show LessHello,
Please I need help, I am running ModusToolbox 3.1 on windows 10 and when I try to make a New Application, the Choose Board Support Package (BSP) - Project Creator 2.10 window shows the following messages along with two errors:
Loading the ModusToolbox Technology Packs and Early Access Packs
Finished loading the ModusToolbox Technology Packs and Early Access Packs (1 ms)
Loading the tools information
Finished loading the tools information (7 ms)
Loading the manifest data
Loading super manfiest files from all sources
Getting manifests from remote and/or local sources
Processing system manifest 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Downloading super manifest file 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Finished loading super manifest files from all sources
Finished download of file 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
WARNING:Error downloading 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml' -- Connection closed
ERROR:all super manifests were invalid, no data loaded
ERROR:Manifest loading completed with error.
2 error(s), 1 warning(s)
I tried all I can but still getting these errors! Please help.
Show LessCY8C6136BZI-F14用miniprog4接上去之后仍找不到芯片报错There was an error attempting to run the port acquire command. This is often a result of no supported devices being attached, or a device being used by another application. Ensure that everything is properly connected, and that no other application is using the device and try again.
Show Less请问大家,要烧录CY8C6136BZI-F14应该用什么编程器或者说从什么开发板上能把它的编程器掰下来用,目前现有的编程器似乎不兼容该芯片
I'm using the CyBLE 416045-02 module. I am currently unable to get the module to go into deep sleep.
I am using the single core M0 configuration due to needs on the M4 core. I have the "Use BLE low power mode" checked in Top Design. I have a 32 Mhz external crystal across 12.6 and 12.7 for the ECO. I have the PILO enabled and I'm driving the Clk_LF with the PILO.
I have it in Limited Discovery Mode with a Fast Advertising interval timeout of 10 seconds. In my BLE event handler CY_BLE_EVT_GAPP_ADVERTISEMENT_START_STOP I am setting a sleep flag if the advertisement state is stopped. I can see it hit this in the debugger after 10 seconds.
For testing, I'm not even enabling the M4 core. I'm just turning on starting the BLE stack and waiting for the sleep flag to get set, which it does, then I'm attempting to enter deep sleep by calling Cy_SysPm_DeepSleep(CY_SYSPM_WAIT_FOR_INTERRUPT);
I'm seeing some conflicting information about the extern watch crystal. Several places it says its required to use BLE low power mode but in the module datasheet it says " The external 32-kHz XTAL is optional, and the precision internal low-speed oscillator (PILO) can be used if precise timing is not required". Apparently this is because the PILO isn't available on most PSoC 6 modules. I don't have a WCO connected because we're using the PILO as stated above.
Any suggestions? Are there any example of a single core BLE controller/host where its going into deep sleep?
Show Less