Quantcast
Channel: Infineon Forums
Viewing all 9892 articles
Browse latest View live

Problem programming new TC1796 with MemTool


XMC1400 Problems changing BMI from UART to SWD

$
0
0
Hi Deni,

do you have solution for me.
I have already done update of J-Link.
But its show still the same message: Firmware is too old.
Regards
Michael

12V/15V power supply rating for gate driver 1EDI60N12AF

$
0
0
Hi,

I'm looking for a suitable power supply for the gate driver 1EDI60N12AF. As it is a isolated driver, it uses two isolated voltages, 5V and 12V or 15V. My question is basically about the ratings of the 15V power supply. The gate driver datasheet specifies a minimun peak current of 6A. But that doesn't mean that my supply has to be rated at 6A or 10A. In fact, my PWM frequency is 10 kHz, so I expect an average current drawn from 15V supply of I = Q x Fs, where Q is the total gate charge of my power MOSFET and Fs my PWM frequency. According to my power mosfet datasheet (IRF250P224), the total charge is 160 nC (for a VDS of 200V), so I = 160nC * 10 kHz = 1.6 mA.
In summrary, do you think that a 15V power supply rated a 66mA/1W is suitable? The minimum 6A peak current is provided by the decoupling capacitor, right? I'm just starting to do designs in Electronics, so I'm trying to strengthen some concepts.
My project involves mains, so I will use an AC/DC converter to get the 5V (IRM-15-5), and isolated DC/DC converter to step up the 5V to 15V (R1SE-0515/H2-R).

Add additonal area to the copytable of tc222

$
0
0
Ok, here is the problem.

I have a bunch of variables that I need to have a ROM version of at a specific address and a RAM version at any RAM address. No problem yet, I just did two copies of each variable (one ROM and one RAM) and a init function which copies from ROM to RAM.
The problem is that the init function which copies the variables is really huge and take a lot of flash. So I started looking at just using a memcopy over all of the variables, but I do not know how to garantee that the variables is in the right order and with the same padding. I cannot use a struct to accompish this as I need to find the variables in the map-file.

Then I found the copytable and saw that all the RAM variables was copied from the ROM with the copytable. The problem is that I cannot move the ROM versions of the copytable variables.

So my question is really can I add an additional area with specific variables to the copytable?

This is how it looks like in the map-file:

| mpe:dspr0 | | .data.Temp.VariableA(13026) | 0x00000001 | 0x700027fe | 0x000027fe | 0x00000001 |

| mpe:pflash0 | | [.data.Temp.VariableA] (35650) | 0x00000001 | 0xa002281e | 0x0002281e | 0x00000001 |

I want to change the ROM address 0xa002281e to another which I can choose, but just for specific variables, I do not want to move the entire copytable ROM area.

Please let me know if you need additional information, I am sure you do, this is my first time writing such a post.

/Johan

IR2136 Hardware Over current ,Why Output waveform this?

Tle5012b e1000

$
0
0
Hi.. Looking at your code,seems as if you are not clearing the interrupt after every read i.e.Clear the interrupt after receiving each frame.

Problems with EBU on XMC4700

$
0
0
Hi All,

I am having trouble interfacing XMC4700 (100 pins)with NAND flash via EBU. In my project EBU lines are shared with NAND flash and FPGA. FPGA is configured to pull up all AD/CLE/ALE lines.
So on power up all lines are pulled up. Even though lines are pulled high, when EBU is initialized, EBU should take control of these lines and control accordingly.
I have configured all EBU related general control and region control registers. I have made sure-
1. EBU is enabled on power on
2. Master mode is selected
3. Region 0 is selected and write is enabled for region 0.
4. All EBU related pins are configured to Hardware control as per the IO pin assignment.
5. EBUCLK status is enabled.
6. 16 bit mode is selected

Inspite of all these configuration, when i try to write cmd at 0x60000000 none of the EBU related pin seems to be changing.
For ex. since i have enabled default Region-0 in ADDRSEL register and Arb_mode as master in MODCON register, as per the user manual CS0 should go low but i dont see any changes on CS0.
To me it looks like, even though EBU is in master mode its still acting like a No Bus mode where it doesnt have control over ports pin yet

