Software Forum Discussions

Hi,

TL;DR: How to know the Interrupt number that is triggered when Counter triggers a Compare or TC ?

I'm migrating a project from PSoC Creator (Schematic editor) to ModusToolbox (PDL).

In PSoC Creator's Schematic Editor, I can assign an interrupt (ISR) to the Counter object.

And I can get the number of the Interrupt because it gets autogenerated by the fitter (?).

E.g: If I have an ISR object called "ISR_Counter", then a "#define ISR_Counter__INTC_NUMBER xxx" will be generated.

And I want to know the interrupt number when using PDL or HAL API?

e.g:

    // Which NVIC will be triggered ?

    cyhal_timer_register_callback(&led_blink_timer, isr_timer, NULL);

Thanks!

Rolf Nooteboom helped develop a technique for writing and compiling firmware for PSOC5 on Linux and Macintosh (and Windows).  The overall system uses the free VSCode from Microsoft, the ARM compiler from ARM itself, some of the Modus Toolbox work Cypress put into previous versions of ModusToolbox(tm).

The upside to his work is the entire project's build finishes in seconds on Mac or Linux vs. minutes natively. (The minutes is when building under Windows using Creator).  I was able to take his work and stumble into modifying it for using a KitProg (as well as kitprog 2 or 3).   The pattern for the project directory was also changed, making it easy to use as a template for future projects, and with FreeRTOS.  (Yes, a complete FreeRTOS rebuild takes seconds on a Mac.)

I wrote several blog posts on this at socmaker.com.  My guide for coding/compiling on Linux (which is built on the previous blogs) is at https://socmaker.com/?p=1119 .  You have to create the schematic with PSOC Creator first.  (I use a virtual machine running windows 7, 64 bit to accomplish this.)  Then finish with the firmware development on your native O.S.

Previous posts at socmaker.com cover the Macintosh side.  Enjoy

Hi All,

it seems that there is not any category for TC356/TC357 project on AURIX™ Development Studio (Version: 1.7.2)

so, I want to know when AURIX™ Development Studio support this MCU(TC356/TC357).

regards,

WS

Hello,

I hope this is the right forum/place to ask my question.

I need some help and hand holding to achieve the following thing:

• I want to send data from PSoC62 Proto Kit to Cirrent using Cirrent Agent
• My data format is JSON
• I want to send data every hour and it will not exceed half a KB per update

I want the help to do :

• Cirrent Agent getting started
• Any guides/tutorials to help me do that
• Cirrent Platform hand holding - where can I see the date?

Thanks & Regards,

Arka

cc: @Rakshith @pandaySwarnam 

I have a design that needs to support USB audio class and an HID generic class simultaneously, are there any examples on USB descriptor design? especially using the USB Configuration tool.

Hi Infineon Team,

We are using CYW43455 chip for WiFi in iMX8MM board working on Android 11 OS. We have completed the bringup for WiFi but it is not supporting WPA3 connections.

When we try to connect wifi with iphone hotspot, it doesnt connect. When we checked the logs, we found the following:

wpa_supplicant: wlan0: WPA: Failed to select authenticated key management type
wpa_supplicant: wlan0: WPA: Failed to set WPA key management and encryption suites

Does CYW43455 support WPA3 SAE? I couldnt find WPA3 support in the datasheet.

If it supports, could you please guide us in enabling the WPA3 profile in Android 11 OS for this IC?

Thanks,

Hrithik

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?

When sending data from PC via USB serial port to CYSPP CYBT-483039-EVAL, it appears to be over-running the CYBT, without CYBT ever asserting PUART_RTS low.

• CYSPP CYBT-483039-EVAL is connected to iOS app using EZ-Serial BLE CYSPP
  
• Data is being sent using the Acknowledged Characteristic  (101)
• PUART SW5 are all turned On
• After press reset switch on eval board, I see UART RTS pin Arduino J7-P6 go high on oscilloscope
  
• I set CYBT and flow control by sending following command to PUART from the PC.
  

• "STU,B=1C200,D=8,F=1,P=0,S=1\r\n"

When PC starts sending file data to PUART over USB serial, I see the data being received on the iOS side, however, some data is missing.

I expected  PUART RTS to be asserted low to prevent 3 MB of file data from over-running the CYBT, when sending data to PUART_RX ?

I do not see UART_RTS on pin Arduino J7-P6 being set low during the 3MB file transmission.

What are potential solutions to prevent data over-running when sending data to PUART RX for transmission to iOS device?

Thank you,

-Ed

Hello,

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
Protocol: 1.3
HW: CYBT-343026-01

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.

BT_DEVICE_ADDRESS?=default

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.

Thank you,

-Rocko

We have a platform that uses WICED Version 3.7.0-7. AN STM32F469 processor uses the WiFi/BT module LBEE5KL1DX. We're able to bond with and connect and reconnect to a BTLE 4.0 keyboard without issues. When we do the same with the same model of keyboard that uses BTLE 5.0, we're able to bond with and connect with the  keyboard, but upon re connection, the firmware crashes. From the debugger, it seems to be crashing in a pee-compiled module we have: BTE_low_energy.FreeRTOS.LwIP.ARM_CM4.release.a.

Our belief is that something in the firmware is not handling BT 5.0 events correctly and is causing the firmware crash. But it isn't easy to tell what's going on in the project and the .a file is a bit of a mystery too. Are there any clues as to where to look for this issue? Is there perhaps an updated version of WICED or an updated driver file we should be using?