Welcome to the Infineon Developer Community

Hi,all

 

Recently, we are doing the software development of USB PD 140W related verification.

Our usage scenario is one CYPM1311-48LDXI as sink and another CYPM1311-48LDXI as source, so my understanding is that one FW burning USBPD_sink source code as Sink and another FW burning USBPD_DRP source code as Source.

I think I need to use the code to the following two links.I want to develop on ModusToolbox 3.x.

Are the following code available in ModusToolbox 3.x now?

https://github.com/Infineon/mtb-example-pmg1-usbpd-sink

https://github.com/Infineon/mtb-example-pmg1-usbpd-drp

 

 

 

Show Less

Hi,

I am using aurix TC233 micro controller.

I want the same function to be executed from multiple core (core 0, 1 and 2).
But the function should execute in parallel, each core should have its own instance of execution (independent local variables etc)
Also the function uses global variable shared across all cores.

How I can do this. Show Less

My goal is to use Raspberry Pi 3 Model B+ (RPi) to write hexadecimal keys/numbers into OPTIGA™ Trust X on the Security Shield2Go board, through a Python program. The communication between RPi and Trust X is through the I2C interface.

May I know are there existing libraries to use? If yes, may I know the procedure to use the library and the procedure to complete the whole I2C setup?

Thanks!

Show Less

Hi,

Having read some threads in this forum I have come up with this layout, we need inmunity to liquids.

 

(the dimesions are aproximate).

The shield will be on an intermediate layer (4 layer PCB). The guard and proximity sensor will be on the bottom layer.

The shield will have the pattern described in AN90071.

 

Questions:

1. Is it better to have a square pattern instead of a rectangular one?

2. The location of the wireless module is adequate? Should I place it in the top or bottom (same as cap sense) layer?

3.  Is it important to avoid having solid ground planes around the sensor? From my experience it is a thing to avoid. But the AN90071 seems to say otherwise. I say that because in the proximity sensor design they recommend placing a ground trace around the sensor.

4. How would you improve the design?

Show Less

I am attempting to make a FX3 firmware which extracts UVC data from a FIFO populated by an FPGA, attaches UVC headers and then sends the packets to the USB host however my video data is not being consistently sent to the host. Looking at the USB bus in Wireshark I can see 1 or 2 full packets of UVC data are sent to the host but after that the FX3 seems to ignore requests from the host for more data and I am not sure why. The packets that are sent are full, so they should not be marked as EOF and I can verify that by looking at the packet's headers in Wireshark. Additionally, the FPGA is constantly outputting data to the FIFO therefore the FIFO should have data and the FX3 should be able to fill its buffers with that information and invoke the callback functions. Since the sending of the UVC data handled by a callback function, I don't think the issue is a failing API call which results in an endless loop but I cannot verify this. I am basing my firmware off the AN75779 and USBVideoClassBulk example firmwares and I am following the same setup and logic for sending UVC packets to the host. The descriptors only allow for 1080p60 and the parameter negotiation with the host seems to complete successfully.

I have included my firmware as well as 2 different Wireshark captures showing 1 and 2 packets being sent. Help diagnosing why my firmware is hanging would be appreciated. Unfortunately I do not have access to the debug logs despite them being activated in the firmware.

Show Less