Just to ensure FPGA is not overwriting on AD lines, I tried toggling one of the AD line by making it GPIO and it worked as expected. \
Below is my EBU configuration
Code:

    // These values get written to the CLC register.
   
      configuration.ebu_clk_config.ebu_clk_mode          = 1U;
      configuration.ebu_clk_config.ebu_div2_clk_mode      = 1U;
      configuration.ebu_clk_config.ebu_clock_divide_ratio = 1U;
                                                                                                                               
    // These values get written to the MODCON register.
      configuration.ebu_mode_config.ebu_sdram_tristate  = 1U;                                                                                                               
      configuration.ebu_mode_config.ebu_extlock          = 1U;
      configuration.ebu_mode_config.ebu_arbsync          = 0U;
      configuration.ebu_mode_config.ebu_arbitration_mode = 3U;                                                                                                               
      configuration.ebu_mode_config.bus_timeout_control  = 0U;
      configuration.ebu_mode_config.ebu_ale_mode        = 1U; // Output is ALE

      // These values get written to the USERCON register.
        configuration.ebu_free_pins_to_gpio.address_pins_gpio = 0x1FFU;
        configuration.ebu_free_pins_to_gpio.adv_pin_gpio      = 0U;
   
      region.read_config.ebu_bus_read_config.raw0  = 0x20500024U;
      region.read_config.ebu_bus_read_config.raw1  = 0x00000000U;
      region.write_config.ebu_bus_write_config.raw0 = 0x20500004U;
      region.write_config.ebu_bus_write_config.raw1 = 0x00000000U;
               
               
        ebu_status = XMC_EBU_Init(XMC_EBU, &configuration);
               
        if (ebu_status != XMC_EBU_STATUS_OK)
        {
                error_flag = true;
        }
        XMC_EBU_ConfigureRegion(XMC_EBU, &region);
        XMC_EBU_AddressSelectEnable(XMC_EBU, 1U, 0U);
        XMC_EBU_AddressSelectDisable(XMC_EBU, 2U, 0U);
        XMC_EBU_AddressSelectDisable(XMC_EBU, 4U, 0U);

Below is my configuration for ports--( i have just mentioned configuration till AD4 below but similar configuration is present for all other pins as welli.e. AD5-AD15, CLE, ALE, CS, RD And WR)
XMC_GPIO_CONFIG_t config;

    config.mode = XMC_GPIO_MODE_OUTPUT_PUSH_PULL;
    config.output_level = XMC_GPIO_OUTPUT_LEVEL_LOW;
    config.output_strength = XMC_GPIO_OUTPUT_STRENGTH_STRONG_SHARP_EDGE;

    XMC_GPIO_Init(EBU_AD0_PORT, EBU_AD0_PIN, &config);
    XMC_GPIO_SetHardwareControl(EBU_AD0_PORT, EBU_AD0_PIN, XMC_GPIO_HWCTRL_PERIPHERAL2);

    XMC_GPIO_Init(EBU_AD1_PORT, EBU_AD1_PIN, &config);
    XMC_GPIO_SetHardwareControl(EBU_AD1_PORT, EBU_AD1_PIN, XMC_GPIO_HWCTRL_PERIPHERAL2);

    XMC_GPIO_Init(EBU_AD2_PORT, EBU_AD2_PIN, &config);
    XMC_GPIO_SetHardwareControl(EBU_AD2_PORT, EBU_AD2_PIN, XMC_GPIO_HWCTRL_PERIPHERAL2);

    XMC_GPIO_Init(EBU_AD3_PORT, EBU_AD3_PIN, &config);
    XMC_GPIO_SetHardwareControl(EBU_AD3_PORT, EBU_AD3_PIN, XMC_GPIO_HWCTRL_PERIPHERAL2);

    XMC_GPIO_Init(EBU_AD4_PORT, EBU_AD4_PIN, &config);
    XMC_GPIO_SetHardwareControl(EBU_AD4_PORT, EBU_AD4_PIN, XMC_GPIO_HWCTRL_PERIPHERAL2);

Is there anything I am missing on my configuration ?

