Welcome to the Infineon Developer Community

Hi,

I've just received the arduino shield and seems to work fine in FOC mode (in my case for a 3 phase brushless dc without sensors)

However I am unable to make it work in BEMF mode, I've tried some variations in the parameters without luck, however, In my attempt to read the current values it uses it seems that the arduino libraries and the board firmware are out of sync, the following sequence gives me an error:

shields = new TLE9879_Group(1);

shields->setMode(BEMF);

shields->readDataset(1);

In the arduino serial monitor the following message appears:

"WARNING: Board[1]; Action[read dataset]; checksum does not match -> calc: 63; recv: 125 "

Doing some debugging I've figured that the board sends a response of 29 messages, while arduino library expects one of 30 messages as defined by:

Is it possible to create an SDIO interface on a PSoC 63 in a WLCSP?
Specifically; is it possible to either split the SDIO to multiple ports or route a UDB based SDIO interface to one of the ports with six or more signals?

There is support for creating a UDB based SDIO interface @ https://github.com/Infineon/udb-sdio-whd
The available library supports an SDIO interface on one of three different ports: P2, P9 or P12. The SDIO interface requires six (6) signals on whichever port is selected for SDIO. Reference the table under "Whats included" @ https://github.com/Infineon/udb-sdio-whd

It appears only a maximum of five (5) signals are available for any of those three ports on a PSoC 63: P2, P9 or P12.
Other ports on the PSoC 63 in a CSP have six or more signals including: P0, P5, P6, P7, P8, P10 and P11.
Reference Table 7 in PSoC 63 CY8C63x6, CY8C63x7 Datasheet @ https://www.infineon.com/dgdl/Infineon-PSoC_6_MCU_PSoC_63_with_BLE_Datasheet_Programmable_System-on-Chip_(PSoC)-DataSheet-v16_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ee4efe46c37

Greg

Dear Infineon team,

we are experiencing the following behaviors.

HW: CYW4343W (Laird Sterling LWB) within Variscite DART-6UL SoM

FW: BCM43430A1_v001.002.009.0142.0511.hcd (within Yocto Dunfull, kernel 5.4.142, bluez 5.55)

Repro Steps:

- bluetoothctl: power on

- bluetoothctl: advertise on

Connect using BLE Scanner App on phone.

- bluetoothctl: disconnect

Phone with Android 11 & 12 force an automatic reconnection.

- bluetoothctl: disconnect

Phone with Android 11 & 12 force an automatic reconnection but the kernel now notifies the following messages

[17196.416963] Bluetooth: hci0: command 0x2006 tx timeout

[17198.497135] Bluetooth: hci0: command 0x200a tx timeout

The only way to recover is stopping the hci interface and the brcm_patchram_plus binary to reload the BT firmware and restart the BT interface.

Phones with Android 11 and 12 show this behavior. Tested phones: Samsung Galaxy S20/S22, Google Pixel 3XL/4A/6 and Nokia 5.3

Phones with Android 10 or below do not show this behavior and upon disconnect, the phones don't try reconnecting.

Are you aware of any known similar behavior ?

Thanks

Best Regards

Pier

Hello,

   I've just installed aurixide_1.7.2_Windows_x64.exe and I can see that DAS 7.3.7 was also installed(installer in AURIX Development Studio install dir) but it does not work.  Trying to flash a project results in an error

Aurix Flasher 2.5.3.0, built on 3/17/2022 3:12:47 PM
DASWRAPPER::ERROR init DAS API. Do you have DAS drivers installed?

Overall time: 123 ms
AurixFlasher Exit Status: Fail
DAS struct not initialized
Flashing failed

But DAS is installed, just that it does not work. -> see attached picture.

I've tried with reboots and reinstalls but to no avail.

Thanks for the help,

George

PS1: If I install DAS_V7.1.8 it works, but when trying to start a debug session a popup informs me that DAS 7.3.7 is needed.

PS2: Windows 10 X64

PS3: I have a TC334 Lite Kit

I need to use the cyusb3kit-003 SuperSpeed Explorer kit to develop a "logic analyzer" that writes from 16 bit parallel input to windows disk through USB3.   I have a USB2 device that takes data to a buffer, but the readout won't keep up with input.

It is simple.  I need an EXE file for execution under windows command prompt that takes data and writes to binary disk like my current unit.   I am not a programmer, so I need to find someone to do the programming.    I use a high level language to read the binary file and process it.

The web pages lead me in endless circles, and the associates list does not seem to know about the SuperSpeed device.   Short of learning binary coding which I do not have enough time to do,  I see no help. 

Hi I,m using tc275 (Hightec compiler )and I have this error:

.bmhd_1 loaded at [80020000,8002001f] overlaps section .text

Any suggestions?

Thanks 

Hello,

I tried to flash the TC38x microcontroller ECU and it failed but now I am unable to communicate/connect or flash the TC38x with the Infineon MEMTOOL via MiniWiggler. I think the TC38x target is locked, as I can see an error as IF_LCK . Can you let me know how to unlock the target device. I am thinking probably I should reset the microcontroller but cannot find the right procedure.

This is the error message: 

MEMTOOL Error messages:
Controller0.Core0.Tc2CoreTargIntf: Can't connect target !
Controller0.Core0.Tc2CoreTargIntf: Can't connect target device via DAS !

Hello,

We are using a PSoC5LP and just implemented our bootloader. We are going to program the bootloadable application via the i2c bus from another microcontroller.

The other microcontroller is responsible for sending a "Reset" command to the PSOC to get it into bootloader mode.

What is the correct sequence in the PSOC for the bootloadable application to issue a reset command so it can go into the bootloader, and then wait for the specified host link time in the bootloader?

This forum post [Link] says to do the following in the bootloadable application:

    Bootloadable_SET_RUN_TYPE(Bootloadable_SCHEDULE_BTLDR);

    CySoftwareReset();

However, when I browsed the generated source code of Bootloader.c, it appears that if SCHEDULE_BTLDER is set, then it will wait forever for the command, and not even check the wait time set in the bootloader component.

If CySoftwareReset() is used without setting the run type, does the PSOC reset to the bootloadable or bootloader?

We used a PSOC4 in a different application, and our reset process was to enable the watchdog so we could reset from that. PSOC5LP is different, because the watchdog API is not as flexible as the PSOC4. Our watchdog is already going to monitor the application, and the timeout is too much for us to use for this purpose.

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!