PSoC™ 6 Forum Discussions
I was wondering if any one had an example of a servo (like a mg90 type) controlled by an app over ble?
I'm wanting two buttons one 0 degrees and one 180 degrees. Anyone have an example they could share? Seems there are very few servo examples or I don't know where to look.
Show LessI'd like to count cache misses but am unable to find any registers that might be useful.
The three Cache Status registers seem to just indicate cache tag status and not hit/miss rate.
/* FLASHC.CM4_CA_STATUS0 */
#define FLASHC_CM4_CA_STATUS0_VALID16_Pos 0UL
#define FLASHC_CM4_CA_STATUS0_VALID16_Msk 0xFFFFUL
/* FLASHC.CM4_CA_STATUS1 */
#define FLASHC_CM4_CA_STATUS1_TAG_Pos 0UL
#define FLASHC_CM4_CA_STATUS1_TAG_Msk 0xFFFFFFFFUL
/* FLASHC.CM4_CA_STATUS2 */
#define FLASHC_CM4_CA_STATUS2_LRU_Pos 0UL
#define FLASHC_CM4_CA_STATUS2_LRU_Msk 0x3FUL
Is cache profiling supported?
Kind regards,
Steve
Show LessWhere USB code example will be available for PSOC-6 series? We need Device and Host -FS
I have RF Project. RF receiver will be 100m distance between RF transmitter. Which communication block is better to use? Would you help me decide the communication block?
Show LessHow do I wake from Hibernate, WAKE pin 0-4 does not work? I have looked at the API code and all of the demo code. However, I can Hibernate, but the pin wake does not work.
Please help.
Show LessHello Team,
I am trying to build the example project provided in Modus Toolbox. My target device is: CYBLE-416045-02 .
I am getting following errors: (Sample project is also added below)
make --no-print-directory post-build
C:/Users/mehdi/ModusToolbox_1.1/tools/modus-shell-1.0/bin/bash --norc --noprofile C:/Users/mehdi/ModusToolbox_1.1/libraries/psoc6sw-1.1/makefiles/platforms/PSoC6_cm4_dual/cymcuelftool_postbuild.bash C:/Users/mehdi/ModusToolbox_1.1/tools/cymcuelftool-1.0/bin/cymcuelftool C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus Build\SPS_NEW_BOARD\EmptyPSoC6App_mainapp/psoc6_01_cm0p_sleep.elf C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus Build\SPS_NEW_BOARD\EmptyPSoC6App_mainapp/Debug/EmptyPSoC6App_mainapp.elf ARM_CM4
Script: cymcuelftool_postbuild
1: MCUELFTOOL_LOC : C:/Users/mehdi/ModusToolbox_1.1/tools/cymcuelftool-1.0/bin/cymcuelftool
2: CM0P_LOC : C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus
3: CM4_LOC : Build\SPS_NEW_BOARD\EmptyPSoC6App_mainapp/psoc6_01_cm0p_sleep.elf
4: MCU_CORE : C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus
Failed to move C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus to C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus_signed.elf.tmp
=========================================
== Application CM0+ Memory ==
=========================================
C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus_signed.elf: Failed to open C:\Users\mehdi\Desktop\WORK\Work\SPS_REP\PSOC6\Modus_signed.elf
Invoking: GNU ARM Cross Create Flash Image
arm-none-eabi-objcopy -O ihex EmptyPSoC6App_mainapp_final.elf EmptyPSoC6App_mainapp_final_manual.hex
c:\Users\mehdi\ModusToolbox_1.1\tools\gcc-7.2.1-1.0\bin\arm-none-eabi-objcopy.exe: 'EmptyPSoC6App_mainapp_final.elf': No such file
make: *** [EmptyPSoC6App_mainapp.hex] Error 1
Show LessHi!
I'm looking to implement an ECO crystal (24.576MHz to support proper I2S transmission on 48khz sample rate). In "AN218241 PSoC6MCU Hardware Design Considerations", page 8. the diagram shows that the ECO crystal shall be connected to P12_6 and P12_7 AND the pins grounded. I have only seen
similar practice in GHz circuits, not on MHz level, so I suspect the AN diagram is wrong. Can someone from Cypress please confirm the correct hardware connection and update the application note document for other people?
https://www.cypress.com/file/385701/download
Regards,
Ladislav
Show LessHi,
I added the "Emulated EEPROM" component into my PSoC6 design and after this the build consistently fails with:
App.elf: Merge error: Section 0x14000000 at App.elf overlaps section 0x14000000 from App_signed.elf, but it contains different data
The command 'C:\Program Files (x86)\Cypress\PDL\3.0.1\tools\win\elf\cymcuelftool.exe' failed with exit code '1'.
Looking in the .map file that was generated around 0x14000000 shows this:
cy_em_eeprom 0x14000000 0x1400
*(.cy_em_eeprom)
.cy_em_eeprom 0x14000000 0x10bd .\CortexM4\ARM_GCC_541\Debug\BLE_config.o
*fill* 0x140010bd 0x143
.cy_em_eeprom 0x14001200 0x200 .\CortexM4\ARM_GCC_541\Debug\Em_EEPROM_1.o
0x14001200 Em_EEPROM_1_em_EepromStorage
Before it was merely:
.cy_em_eeprom 0x14000000 0x10bd
*(.cy_em_eeprom)
.cy_em_eeprom 0x14000000 0x10bd .\CortexM4\ARM_GCC_541\Debug\BLE_config.o
Disabling the EEPROM component reverst the .map file change and build succeeds as before.
Further looking into the App.elf and App_signed.elf files:
App.elf:
Contents of section .cy_em_eeprom:
14000000 00000000 00000000 00000000 00000000 ................
...
140010b0 00000000 00000000 00000004 11 .............
App_signed.elf:
Contents of section .cy_em_eeprom:
14000000 00000000 00000000 00000000 00000000 ................
...
140010b0 00000000 00000000 00000004 11000000 ................
...
140013f0 00000000 00000000 00000000 00000000 ................
Clearly the signed ELF file has the emulated EEPROM data but the regular ELF does not.
Looking into it further, it seems that the ELF file for the M0 core only has the EEPROM data in the .cy_em_eeprom section but the M4 has both the BLE and EEPROM data and merging these two together is causing the problem.
I also created a fresh project with only these two components and got the same error.
Is there a correct way to fix this problem?
- Juha
Show LessI am using CY8CKIT-062-WIFI-BT kit with KitProg3 fw and I am unable enter into CMSIS-DAP mode with mass storage. Is there any other solution except downgrading to KitProg2 FW?
And when can we expect that these issues with KitProg3 fw will be solved?
Show Less