PSoC™ 6 Forum Discussions

Hi all,

Somewhere in the documentation it says that CY_USING_HAL is enabled by default. So why don't the definitions from the device configurator for the pin assignments below "#if defined (CY_USING_HAL)" work? I have:

When I setup the freeRTOS example I get an error if I use "GREEN_LED".

If I replace "GREEN_LED" with "P8_3" it works, no errors or warnings. I tried looking for "#define CY_USING_HAL" but I didn't see it anywhere. So how/where is CY_USING_HAL enabled/defined?

Thanks

Thanks.

Xin chào!
Tôi đang làm chương trình đọc cảm biến DHT11 bằng Modus Toolbox và sử dụng bộ PSoC 063 BLE, tôi đã thử một số thư viện của cảm biến DHT11, tuy nhiên, nó không hoạt động, tôi đang tìm một thư viện tốt! Mong mọi người giúp đỡ!
Cám ơn!

I need to add a proximity sensor in the black identification part of the photo to realize proximity sensing. The wire on the film is made of carbon film or silver wire connected to the gold finger at the upper right corner, the gold finger connected to the PCB hard board, and the IC placed on the PCB. What are the requirements for this length of wiring?

Hello friends!
I am referencing the ADC_basic example of Modus Toolbox to see how to read the ADC, I wonder how when I attach my sensor, the ADC will read the value and convert the voltage value read from the sensor. turned into a percentage value!

Thanks!

I have an application where a SPI based external ADC is used (using ModbusToolbox for development), using the HAL libraries for SPI interface.

The application works fine, until I add LittleFS library to store files/data to a QSPI based serial flash.

The ADC SPI tranfer calls seem to be stuck in the transfer_async where it is waiting for the interrupt.

It appears that LittleFS library (or underlying serial-flash) library might be conflicting with the SPI calls.

My issues seems to be similar to this ticket, but I don't know where to look for conflicting interrupt handlers.

Any suggestions are welcome.

I am trying to run a gesture classification demo on the CY8CKIT-062S2-43012 kit. I am following the steps described in https://github.com/Infineon/mtb-example-ml-gesture-classification.

But as try to import the example using New Application link in the Quick Panel I run into the below error and can not download the example. I have tried both methods described in the https://community.infineon.com/t5/Code-Examples/ModusToolbox-URL-Modifier/td-p/366015 thread but still running into the same issue.

Loading the manifest data
Found environment variable CyRemoteManifestOverride=https://raw.githubusercontent.com/Infineon/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml
Loading super manfiest files from all sources
Processing manifest pack file 'C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifest.xml'
Downloading super manifest file 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifest.xml'
Getting manifests from remote and/or local sources
Processing system manifest 'https://raw.githubusercontent.com/Infineon/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Downloading super manifest file 'https://raw.githubusercontent.com/Infineon/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Finished loading super manifest files from all sources
Finished download of file 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifest.xml'
Starting to parse super manifest with URL 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifest.xml'
Finished parsing super manifest with URL 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifest.xml'
Downloading manifest file 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifests/mtb-ml-ce-manifest.xml'
Finished download of file 'https://raw.githubusercontent.com/Infineon/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Finished download of file 'file:///C:/Infineon/Tools/ModusToolbox/packs/ModusToolbox-Machine-Learning-Pack/manifests/mtb-ml-ce-manifest.xml'
Finished loading the manifest data (42454 ms)
Loading the device db
INFO:Using the executable path for the tools directory.
WARNING:Error downloading 'https://raw.githubusercontent.com/Infineon/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml' -- Connection timed out
INFO:No device-db assets found in manifest
0 error(s), 1 warning(s

git bash config after modifying the URL as suggested.

core.editor="C:\\Program Files (x86)\\Notepad++\\notepad++.exe" -multiInst -notabbar -nosession -noPlugin
pull.rebase=false
credential.helper=manager
credential.https://dev.azure.com.usehttppath=true
init.defaultbranch=master
url.https://ghproxy.com/https://github.com.insteadof=https://github.com

Let me know if I am missing something.

Hi all,

    I am using the PSoC 6 cy8ckit-064b0s2-4343w . I attempted to construct a UART interrupt in Modustoolbox (version 3.0)using SCB blocks without FreeRTOS, and the hardware interrupt happened at that time. However, when I implemented the same code again with FreeRTOS(v10.4.302), I did not encounter a hardware interrupt since FreeRTOS does not call the interrupt function while transmitting.

The PDL(v3.2.0) API's used:

   For configuration:

        (void) Cy_SCB_UART_Init(SCB5, &uartConfig, &uartContext)
        Cy_GPIO_SetHSIOM(UART_PORT, UART_RX_NUM, P5_0_SCB5_UART_RX)

        Cy_GPIO_SetDrivemode(UART_PORT, UART_RX_NUM, CY_GPIO_DM_HIGHZ)

   For transmit data:

           (void) Cy_SCB_UART_Transmit(SCB5, txBuffer, sizeof(txBuffer) and &uartContext)
   For enable Interrupt:

            (void) Cy_SysInt_Init(&uartIntrConfig, &UART_Isr) and NVIC_EnableIRQ(UART_INTR_NUM)

 For other API's I referred   https://infineon.github.io/psoc6pdl/pdl_api_reference_manual/html/group__group__scb__uart.html . Can anyone suggest why in FreeRTOS the same code I implemented without FreeRTOS is not working and does I have to include any PDL API for interrupt in FreeRTOS?

Hi all,

I want to use freeRTOS in both cores but it uses the HAL. The PSoC™ 6 MCU: Dual-CPU empty application template says:

The Infineon HAL is not yet designed to run simultaneously on CM0+ and CM4 CPU. Because the proj_cm4 already uses HAL, proj_cm0p should only use PDL APIs.

Is this a problem if using Local git where each core gets a different copy of the HAL? if so, when will this issue be resolved.

Thanks