PSoC™ 6 Forum Discussions

Dear Receiver,

As the attached picture shows, I have 4 ADC channels to measure different analog signals. (Volatge, Current, Temperature and Humidity). So I go to HAL library Hardware Abstraction Layer (HAL) (infineon.github.io)

In the HAL library, there are 4 snippets for references. I felt confused about the snippet 1 and snippet 2.

Initially, I follow snippet 1 to add ADC channels step by step. (From pin 10_0 to pin 10_3...)

But someone told me you need to follow snippet 2. Because snippet 2 is for multi-channels usage.

So I feel confused now.

Which  snippet 1 or  snippet 2 is the correct steps to add ADC channels ?!

Thank you so much.

I have a memory seeing an UDB based SDIO controller for some old psoc6 + wifi ev-kit. 

basically I'm after a sd-card implementation in UDB

I am trying to read the ADC values of 2 pins, and there are other pins which am using for other purposes, i want all the pins to be initialized and ADC to work. But my ADC pins are not initializing, But all the other pins are initialized successfully. I want all the pins to be working simultaneously.  I have attached the code please refer it.

Am using the CY8C6245LQI-S3D72 BSP.

1、I am  using  CY8C6244LQI-S4D82 now

2、I  want to encrypt the  program  to prevent theft 

你好 我现在用的  CY8C6244LQI-S4D82  ，如果 其他人 盗取     芯片程序，然后 反编译，有什么措施来防止这些吗 ？

不胜感激

Hello,

I have installed the latest version of the ModusToolbox and try to create a "New Application".

Usually I should get a list of kits for selecting the one I want to use. But unfortunately the process stops with the following error message:

Loading the manifest data
Found environment variable CyManifestLocOverride=C:/Users/unitj001/.modustoolbox/manifest.loc
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'
Starting to parse super manifest with URL 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Finished parsing super manifest with URL 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Downloading manifest file 'https://github.com/Infineon/mtb-ce-manifest/raw/v2.X/mtb-ce-manifest.xml'
Downloading manifest file 'https://github.com/Infineon/mtb-ce-manifest/raw/v2.X/mtb-ce-manifest-fv2.xml'
...
Finished download of file 'https://github.com/memfault/mtb-memfault-mw-manifest/raw/main/mtb-memfault-mw-manifest-fv2.xml'
Finished download of file 'https://github.com/sensiml/sensiml-mw-manifest/raw/main/sensiml-mw-manifest-fv2.xml'
Finished loading the manifest data (2133 ms)
Loading the device db
fatal: unable to access 'https://github.com/Infineon/device-db/': error setting certificate verify locations: CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none
INFO:Using the executable path for the tools directory.
ERROR:there was an error retreiving the asset 'https://github.com/Infineon/device-db' commit 'release-v4.3.0' - fatal: unable to access 'https://github.com/Infineon/device-db/': error setting certificate verify locations: CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none
ERROR:Global asset download of device-db loading completed with error.
ERROR:The asyncStepComplete failed for LoadFlag DEVICE_DB.
3 error(s), 0 warning(s)

I think that I followed the installation guide correctly.

I've set the environment variables like this:

The different directories do exist, but the manifest.loc file does not.

The problem occurs with and without VPN connection on my company notebook (Windows 10).
I don't have any problems on my private notebook (Windows 11).

Is there anything else I should check?

Hello,

just wanted to let cypress/infineon and the community know that there is an linker/makefile-config mismatch of the CY_CORTEX_M4_APPL_ADDR which leads to a crash / not starting of the CM4 core. 

In contrast to definitions of the other boards, the following directory lacks a COMPONENT_CM4/*/linker.ld file, so that the default of FLASH_CM0P_SIZE of 0x20000 is used:

https://github.com/Infineon/mtb-example-psoc6-dual-cpu-empty-app/tree/master/templates/TARGET_CY8CPROTO-063-BLE

The Makefile in proj_cm0p/Makefile states:

DEFINES+=CY_CORTEX_M4_APPL_ADDR=CY_FLASH_BASE+0x4400U

so the CORTEX_M4_APPL_ADDR is calculated wrong ( it should be 0x20000U).

https://github.com/Infineon/mtb-example-psoc6-dual-cpu-empty-app/blob/master/proj_cm0p/Makefile

It took me some time to find this bug. I hope it will be corrected soon by adding a COMPONENT_CM4/*/linker.ld file to the git.

Greetings,

 Matthias