Welcome to the Infineon Developer Community

Hello

I want to use the XMC family of microcontrollers (xmc1000 and xmc4000) but I only have J-Link BASE and J-Link EDU Mini programmer, I have two questions.

- Can I use any of these two programmers with the XMC family? -

Where can I find the programming pins of these microcontrollers?

Thanks for the help

For emissions testing, I am trying to use the wl tool with NVIDA Jetson TX2, which has the BCM4354. I received a wl64 executable and 4354’s mfgtest firmware from an Infineon Tech Support Case.

I believe I correctly installed the mfgtest firmware by replacing /lib/firmware/brcm/fw_bcmdhd.bin with cyfmac4354-sdio.bin and by moving cyfmac4354-sdio.clm_blob to become /lib/firmware/brcm/bcmdhd.clm_blob. Before the above changes, running “sudo ./wl64 ver” gave me:

1.28 RC0.0
wl0: Jul 21 2020 16:35:45 version 7.35.349.94 (r726700 CY) FWID 01-aa356e32

After installing mfgtest firmware, the wl ver command gave me:

1.28 RC0.0
wl0: Sep  1 2021 02:23:00 version 7.35.349.112 (ae8cc29 CY WLTEST) FWID 01-6e1af42a

My main problem is that wl64 can’t bring up the Wi-Fi after I use it to bring down the Wi-Fi. It also doesn't work using the original firmware (i.e., before introducing the mfgtest firmware). The following are the commands I ran and the output.

user@device:~$ ip -br address show wlan0
wlan0            UP             192.168.0.79/24
user@device:~$ sudo ./wl64 down
user@device:~$ ip -br address show wlan0
wlan0            DORMANT        192.168.0.79/24

(after ~20 seconds)

user@device:~$ ip -br address show wlan0
wlan0            DORMANT
user@device:~$ sudo ./wl64 up
user@device:~$ ip -br address show wlan0
wlan0            DORMANT

At this point, I also can’t use the GUI to connect to a Wi-FI network.

Have I done anything wrong? What do I do so that I can at least use the wl tool to bring down and up the Wi-Fi module?

Hello

Is there any firmware available for BGT60TR13C  module to send out some information about the direction of the movement or angle values? 

I'm running presence_detection 1.3.0 but it seems it only transfers distance information not direction. Thanks in advance. 

Hello,

I am trying to generate an output frequency of 6 MHz using a PSOC 6 prototyping board but every time I measure the output pin using an oscilloscope its only giving 1.5 KHz. I want to get 6 MHz when I measure the output pin. I have attached the project. Can anyone help please?

Thank you

I just started using SK-FM4-216-ETHERNET Evaluation Board and it comes with a few examples but I'm looking for the most basic, to understand the use of inputs and outputs, press a button and turn an LED things like that.

Is there any sample code that explain the use of GPIO's?

The software I'm using is Keil uVision 5

Hi

I like the IR4426/7/8 low end drivers because they have MOSFET end stages, have two channels, and have a SO8 package. Unfortunate, the data specifications only specify the pulsed output currents. I need to know what the DC current capacity is.

Can anyone tell me what the DC output current capabilities are of these drivers, and what the RDSon resistance is of the output stage.

Thanks

I've been trying to implement a SPI interface on FX3 in order to reprogram a flash IC driving an FPGA, similar to the implementation described in AN84868 . I've been able to read from and write to the flash chip when I load slightly modified* versions of the USBFlashProg and UsbSpiDmaMode examples into RAM, but if I build the same code as an I2C image and load it onto the FX3's I2C boot EEPROM,  the FX3 crashes and returns nothing but code 997 as soon as I make a SPI request.

Things I've already tried:

1) All three available speeds, 64k and 128k I2C sizes in elf2img.exe's -i2cconf argument. Of the settings that could be successfully programmed to the I2C EEPROM, none of them had any discernible effect

2) Performing a SPI read operation while the SPI mux select pin* is pulled low; this doesn't cause a crash, but the data returned is all zeroes (for obvious reasons)

3) Changing the DMA timeout value from 0xFFFFFFFF to 0x00004000 -- no effect at all

4) Checking SPI busy status before performing a SPI read operation -- the check busy status command also crashed the FX3.

5) Using I2C in register mode instead of using DMA -- no effect

6) Commenting out all of the "if (status != CY_U3P_SUCCESS) {return status;}" statements -- no effect

7) disabling and reinitializing SPI and I2C before making any SPI requests -- no errors were returned during DeInit and Init calls for I2C and SPI, but the crash happened as soon as I made a SPI request

8 ) Commenting all I2C functions out and setting io_cfg.useI2C to CyFalse. 

I'm out of ideas. I can't think of any reason that booting from I2C should have any impact on SPI operation in a way that wouldn't be solved by one of the things I tried. Has anyone else encountered anything like this? 

* An external mux select needs to be pulled high to give the FX3 access to the SPI flash IC, but it's driven from a GPIO so I just use CyU3PSetSimpleConfig()  with .outValue set to CyTrue. 

EDIT: I was able to capture oscilloscope readings on the MOSI trace between the FX3 and the SPI flash. Here's a capture of a CY_FX_RQT_SPI_FLASH_ERASE_POLL when the image is loaded via RAM:

and here's the same command running the exact same image booting from I2C:

I've seen this happen on every command -- if the FX3 was booted from I2C, the MOSI line has a lower-voltage "echo" after each pulse.  Additionally, there is no activity at all on the MISO line after booting from I2C no matter what commands are sent. 

When a SPI read request is made after booting from I2C, the FX3 continually broadcasts the same pulse and echo until power is removed, suggesting that the crash is happening because the FX3 is stuck in a loop attempting to make contact with the SPI flash IC. However, setting a timeout in the SPI configuration settings does not fix this issue. 

Hi all,

Please tell me about the 1EDF5673.

I have two questions.

 1.Does 1EDF5673 have the circuit function which is similar to the active miller clamp circuit? 

     If not, please let me know the reason the function isn’t needed.

2.Is it correct that VGS is about t3(=20ns) shorter than PWM at first pulse?

    The first pulse is the light blue part below. 

Best regards,

MS

 Can't find the soldering peak reflow and also MSL documents for the 1EDN7550U gate driver on the product web page.  There is a good board assembly app note with soldering guidelines, but customer is looking for the peak reflow specification.

Please send, thank you!

Gordy Carlson

Infineon PSS FAE