Hi,

I have a PSOC 4200M project that was working and debugging well.  A change must have been made, because all of the sudden, I could not reach any breakpoints, even right inside the main() method.  They never seem to be reached, but instead the software goes to a disassembly window instead.

I have never seen this before.  I tried to turn off the disassembly window in Tools>Options, but then a window just pops up informing me that there is no source to debug, and would I want to see the disassembly window.

Please help if you have encountered this before, I am stuck.

I would rather not post my whole project if possible, if there are snippets or screenshots I would be happy to show those.

Thank you,
Tom

I'm trying to learn if I can make a very slow clock without using up UDB/counters, etc.  The PSoC® 3: CY8C34 Family Datasheet says:

Each clock divider consists of an 8-input multiplexer, a 16-bit
clock divider (divide by 2 and higher) that generates ~50 percent
duty cycle clocks, master clock resynchronization logic, and
deglitch logic. The outputs from each digital clock tree can be
routed into the digital system interconnect and then brought back
into the clock system as an input, allowing clock chaining of up
to 32 bits.

I can make a Clock component and it will use one divider up to 65536 to produce it, but how do I then route it back through another divider?

I'm trying to become more acquainted with DMA resources and API calls.

I'm looking to change a DMA channel TD after it was previously initialized.

I found the CyDmaTdGetConfiguration() and CyDmaTdGetAddress() functions in the API section of the datasheet.

I've tried some code with these functions but I basically get useless information.

Are there any examples of using these functions for changing the TD parameters?

Hi,

can anyone pls help.

When was this part obsolete? when was the last time buy?

I still have 2019 year of manufact.  is it ok?

Best regards

Paolo

I got the USBUART example working, but all that does is show up as a COM port and echo characters back to the computer.  Is there a bridge example, so it shows up as a COM port, but passes the characters through to a hardware UART component, out of a hardware pin, and vice versa?

Issue:
We want to use external flash memory with a bootloader.

We tested firmware which is modified from https://github.com/cypresssemiconductorco/mtb-example-psoc6-mcuboot-basic .

We tested our firmware with CY8CKIT-062S2-43012, which has S25FL512SAGMFI010 and it works.

Because of procurement, we want to change the flash memory to S25FL512AGMFA010.

We changed the flash memory chip on CY8CKIT-062S2-43012 from S25FL512SAGMFI010 to S25FL512AGMFA010, which is bought from Digi-Key, then firmware can not read/write the flash memory.

Detail:
It looks like the chip does not respond to 4QIR(0xEC) command.
Attached are screenshots of the oscilloscope during the read cycle.
In case of S25FL512SAGMFI010, IO0(yellow), IO1(cyan), IO2(purple), IO3(green) ,SS(digital 0), and CLK(digital 1) work well.

However, In case of S25FL512AGMFA010, after command and address are specified, IO0..4 bus are looked to be released.

During command(0xEC) and address specification(0x00f0 using 4bits), waveform are driven from PSoC appropriately.

Howerver, the duration flash memory is expected to response data, no signal response, and decreasing exponentially before CS is deserted.

PSoC firmware is completely the same for both cases. Only chip change.

Question:
What is the difference between S25FL512SAGMFI010 and S25FL512AGMFA010?
Is any factory initialize required to use S25FL512AGMFA010?
How to solve our issue?

Hi,

sorry for the stupid question but this is my first time with Cypress ecosystem and also I'm not a professional firmware developer.

When I use ModusToolbox, the available template projects don't include the Audio Sink app, but the project README (https://github.com/cypresssemiconductorco/mtb-example-btsdk-audio-a2dp-sink) has a section named "List of boards available for use with BTSDK", which includes my eval board.

