Welcome to the Infineon Developer Community

Hi

I have downloaded the XMC flasher tool, and when I opened it and tried to connect for the first time I was prompted that there was a new version of the firmware, so I clicked install. But I think somewhere in the installation process it failed, so now the XMC1300 wont connect anymore. I have tried to connect to it using Memtool, but without success.

I have selected device name as 1302-200 (as stated on the chip) and I have selected the connected emulator.

The error log in the XMC flasher is:

INFO-com.infineon.XMCFlasher.MainAppController-main: Logger Name: com.infineon.XMCFlasher.MainAppController
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Not Found property: xmcFlasher.JLink.dllPath Searching in registry key
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Setting property: bridj.JLinkARM.library to: C:\Program Files\SEGGER\JLink_V796e\JLinkARM.dll
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Not Found property: xmcFlasher.JLink.dllPath Searching in registry key
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Setting property: bridj.JLinkARM.library to: C:\Program Files\SEGGER\JLink_V796e\JLinkARM.dll
INFO-com.infineon.XMCFlasher.SeggerDLL-checkAvailabilityAndLoad:  Loaded JLink DLL 7.96.e
INFO-com.infineon.XMCFlasher.MainAppController-start: Starting Application in process ... 
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeDeviceName: Setting Device Name configurations
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeEmulator: Setting Device Name configurations
SEVERE-com.infineon.XMCFlasher.ErrorLogCallBack-apply: Communication timed out: Requested 8 bytes, received 0 bytes !
WARNING-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleConnect: com.infineon.XMCFlasher.DebuggerExceptions: Error get BMI value
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeDeviceName: Setting Device Name configurations

What can I do to re-flash it?

I have attached an image of XMC flasher

Hi all,

I have a induction motor that I am trying to control using the EVAL-M3-IM564 driver board and the EVAL-M3-302F controller board.

I used the MCEWizard to enter all the parameters and generated a .txt file for the MCEDesigner. In the designer I uploaded the .txt file to the controller and tried starting the motor.

Everything goes fine until my RPM reach the "Minimum running speed" RPM value. Then it either stops or runs at 1-10 RPM depending if the previous value was rather small or big. Even if I set the "Minimum running speed" higher than the "Reference speed" parameter in the designer, the motor will keep speeding up beyond the "Reference speed" and shut down when it reaches the "Minimum running speed".

Any idea's what might cause the problem?

PS. I'll add the .mc2 file.

Hello,

I am an engineer who has encountered the issue in the following link while using CX3 U3V. 

Solved: CX3 U3V partial buffer - Infineon Developer Community

I have another issue..

Currently, there is an issue where the image is not transmitted occasionally. No error is printed. So, I added a log in the Firmware to print the State of the MIPI Module every 5 seconds. Afterwards, I obtained the following log.

Here are my questions:

1. There are cases where it stays in State 15 without any error/action. However, in this case, if I continue to attempt to acquire the image, the image is acquired.
2. And suddenly at some point, the State changes to F and after that, no image is acquired at all. In the article below, it seems that if FW_TRG does not become !FW_TRG, it does not move from F. What problem could be causing this? 

EZ-USB™ CX3 - USB 3.2 Gen 1 device controller for USB3 Vision camera (infineon.com)

The situation has only changed in the following content from the issue in the above link.

• image size: 1744x2400 -> 872*1200

Thank you

Kang

Hello,

I am facing an issue while writing data to the DFlash memory region. I am using the TC375 Flash programming Example code with some changes. Below is the scenario for which I am facing the issue.

1. The first time writing data (0xAF000400) to the address 0xAF000240 is writing successfully.

2. reading data from 0xAF000240 reading successfully.

3. If I write the data that is read from 0xAF000240 to the same address by updating the data with some other value, the memory(0xAF000240) is filling with zeros (0x00000000).

Can any one please suggest the solution. 

Thank you very much !

Dear Infineon support Team,

I want to replace BTS442 E2 by BTS441RG in one of our products and have following questions:

Most critical for us is the lower maximum allowed Vbb (abs.max) which is 63V for BTS442 and only 43V for BTS441. 

The datasheet of the BTS441RG recommends for overvoltage protections 150 Ohm between BTS441.GND and Signal GND.  I would like to implement these 150 Ohm but am wondering, if there are any further informations about this replacement:

1) do you have some further informations about replacing BTS442 E2 by BTS441RG not written in the datasheet?

2) Any drawbacks i might currently not be aware of using the 150 Ohm resistor for OV protection as proposed in datasheet?

3) is there a LTspice model for BTS441RG available? For example the BTS436L2G has one on your homepage.

Thank you very much in advance for your support!

Best regards,

Bastian

Hello all,

I'm using the TLI49d-W2BW with a Raspberry Pi4,
I started with a code found on another thread in the forum, thanks to @Yashraj_P .

And it worked quite nicely during a long time.

But I'm having slight problems nowadays :
The sensor is working properly and I'm reading the values (Bx, By, Bz) of the sensor during an hour or more (values arriving each 20seconds),
And suddently the read values are not changing anymore, and I read Bx=-1, By=-1, Bz=-1
With or without a magnet around.

First is :

def initialize(self):
        # Enabling One-byte read, Clock Stretching enabled, /INT disabled, Master Controlled Mode
        self.pi.i2c_write_byte_data(self.h, 0x11, 0x15)
        # Temp enabled, Bz measure enabled, ADC trigger on reading after 0x05 register
        self.pi.i2c_write_byte_data(self.h, 0x10, 0x20)
        sleep(60e-6)
        self.update_data()

Then :

def update_data(self):
        (count, self.data) = self.pi.i2c_read_device(self.h, 6)

def get_x(self):
        self.bx = (self.data[0] << 4) | ((self.data[4] >> 4) & 0x0f)
        if self.bx > 2047:
            self.bx -= 4096
        # self.bx *= 0.098
        return self.bx

I tried few things and realised that when I'm launching my software, 
I'm in fact "initializing" the sensor to write the configuration to the register,
And later on when reading (clicking on a button or automatically during a sequence) the values, well I'm just reading them.

Once I have Bx=-1, By=-1, Bz=-1,
I quit the program and relaunch it then it works fine.
So the problem should be with the iniatilazion at that point ?
So now I have fixed the problem by initiazing the sensor every time before reading the values,
But I'm wondering if it really should be like this 🤔

Doeas anybody had a problem of the same kind ?
Did I miss something somewhere ?

Thanks a lot for the reading time,
A good day to all.
Bastien

Hello, I need to know the correct part number associated to ordering code SP005591068.

BTS409L1E3062AA or BTS409L1E3062AB ?

Thanks.

Best Regards