Any information is appreciated.

Thanks

IR2136 Hardware Over current ,Why Output waveform this?


Can not flash new XMC1302 on custom board

$
0
0
Hello, I am not able to flash my XMC1302 on my custom board, I'm getting "Could not connect to target. Please check power, connection and settings.". It works perfectly fine with the XMC1300 boot kit.

My setup:

- Flasher software: DAVE and JFlash, works fine with the boot kit with the same MCU and pin config.
- Flasher hardware: The JLink board that comes with the boot kit.
- MCU: XMC1302T038X0200ABXUMA1.
- IC package: TSSOP-38.

What I have done to debug:

- Reviewed my design over and over with different methods. Everything from pins, footprints, connections etc.
- I have soldered the IC with different solder with different temperatures. In my last attempt I went with non-lead-free solder and 245 degrees C.
- I have checked every pin so that there's no short-circuits or open connections (except for the ones that should be there).
- I have "reverse-engineered" the boot kit to make sure that I use the exact same setup, connections, components etc. I looked in the schematics as well as checking with a multimeter.
- I haven't touched the IC with my hands and I'm very careful with handling it.
- I have 4 boards that should work but all of them have the same problem.
- I checked the documentation to see how the BMI headers are configured for new ICs and learned that the default setup is like the one in the boot kit.
- I have verified multiple times that the programmer has the correct connection to the debug (J4) header connector and that it is the same as for the boot kit.

Boot kit:

https://www.infineon.com/cms/en/prod...mc13_boot_001/

The design:

The design is just like the boot kit but with connections for sensors and some more stuff. I haven't soldered anything of that yet so the only connections that aren't left open is the power pins and programming pins.

Attachment 3534

Attachment 3535

Any ideas on how I could solve this or debug this further?

IRF1404 in the market with defect

$
0
0
Recently, I bought a lot of mosfet IRF1404 from a seller who said to have imported from US such mosfets.
When I performed bench tests on them, I realized they were original, but they had some anomalies, such as current leakage and low current tolerance, being limited to 15 or 20 amps, prior to their burning.
When I dismantled the mosfets, I noticed that their internal silicon chip was shifted to the left in an erratic way, which I believe was produced by Infineon, but failed in quality control and this somehow ended up in the market and caused me problems.
I request that the company carry out investigations, so that this does not become an usual practice and does not denigrate the name of the company, which in my view, produces great products. Below I show in the photograph of which I am referring.
The one on the left is the mosfet with problems and the one on the right is the normal mosfet.
The lot that presented defect, refers to the second photo.


Regards.
Henrique Duarte
+5519-994668256 (whatsapp)
?????

TC223 Starter Kit UART over DAP

$
0
0
HI All,

I trying to find out if it's possible to have UART over DAP (external miniWiggler connected to board DAP port) in same way as it's achieved with on board miniWiggler.
To be precise I want ot achieve setup on which I can communicate with board over virtual COM port provided by miniWiggler device (external).
I can use on board miniWiggler in such configuration without problems but I have to switch to external one (connected via DAP port).

Did anyone tired to configure UART over DAP for TriCore Starter Kit boards? Is this even possible?

Best Regards,
Konrad

XMC 4500 - how to enter Hibernate mode?

$
0
0
I'm currently working on the Hibernate mode. Have tried this code but this does not work for me and the description in the documents of Infineon help me unfortunately not further. Does anyone have a running code or can someone tell me what could be wrong with the code posted above?

Greetings Patrick

Microcontroler - Multiple I/O

$
0
0
Hi Jamesjgh,
we have several products which can cover your functional request. Nevertheless further information are necessary, i.e. how does the input signal looks like and what do you want to switch off.
Please have a look to our ePower product page.
Best regards

Codesize arm gcc4.9 to arm gcc7 increased drastic

$
0
0
Thanks for testing.

I extracted the section from the listing from my compilation.

Attachment 3540
Attachment 3541

Can you please post your listing and if possible your compiler / linker log?

