Welcome to the Infineon Developer Community

Hi,

I am connecting up the iMotion-Link for the first time. I understand from my previous post (see link below) that I can use 5V logic on the target board.

https://community.infineon.com/t5/iMOTION-controller-driver-IPM/iMotion-Link-useable-for-interfacing-with-custom-board-with-IMC101TF-and-5V/m-p/346143/thread-id/436

However, now that I am using the iMotion-Link, I am not getting ANY signal out the RXD1 pin (which should transmit to the IMC101's RX0 pin on my board).  Both RXD1 and TXD1 pins from the iMotion-Link 8-pin header connector appear to be floating. Of course, the 3.3V switch is turned off as well.

I hook up the USB cable between PC and the iMotion-Link, run MCEDesigner, the virutal serial port appears (as COM10) and then I try to connect over the port. However, no signals are generated from the RXD1 and TXD1 pins.  What could be going wrong?

Do I need to apply my 5V power to the 3.3V pins on the header connector?  I thought that RXD1 pin would be driven without needing this.

I also verified that resistor R1 is not present on the iMotion-Link per previous posts on this issue. I purchased the unit earlier this year.

Thanks,

       Aaron

Hi,

I'm facing a problem while developing the firmware for a 100W power adapter.

I programmed the CYPD3196 via SWD and J-Link. Afterwards I could not program it a second time. In openocd I get the error "DP: cannot read IDR".

I suppose I have chosen the wrong bootloader. Because I was not able to find the bootloader for the CYPD3196, I utilzed the one for CYPD3175. Is it possible that this is interrelated?

Where can I find the correct bootloader files for the CYPD3196?

Is it possible to reprogram the chip?

Hello there,

I am attempting to run a Altium SPICE simulation with the SPICE model for the IRS21876S, and I'm encountering a few errors. I keep getting a PWL  error about an ngspice expression not being a constant. This confused me since there is no PWL source in the model. I'm not sure if this is a problem with the model or Altium, but I thought I'd post this here to help track down the issue. I've included a screenshot of the error messages with this post. 

Altium/ngspice Error Messages

Hello,

Could you confirm if AT24CM02 256KB EEPROM can be used for FX3 I2C boot?

Did Cypress do any testing with any 256K Atmel memories?

Thanks you!

Hi,

I am trying to generate the correctable alarm0[6] in SMU (for example: CPU0 SRAM PCACHE/PSPR single-bit correctable). but it was not generating, the code snippet is below--

Regards-

I first tried to install :

Infineon-Memtool-DevelopmentTools-v05_00-EN.exe on my windows 10 PC (this installer has been successfully installed else where). After installation, when I first run it, I got pop up "Can't create Memtool user interface !". 

Then I downloaded the latest: Infineon-Memtool-DevelopmentTools-v06_00-EN.exe which automatically install pre-requisites. Uninstall the previous version, then install the latest one. I got the same error once I tried to run it. 

Please see attached and kindly advise.

I am currently using a setup with a FF1400R12IP4 IGBT with a corresponding 2SP0320TA0 gate driver. I have verified that the diodes are working in the intended direction with the description below.

Hello Team Infineon,

I have questions on PSoC 4100 BLE I have two questions:

1. What is the maximum number of Segment LCD can one PSoC4100 BLE can handle?

2. What is the maximum number of pins in PSoC4100 BLE can be used for Segment/Character LCD?

the datasheet shares 4 COMs and 32 pins, but can there be more pins used to control Segment/Character LCD?

Regarding "1.", after reading the datasheet, I checked Functional block. There is a LCD block.

There is one LCD Block, but I cannot find the maximum number of Segment LCD
can one PSoC4100 BLE can handle. 

Regarding "2.",  in PSoC 4100 BLE Datasheet> Features > Up to 36 Programmable GPIOs,
the explanation says "Any GPIO pin can be ... LCD, ..."

according to PSoC4100 BLE Datasheet > Special-Function Peripherals>LCD Segment Drive section,
It says LCD controller can drive up to "four commons" and up to 32 Segments.

What is the maximum number of pins in PSoC4100 BLE can be used for Segment LCD? 

Thank you for your concern and help.

Hi,

We have developed a custom PCB with the CYUSB3014-BZXC and we've noticed that sometimes when we connect the board to the PC using a USB 3 C to C or USB 3 A to C cable Windows fails to detect it. In such cases Windows does not make the new device connected sound nor does it report an error.

According to my coworkers this happens randomly, typically after the board has been disconnected from the PC for a long period of time. They tried disconnecting the board from the PC, discharging the onboard capacitors, and then reconnecting it to see if they could reproduce what seems to be a random issue that occurs after long periods of the board being unpowered  but they weren't able to reproduce it this way. My coworkers are using laptops that come with Intel 3.1 host controllers.

I added UART debug logging to our bootloader and yesterday I noticed something similar occur. I had been testing our bootloader and application firmware on an Apple M1 Mac Mini, then disconnected the board (left unpowered) for a while (maybe 20 minutes), and then connected it to the Intel 3.0 USB A port on my Windows 10 desktop PC. Windows did not make the new device connected noise, nor did it display any messages. Fortunately I had a USB UART connected to the board and managed to capture the USB events via the output, which were as follows:

Initializing FX3 Boot Firmware 1.10
Boot FW Event: CY_FX3_BOOT_USB_IN_SS_DISCONNECT
Boot FW Event: CY_FX3_BOOT_USB_CONNECT
Boot FW Event: CY_FX3_BOOT_USB_COMPLIANCE

We have a button attached to RESET#. I tried resetting the MCU using this button and didn't see anything different in the UART log, nor was the FX3 identified by Windows. The problem only resolved after I disconnected the board from my PC and plugged it back in. I'm not sure if this is the same issue that randomly occurs for my coworkers, as they didn't manage to capture the UART logs.

I'm not sure if this issue is caused by something in the hardware design or something in the firmware but it would be great if we could figure that out before the next PCB revision, which is about 3 weeks out.

Thanks,
Michael