My understanding is that the board is compatible with the btsdk, that means I have access to functions like "wiced_audio_sink_configure" (https://cypresssemiconductorco.github.io/btsdk-docs/BT-SDK/20706-A2_Bluetooth/API/group__wicedbt__a2dp.html#ga9b28e8751a80b34db1b9c2123ba6a06f) that allow me to configure and eventually use the audio functionality of the chip, but the example project for some reason is not compatible with it.

Am I correct? Can somebody help? Many thanks, Davide

Hi,

this is a follow-up to a previous post on placing a PSoC right under a CSX touchpad in applications with limited space.

I have a first iteration of such a design, but there are a few things I worry may affect the signal quality of the touchpad. It is made out of 2 PCBs linked together with castellated holes. The first PCB is the PSoC module with castellated holes, and the second one is the touchpad, with mounting pads to solder the module on top.

Here is a view of the stackup to better understand the intended device

The capsense pcb has 4 layers: 2 first are for the touchpad, the 3rd has a ground hatch to protect signal integrity, and bottom layer has  the pads for the castellated holes.

1. The PSoC PCB could be 2 layers, but I made it 4 just so I could add a second hatch ground to isolate capsense signals even more. Is this a good thing, or I just risk stealing to many field lines from capsense to ground?

In the image below, we can see my TX lines and their filtering resistors close to the RX lines, and close to the star ground

2. Now, should I move the TX lines closest to the star ground, increasing the distance from RX lines, or move them closer to the RX lines and separate them with a trace connected to VSS capsense?

3. Another point I want to address is how sensitive and critical are the CIntX capacitors. in the image below, we see that I have I2C lines moving right next to the  CIntA and CIntB capacitors.

can this be an issue? should I keep fast signals away from the capacitors? the space limitation pretty much forces me to do so. I also placed a via for each of the 2 CIntX capacitors, and this eats away a little bit of space. Could I join the 2 capacitors to the save via like so?

4. I did not put a single ground or power plane on the PCB, to prevent field line sinking on the touchpad. Could this be an issue given that the ground comes from supply and follows a single trace all the way to the star ground?

Thanks a lot!

Hello,

I have a few questions about CY7C65631 chip.

I need a high-speed 4-port USB hub chip to connect to raspberry pi unit.

My first question is about compatibility with Linux. I am kind of nervous about compatibility issues. Is there any compatibility issue between CY7C65631 and linux?

Secondly, I am kind of confused about programming eeprom connected to CY7C65631. How is it actually programmed? Do I have to pre-program before soldering the EEPROM or is it programmed through the hub via USB?  Is it OK to completely omit the EEPROM? If you can provide me with any compatible EEPROM manufacturer number I would appreciate it.

Lastly, I'd like to know if I can use an oscillator to run the chip instead of crystal. What should be the voltage level of the oscillator? There aren't any guidelines about the clock pins.

Thanks in advance.

Hi everyone,

I got a Posc64 ，and getting  step by step by  Getting start with the Cypress CY8CKIT-064S0S2-4343W

(https://docs.aws.amazon.com/freertos/latest/userguide/getting_started_cypress_psoc64.html).

Now, I am in  step"Build and run the FreeRTOS Demo project".

I would like to perform " Build aws_demos Application" (use Modustoolbox IDE) on  my project (aws_demos)  ，

and occur some errors in the below context used bold text，and you can see the errors are similar .

How should I solve this problem?

---------------------------------------------------------------------------------------------------------------------------------------

11:34:32 **** Incremental Build of configuration Debug for project aws_demos ****
"C:\\Users\\Mike\\ModusToolbox\\tools_2.3\\modus-shell\\bin\\make" CY_MAKE_IDE=eclipse CY_IDE_TOOLS_DIR=C:/Users/Mike/ModusToolbox/tools_2.3 CY_IDE_BT_TOOLS_DIR= -j2 all
Tools Directory: C:/Users/Mike/ModusToolbox/tools_2.3
CY8CKIT_064S0S2_4343W.mk: ../../../../../vendors/cypress/boards/CY8CKIT_064S0S2_4343W/aws_demos/application_code/cy_code/CY8CKIT_064S0S2_4343W.mk

Prebuild operations complete
Commencing build operations...

Tools Directory: C:/Users/Mike/ModusToolbox/tools_2.3
CY8CKIT_064S0S2_4343W.mk: ../../../../../vendors/cypress/boards/CY8CKIT_064S0S2_4343W/aws_demos/application_code/cy_code/CY8CKIT_064S0S2_4343W.mk

Initializing build: aws_demos Debug CY8CKIT_064S0S2_4343W GCC_ARM

Auto-discovery in progress...
-> Found 249 .c file(s)
-> Found 42 .S file(s)
-> Found 18 .s file(s)
-> Found 0 .cpp file(s)
-> Found 0 .o file(s)
-> Found 24 .a file(s)
-> Found 600 .h file(s)
-> Found 0 .hpp file(s)
-> Found 0 resource file(s)
Applying filters...
Auto-discovery complete

Constructing build rules...
Build rules construction complete

==============================================================================
= Building application =
==============================================================================
Generating compilation database file...
-> C:/Users/Mike/amazon-freertos/build/cy/aws_demos/compile_commands.json
Compilation database file generation complete
Building 521 file(s)
C:/Users/Mike/ModusToolbox/tools_2.3/gcc/bin/arm-none-eabi-objcopy -R .cy_sflash_user_data -R .cy_toc_part2 C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/aws_demos.elf C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.elf; C:/Users/Mike/ModusToolbox/tools_2.3/gcc/bin/arm-none-eabi-objcopy -O ihex C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.elf C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.hex; cp "../../../../../vendors/cypress/MTB/psoc6/psoc64tfm/COMPONENT_TFM_S_FW/tfm_s_unsigned.hex" "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0.hex"; cysecuretools --policy "../../../../../vendors/cypress/MTB/psoc6/psoc64tfm/security/policy/policy_multi_CM0_CM4_jitp.json" --target "cy8ckit-064s0s2-4343w" sign-image --hex "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0.hex" --image-type UPGRADE --image-id 1; cysecuretools --policy "../../../../../vendors/cypress/MTB/psoc6/psoc64tfm/security/policy/policy_multi_CM0_CM4_jitp.json" --target "cy8ckit-064s0s2-4343w" sign-image --hex "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.hex" --image-type UPGRADE --image-id 16; cp "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0_unsigned.hex" "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0.hex"; cp "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4_unsigned.hex" "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.hex"; cysecuretools --policy "../../../../../vendors/cypress/MTB/psoc6/psoc64tfm/security/policy/policy_multi_CM0_CM4_jitp.json" --target "cy8ckit-064s0s2-4343w" sign-image --hex "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0.hex" --image-type BOOT --image-id 1; cysecuretools --policy "../../../../../vendors/cypress/MTB/psoc6/psoc64tfm/security/policy/policy_multi_CM0_CM4_jitp.json" --target "cy8ckit-064s0s2-4343w" sign-image --hex "C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4.hex" --image-type BOOT --image-id 16;
2021-06-18 11:34:36,595 : C : ERROR : Validation against schema failed. Check the log for details
2021-06-18 11:34:36,595 : C : ERROR : 'STATUS_PARTITION' is not one of ['SRAM_DAP', 'FLASH_PC1_SPM', 'FLASH_PC2', 'FLASH_PC3', 'FLASH_PC4', 'FLASH_MAIN_CODE', 'FLASH_MAIN_XO', 'FLASH_MAIN_DATA', 'FLASH_SUPERVISORY', 'FLASH_WORK_SECURE', 'FLASH_WORK', 'SRAM_PC0_PRIV', 'SRAM_PC0_PUB', 'SRAM_SPM_PRIV', 'SRAM_SPM_PUB', 'SRAM_PC1_PRIV', 'SRAM_PC2_PRIV', 'SRAM_PC3_PRIV', 'SRAM_PC4_PRIV', 'SRAM_MAIN', 'SMIF_CODE', 'SMIF_XO', 'SMIF_DATA', 'BOOT', 'UPGRADE']

Failed validating 'enum' in schema['properties']['boot_upgrade']['properties']['firmware']['items']['properties']['resources']['items']['properties']['type']:
{'enum': ['SRAM_DAP',
'FLASH_PC1_SPM',
'FLASH_PC2',
'FLASH_PC3',
'FLASH_PC4',
'FLASH_MAIN_CODE',
'FLASH_MAIN_XO',
'FLASH_MAIN_DATA',
'FLASH_SUPERVISORY',
'FLASH_WORK_SECURE',
'FLASH_WORK',
'SRAM_PC0_PRIV',
'SRAM_PC0_PUB',
'SRAM_SPM_PRIV',
'SRAM_SPM_PUB',
'SRAM_PC1_PRIV',
'SRAM_PC2_PRIV',
Error: Failed processing!
'SRAM_PC3_PRIV',
'SRAM_PC4_PRIV',
'SRAM_MAIN',
'SMIF_CODE',
'SMIF_XO',
'SMIF_DATA',
'BOOT',
'UPGRADE'],
'id': 'type',
'required': True,
'type': 'string'}

On instance['boot_upgrade']['firmware'][0]['resources'][3]['type']:
'STATUS_PARTITION'. Check the log for details
2021-06-18 11:34:36,596 : C : ERROR : Policy validation finished with error. Check the log for details
2021-06-18 11:34:37,091 : C : ERROR : Validation against schema failed. Check the log for details
2021-06-18 11:34:37,091 : C : ERROR : 'STATUS_PARTITION' is not one of ['SRAM_DAP', 'FLASH_PC1_SPM', 'FLASH_PC2', 'FLASH_PC3', 'FLASH_PC4', 'FLASH_MAIN_CODE', 'FLASH_MAIN_XO', 'FLASH_MAIN_DATA', 'FLASH_SUPERVISORY', 'FLASH_WORK_SECURE', 'FLASH_WORK', 'SRAM_PC0_PRIV', 'SRAM_PC0_PUB', 'SRAM_SPM_PRIV', 'SRAM_SPM_PUB', 'SRAM_PC1_PRIV', 'SRAM_PC2_PRIV', 'SRAM_PC3_PRIV', 'SRAM_PC4_PRIV', 'SRAM_MAIN', 'SMIF_CODE', 'SMIF_XO', 'SMIF_DATA', 'BOOT', 'UPGRADE']

Failed validating 'enum' in schema['properties']['boot_upgrade']['properties']['firmware']['items']['properties']['resources']['items']['properties']['type']:
{'enum': ['SRAM_DAP',
'FLASH_PC1_SPM',
'FLASH_PC2',
'FLASH_PC3',
'FLASH_PC4',
'FLASH_MAIN_CODE',
'FLASH_MAIN_XO',
'FLASH_MAIN_DATA',
'FLASH_SUPERVISORY',
'FLASH_WORK_SECURE',
'FLASH_WORK',
'SRAM_PC0_PRIV',
'SRAM_PC0_PUB',
'SRAM_SPM_PRIV',
'SRAM_SPM_PUB',
'SRAM_PC1_PRIV',
'SRAM_PC2_PRIV',
'SRAM_PC3_PRIV',
'SRAM_PC4_PRIV',
'SRAM_MAIN',
'SMIF_CODE',
'SMIF_XO',
'SMIF_DATA',
'BOOT',
'UPGRADE'],
'id': 'type',
'required': True,
'type': 'string'}

On instance['boot_upgrade']['firmware'][0]['resources'][3]['type']:
'STATUS_PARTITION'. Check the log for details
2021-06-18 11:34:37,092 : C : ERROR : Policy validation finished with error. Check the log for details
Error: Failed processing!
cp: cannot stat 'C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm0_unsigned.hex': No such file or directory
cp: cannot stat 'C:/Users/Mike/amazon-freertos/build/cy/aws_demos/CY8CKIT_064S0S2_4343W/Debug/cm4_unsigned.hex': No such file or directory
2021-06-18 11:34:37,605 : C : ERROR : Validation against schema failed. Check the log for details
2021-06-18 11:34:37,605 : C : ERROR : 'STATUS_PARTITION' is not one of ['SRAM_DAP', 'FLASH_PC1_SPM', 'FLASH_PC2', 'FLASH_PC3', 'FLASH_PC4', 'FLASH_MAIN_CODE', 'FLASH_MAIN_XO', 'FLASH_MAIN_DATA', 'FLASH_SUPERVISORY', 'FLASH_WORK_SECURE', 'FLASH_WORK', 'SRAM_PC0_PRIV', 'SRAM_PC0_PUB', 'SRAM_SPM_PRIV', 'SRAM_SPM_PUB', 'SRAM_PC1_PRIV', 'SRAM_PC2_PRIV', 'SRAM_PC3_PRIV', 'SRAM_PC4_PRIV', 'SRAM_MAIN', 'SMIF_CODE', 'SMIF_XO', 'SMIF_DATA', 'BOOT', 'UPGRADE']

Failed validating 'enum' in schema['properties']['boot_upgrade']['properties']['firmware']['items']['properties']['resources']['items']['properties']['type']:
{'enum': ['SRAM_DAP',
'FLASH_PC1_SPM',
'FLASH_PC2',
'FLASH_PC3',
'FLASH_PC4',
'FLASH_MAIN_CODE',
'FLASH_MAIN_XO',
'FLASH_MAIN_DATA',
'FLASH_SUPERVISORY',
'FLASH_WORK_SECURE',
'FLASH_WORK',
'SRAM_PC0_PRIV',
'SRAM_PC0_PUB',
'SRAM_SPM_PRIV',
'SRAM_SPM_PUB',
'SRAM_PC1_PRIV',
'SRAM_PC2_PRIV',
'SRAM_PC3_PRIV',
'SRAM_PC4_PRIV',
'SRAM_MAIN',
'SMIF_CODE',
Error: Failed processing!
'SMIF_XO',
'SMIF_DATA',
'BOOT',
'UPGRADE'],
'id': 'type',
'required': True,
'type': 'string'}

On instance['boot_upgrade']['firmware'][0]['resources'][3]['type']:
'STATUS_PARTITION'. Check the log for details
2021-06-18 11:34:37,606 : C : ERROR : Policy validation finished with error. Check the log for details
2021-06-18 11:34:38,097 : C : ERROR : Validation against schema failed. Check the log for details
2021-06-18 11:34:38,097 : C : ERROR : 'STATUS_PARTITION' is not one of ['SRAM_DAP', 'FLASH_PC1_SPM', 'FLASH_PC2', 'FLASH_PC3', 'FLASH_PC4', 'FLASH_MAIN_CODE', 'FLASH_MAIN_XO', 'FLASH_MAIN_DATA', 'FLASH_SUPERVISORY', 'FLASH_WORK_SECURE', 'FLASH_WORK', 'SRAM_PC0_PRIV', 'SRAM_PC0_PUB', 'SRAM_SPM_PRIV', 'SRAM_SPM_PUB', 'SRAM_PC1_PRIV', 'SRAM_PC2_PRIV', 'SRAM_PC3_PRIV', 'SRAM_PC4_PRIV', 'SRAM_MAIN', 'SMIF_CODE', 'SMIF_XO', 'SMIF_DATA', 'BOOT', 'UPGRADE']

Failed validating 'enum' in schema['properties']['boot_upgrade']['properties']['firmware']['items']['properties']['resources']['items']['properties']['type']:
{'enum': ['SRAM_DAP',
'FLASH_PC1_SPM',
'FLASH_PC2',
'FLASH_PC3',
'FLASH_PC4',
'FLASH_MAIN_CODE',
'FLASH_MAIN_XO',
'FLASH_MAIN_DATA',
'FLASH_SUPERVISORY',
'FLASH_WORK_SECURE',
'FLASH_WORK',
'SRAM_PC0_PRIV',
'SRAM_PC0_PUB',
'SRAM_SPM_PRIV',
'SRAM_SPM_PUB',
'SRAM_PC1_PRIV',
'SRAM_PC2_PRIV',
'SRAM_PC3_PRIV',
'SRAM_PC4_PRIV',
'SRAM_MAIN',
'SMIF_CODE',
'SMIF_XO',
'SMIF_DATA',
'BOOT',
'UPGRADE'],
'id': 'type',
'required': True,
'type': 'string'}

On instance['boot_upgrade']['firmware'][0]['resources'][3]['type']:
'STATUS_PARTITION'. Check the log for details
2021-06-18 11:34:38,103 : C : ERROR : Policy validation finished with error. Check the log for details
Error: Failed processing!
make[1]: *** [../../../../../vendors/cypress/MTB/psoc6/psoc6make/make/core/build.mk:556: CY_BUILD_app_postbuild] Error 1
make: *** [../../../../../vendors/cypress/MTB/psoc6/psoc6make/make/core/main.mk:414: secondstage_build] Error 2
"C:/Users/Mike/ModusToolbox/tools_2.3/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_IDE_TOOLS_DIR=C:/Users/Mike/ModusToolbox/tools_2.3 CY_IDE_BT_TOOLS_DIR= -j2 all" terminated with exit code 2. Build might be incomplete.

11:34:38 Build Failed. 6 errors, 0 warnings. (took 5s.266ms)