Browse the Community
Discussion forum regarding ModusToolbox PSoC™ 6 SDK related topics.
Discussion forum regarding ModusToolbox with the AIROC™ Bluetooth SDK topics.
Discussion forum regarding ModusToolbox AWS IoT SDK topics.
Discussion forum regarding ModusToolbox Mbed SDK topics.
Discussion forum regarding ModusToolbox Any cloud SDK topics.
Discussion forum regarding ModusToolbox general topics.
USB_Audio_Device_FreeRTOS sample project of CY8CKIT_062S2_43012 is targeted for AK4954 codec. How to modify the project for WM8960 codec if the mezzanine card is CY8CKIT-028-SENSE?Show Less
We are developing a product that contains the CY8C6347 part using ModusToolbox v2.3.1 and we are running into issues when trying to create a boot loader that uses the "secure image" functionality as outlined in AN221111.
To start with we made a simple "bootloader" application that runs on the CM0+ core and launches our main application that runs on the CM4 core. For this the "Dual CPU IPC Pipes" (https://github.com/Infineon/mtb-example-psoc6-dual-cpu-ipc-pipes) example was used.
That version of our "bootloader" is operating correctly, however when we start to pull in the "secure image" functionality that are described in AN221111 (and in the examples from the PSoC Creator PDL distribution) we are encountering an error when building the CM4 application. The behavior that we are seeing is that after the CM0 project is compiled the build process appears to stall/hang for a minute or two. While this is happening the windows task manager shows perl process that is consuming a fair amount of CPU as well as 3+ GB of RAM. That process appears to succeed, but then when gcc tries to compile the `.c` file that the perl script generates it errors out due to running out of memory.
I'm guessing that what is going on is that since the "secure image" process requires use of the `TOC2` instances that reside in SFLASH which is at address 0x16007C00 is causing the .bin and .c files to be very large and that is what is causing the perl script to take so long to complete and what causes the compile to error out. The .bin file is 98,336KB and the .c file is 329,231KB. That size for the .bin file seems to correspond with the offset of the SFLASH TOC2 instances within the flash area.
Has this issue been encountered before? Are there any solutions/workarounds?Show Less
I am using the EZ-Serial Host API Protocol Library with the CYBT-343026-01.
App: 1.2.29 build 29
Stack: 5.2.0 build 22
I have a few modules that I re-flashed with EZ-Serial binary.
My procedure is to use ModusToolbox and flash the module with the Firmware_Upgrade_via_HCI application via the HCI UART. Then I use ClientControl to flash the module with the EZ-Serial Binary via the HCI UART.
The issue is, after I do this, all the modules have the same Bluetooth Device Address (MAC). I believe this is because the Firmware_Upgrade_via_HCI application has this line in the makefile.
Per the documentation, this will set a BDA for your device by combining the 7 hex digit device ID with the last 5 hex digits of the host PC MAC address.
My question is, how do I prevent this. I want each module to have a unique MAC, preferably the MAC they had before I reflashed EZ-Serial.
Dear Sirs and Madams,
We are using the LIN sample project on Github as a reference.
mtb-example-psoc4-lin-slave project URL
Using the "make getlibs" command and "make eclipse" command, We successfully built and confirmed the operation.
However, there is an unknown point in this project.
When We confirm for "Device configurator", it is not checked under "Peripherals" and "Pins".
If it is written in the "resource_ map.h" as shown below, is it possible not to check the corresponding "Peripherals" and "Pins" checkboxes in the device configurator?
For example, if you check the check boxes for pins P3, P3, P3, P3 and P2, it will not work properly.
Also, when We would like to use LIN communication in Modus Toolbox , is it possible to use it only if it is described by such a "resource_map.h"?
Please tell us about the relationship between "Device Configurator" and "resource_map.h" in the this "mtb-example-psoc4-lin-slave project".
I opened two USB_Audio_Device_FreeRTOS projects for two eval boards: CY8KIT-062S2-43012 and CY8CKIT-062-WIFI-BT.
CY8CKIT-062-WIFI-BT board works well. But Windows has "USB device not recognized" error for CY8KIT-062S2-43012. How to fix this error?Show Less
Hi i would like to implement the CYBT-231043-MESH chip into my own sensor system but i am having trouble finding developer's guide to utilising the chip. A couple of questions
1) Where can i find resources/guides for using the API? Are there some kind of tutorial besides the few examples here?
2) Is there support for using the chip as a gateway? Or do i need to get the PSoC for that?
3) Is fast provisioning with one node as the configuration client supported?
Previous projects have been developed with V2.2, and future projects are ready to be developed with V2.4.
Now these two versions of modus are installed on the same PC, but when opening the previous project build with Modus V2.2,it is found that Modus is compiled with V2.4 GCC. How can we solve the problem of the coexistence of the two versions?
I have a posc6 cm4 app that when I allocate just a few hundred more bytes of static variables, the linker fails.
The error is:
COMPONENT_CM4/TOOLCHAIN_GCC_ARM/cy8c6xx7_cm4_dual.ld:318 cannot move location counter backwards (from 08046878 to 08046800)
collect2.exe: error: ld returned 1 exit status
Ironically, the PROGBITS feature doesn't run if the linker fails, so you can't see unless you go back to the smaller size. When you do it prints:
| .data | 0x0800228c | 7820 |
| PROGBITS | 0x08004118 | 1 |
| .cy_sharedmem | 0x0800411c | 12 |
| .noinit | 0x08004128 | 15572 |
| .bss | 0x08007e00 | 255208 |
| .heap | 0x080462e8 | 1304 |
| .cy_app_signature | 0x100fff00 | 4 |
The variable I am trying to grow in an uninitialized struct with an member array, so it should be in the .bss section which is huge, so I suspect that general understanding is wrong. I can't figure out why the linker is failing or how to change it. All the advice on this forum does not appear relevant for Modus Toolbox 2. 4
I am using the DFU linker script (dfu_cm4_app1.ld) from the BLE DFU example.
Please suggest where to look and what to change.Show Less