In addition here are my compiler options for gcc7:
-DXMC1302_T038x0200 -DAKTIV=1 -DINAKTIV=0 -DTRUE=1 -DFALSE=0 -DNC=0xFF -DGND=0 -I"D:\Software Infineon\Demo" -I"D:\Software Infineon\Demo\DevDrivers\XMCLib\inc" -I"D:\Software Infineon\Demo\DevDrivers\CMSIS\Include" -I"D:\Software Infineon\Demo\DevDrivers\CMSIS\Infineon\XMC1300_se ries\Include" -I"D:\Software Infineon\Demo\RTOS\include" -I"D:\Software Infineon\Demo\RTOS\portable\GCC\ARM_CM0" -Os -fpack-struct -fshort-enums -ffunction-sections -fdata-sections -Wall -std=gnu99 -Wa,-adhlns="$@.lst" -pipe -c -fmessage-length=0 -mcpu=cortex-m0 -mthumb -g3 -gdwarf-2

They are the same as for gcc4.9.

EBU Addressing on XMC4700

$
0
0
Hi All,

I am attempting to read memory via EBU interface.
In my hardware ALE is connected to pin AD11 and CLE is connected to pin AD12.
Based on addressing alignment mentioned in reference manual 14.6.7 I i understand that internal pin mapping is ABH [16:1], and external pin mapping is AD[15:0]
With this understanding, since my CLE is connected to pin AD12 , internally its connected to ABH13 hence I am wrtiting command at address 0x60002000.
Similarly ALE is connected to pin AD11, internally its connected to ABH12 hence i am writing command at address 0x60001000.

*(volatile uint16_t*)(0x60001000) = 0x0020;// ALE
*(volatile uint16_t*)(0x60002000) = 0x0090;// CLE

However, when i dont see expected result. Like when i am writing address 0x0020 i see dont see ALE going high at all.

Can someone please let me know if my understanding on addressing is correct ?

P.S- Also, i have tried using addressing based on external pin mapping AD[15-0], i still dont see any difference.

Regards,
Query1920

Upgrading GCC in DAVE4

$
0
0
Hi.

I think it should be mentioned that for a project specific toolchain the variable ARM_GCC_HOME has to be deleted in the global scope settings/properties. and adjusted in the project specific settings/properties.
Otherwise allways the global settings/properties will be used to choose the toolchain.

DEMS-DK Kit not working

$
0
0
I recently bought a DEMS-DK kit. power supply and ethernet connections are OK but GUI is not responding. Is there any one successfully started this DMS-DK kit. very poor documentation

tricore-gcc link openssl

$
0
0
Hey together,

I need to link openssl for my project which will run on a AURIX TC275TP-64 later.

I have problems getting the correct version of openssl for the tricore-gcc. Using the normal openssl libs (eg. for mingw) it cannot link and I receive undefined references.
Therefore i tried to crosscompile the openssl libraries for tricore-gcc usage using this manual.

in the configure file which is included in the repository, I can chose the compiler for which it should be cross compiled, but there is no tricore-gcc. I tried with gcc but still get the same linker errors.

Has anybody encountered the same problem? How can i solve this problem?

Best regards,

jonnyx

[Ethernet] iLLD driver issue on TC29x

$
0
0
I've found other bug that may help you.

In my evaluation board, the pin defined for MDIO is not bidirectional. This has some implications in the iLLD PHY driver. For the non-bidirectional pin, the default config makes the MDIO pin to be just an output pin (let's call ut MDO then). When the driver tries to read the PHY registers with the MDO it will obviously not work properly. This cause the initialization function to not wait for the PHY to reset, since this busy-wait relies on the Read of a PHY register. I observed that this cause my PHY to not be configured correctly, by watching the clock pin with an oscilloscope and observing that the frequency was not the one configured. As a "temporary hack", until we migrate the microcontroller to our own board and change the pin mapping, I made dummy sleep function to wait the PHY to reset, by around 200ms. This fixed the issue for me.

P.S.: If you observe the clock pin with a oscilloscope, it is recommended to disattach the probe after your measurments, because I observed many ETH frames not arriving, due to, probably, too much current being drained by my probe.

Synchornization of Cores

$
0
0
Hi ,

Thank you for the detailed explanation. It helped a lot.

Best regards
Prakt
Viewing all 9892 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>