VADC - Startup Calibration

April 1, 2016, 3:54 pm

≫ Next: Multi Core Debug (MCD) API and DAS 5

≪ Previous: XMC4500 ETH-Problems with httpserver_raw-example

$

0

0

Hi all,

I am currently working with an ADC module in an attempt to better understand its properties. As of now, I am getting very inaccurate results, i.e. really big DNL and INL, quite low ENOB. One of the few non-obvious things I did was connecting GND to VAGND, which almost halved DNL, but it's still showing a very high value. I am using XMC4400 kit; sampling at 400 kHz with 4x oversampling and averaging. At this point its not quite clear to me whether the problem is within the software or are there any hardware setup that I am doing wrong. Could anyone please suggest a possible explanation as to why the accuracy might be so poor? Thank you!

All the best,
Andrey

---

Multi Core Debug (MCD) API and DAS 5

April 2, 2016, 9:48 am

≫ Next: Jlink connection via USB failed

≪ Previous: VADC - Startup Calibration

$

0

0

Hi, has someone implemented something with MCD API? Documentation is very poor, Infineon doesn't ansver and DAS 5 support and help is less then zero.
MCD Client is doing something but not correctly and API implementation is not working in the same way.
SPRINT project seams to dead, web page www.sprint-project.net doesn't exist.
I have a MiniWiggler3, that Infineon solds that is practically unusable.

Best regards
Gian

Jlink connection via USB failed

April 2, 2016, 9:24 pm

≫ Next: XMC 2Go - I2C - RGB Sensor

≪ Previous: Multi Core Debug (MCD) API and DAS 5

$

0

0

First time xmc user here. Installed Dave 4 and connected an xmc 2go to a usb port.
Went through XMC 2Go Initial start-up Guide but I could not get HTerm to communicate with the XMC, the only port available is COM1.
Started Jlink V5.10l and it reported no emulators connected via USB.
Did I miss any drivers to install? I am using Windows 7 64-bit. Thanks for the help.

XMC 2Go - I2C - RGB Sensor

April 4, 2016, 12:01 am

≫ Next: how to use the ambient light sensor(XMC1200 RGB LED Light)

≪ Previous: Jlink connection via USB failed

$

0

0

Hello Schimidi,

Yes, the debug mode is meant to help trouble-shoot any potential issues.

From you code, I think there are two aspects that needs to be investigated further.

1) In your write function which consists of 5 calls of the I2C001_WriteData() API, the 4th one is missing a semi-colon.

Code:

---

        data1.Data1.TDF_Type = I2C_TDF_MTxData;
        data1.Data1.Data = *I_O_msb;
        while (!I2C001_WriteData(&I2C001_Handle0, &data1))

---

2) I think the read function will result in an endless loop due to the while(i2cbusy) statement. i2cbusy is defined to be always 1?
Also, I would suggest to use the TDF code "I2C_TDF_MRxAck0" for the first data to be received.
This code means receive data and send acknowledgement.
TDF code "I2C_TDF_MRxAck1", which means receive data and send not-acknowledgement, should be used only for the last data to be received prior to the stop condition.

Regards,
Min Wei

how to use the ambient light sensor(XMC1200 RGB LED Light)

April 4, 2016, 12:26 am

≫ Next: Data streaming with DMA

≪ Previous: XMC 2Go - I2C - RGB Sensor

$

0

0

Hi Allan,

I have an example project for this. Please provide your email address so that I can send it to you.

Data streaming with DMA

April 4, 2016, 12:27 am

≫ Next: Bootloader running from Flash

≪ Previous: how to use the ambient light sensor(XMC1200 RGB LED Light)

$

0

0

I need to send a continuous stream of data via a USIC. I am planning to use 2 data buffers to prepare the date and then transfer the data using DMA.
What is the best way to continuously swap between the 2 buffers? Can the "Gather" function be used or is it better to use a linked list and update the address after each block is finished?
Or is there another method which I do not know? I guess this is a common requirement so there is probably a good and easy solution.
Any code example would be useful.

Bootloader running from Flash

April 4, 2016, 2:00 am

≫ Next: About Boot loader

≪ Previous: Data streaming with DMA

$

0

0

Hi,

Can anyone Please guide me for implementing SPI boot loader for XMC 1400 with external interface of SD card.Please help me in the Firmware prospective and process which i need to

follow for the entire implementation(I am working on XMC 1400 Dev. kit with controller XMC 1404-F064x0200).

Thanks & Regards,

M. Ramarao.

About Boot loader

April 4, 2016, 3:13 am

≫ Next: XMClib SDMMC example

≪ Previous: Bootloader running from Flash

$

0

0

Hello Ramarao,

Sorry I missed your reply on the problem with downloading the file.
But can I confirm that when you click on the button "Accept and Open" on the subsequent page with agreement on use of the document/SW, you do not get a dialog box to save the file, which is actually a zip file?

I saw that you have posted on implementing a SPI boot loader with SD Card interface. Since those threads are quite old, I will simply use this one to comment.

I got to admit that I have not tried implementing such a boot loader before, but I should be able to support you from the device point of view.
Obviously you must first be able to interface to the SD card through the SPI. Are you able to do this already?

From the boot loader and device perspective, then there should be a means of reading blocks of data from the SD Card into the SRAM, and triggering the Flash erase (if necessary) and program.
Since the XMC1400 SPI is the master, it can decide when to read the subsequent blocks of data after the current ones have been successfully programmed.
So in this aspect, the handshaking between XMC1400 and the SD Card is much easier, compared to the ASC-based implementation.

Regards,
Min Wei

---

XMClib SDMMC example

April 4, 2016, 4:04 am

≫ Next: FAQ for XMC4800 EtherCAT

≪ Previous: About Boot loader

$

0

0

May I know if it is not available? Has it been tested with XMC4500?

FAQ for XMC4800 EtherCAT

April 4, 2016, 6:28 am

≫ Next: Modifying DAVE generated source

≪ Previous: XMClib SDMMC example

$

0

0

How I Can modify the example code XMC4800_Relax_EtherCat_APP_Slave_SSC for using the Distribut clock (Sync0 interrupt) ?
Thanks

Modifying DAVE generated source

April 4, 2016, 9:06 am

≫ Next: ABM Header

≪ Previous: FAQ for XMC4800 EtherCAT

$

0

0

I had problem with application crashing on RX task stack overflow. I found out the offending thread, it is ETH_RX_INPUT from
lwip stack. Because I found no settings for its stack size, I directly modified file ethernetif.c:
sys_thread_new("ETH_RX_INPUT", ethernetif_input, netif, 400U, osPriorityBelowNormal);
Unitl now it seems to help.
But every time I change the DAVE application settings and new DAVE code is generated, my changes are lost. It there any solution other
every time to edit ethernetif.c again?

ABM Header

April 4, 2016, 9:27 am

≫ Next: Radar

≪ Previous: Modifying DAVE generated source

$

0

0

Thanks OMR. Sorry for the late reply, I was on vacation :-)

Before I proceed I want to explain my reason. I want to use the ABM Header because I'm still working on my bootloader. I'm using a XMC4500 (with Dave4) but I cant use the ASC Bootloader because the pins
which are needed are used for something else. Therefore I have to find another solution. The only solution is now to have a Bootloader starting at 0x0C000000 which jumps to the application
after receiving and saving the data of the application. The receiving and writing of the data works. I've check the memory with the J-Mem tool. The bootloader is communicating with my selfwritten
windows application.

My only problem is I cant jump to the application. I've tried it with your code and couldnt get it to work.

PPB->VTOR = APP_START_ADDRESS;
asm(
"ldr sp, [%0]\n\t"
"ldr r0, [%0, #4]\n\t"
"bx r0"
:
: "r" (APP_START_ADDRESS)
:);


I guess I need the ABM and set the SWCON to ABM and then do a system reset.
I'm calculating and writing the CRC checksums only once (after a flag has been set) AND before I write anything in the desired Code range or into the last 32 Byte of the first 64KB sector.
Is that right?

I can calculate the CRC Checksums. But I'm not sure if the results are valid. I get the Checksum 0 for both the abm0[3] CRC32 for application length and abm0[4] CRC32 for above 4.

I used the start address for calculating the CRC-32 for the application. The application should start at 0x0C080000 and is defined as APP_START_ADDRESS.
The size therefore 0x0C100000 - 0x0C080000 = 0x80000

with crc32Gen(APP_START_ADDRESS, 0x80000) I get the crc of 0

ABM Header with the define ABM_ADDRESS 0x0C00FFE0
For the Header the size is 0x0C010000 - 0x0C00FFE0 = 0x20

with crc32Gen(ABM_ADDRESS, 0x20) I get the crc of 0.

Why ist that?

I've also tried it with Travis is suggestion

/************************************************** *********
* Coding supply by verification team
*
************************************************** *********/
uword crc_gen (uword *data, uword size)
{
uword crc = 0xFFFFFFFF;
for(uword i=0; i<size; ++i) {
uword word = *(data+i);
uword feedback =
((crc & (1 << 31)) ? 1 : 0) ^
((crc & (1 << 30)) ? 1 : 0) ^
((crc & (1 << 29)) ? 1 : 0) ^
((crc & (1 << 27)) ? 1 : 0) ^
((crc & (1 << 26)) ? 1 : 0) ^
((crc & (1 << 24)) ? 1 : 0) ^
((crc & (1 << 23)) ? 1 : 0) ^
((crc & (1 << 21)) ? 1 : 0) ^
((crc & (1 << 20)) ? 1 : 0) ^
((crc & (1 << 19)) ? 1 : 0) ^
((crc & (1 << 15)) ? 1 : 0) ^
((crc & (1 << 9)) ? 1 : 0) ^
((crc & (1 << 8)) ? 1 : 0) ^
((crc & (1 << 5)) ? 1 : 0);

crc = ((word ^ ((crc & 0x7fffffff) << 1)) & 0xfffffffe) | (feedback ^ ((word & 1) ? 1 : 0));
}

return crc;

}


uword Calculate_WordSize (uword start, uword end)
{
uword size;

size = (end-start);
size = size >> 2;

return size;
}

With that I dont get zeros as a result. But its not working either :(

Radar

April 4, 2016, 6:51 pm

≫ Next: XMC4500 Max I2C speed

≪ Previous: ABM Header

$

0

0

It appears Infineon has a great 60ghz if for gesture recognition. How can we find and get information about this? We like to design this for which volume applications.

XMC4500 Max I2C speed

April 4, 2016, 9:31 pm

≫ Next: About FAT FS APP usage

≪ Previous: Radar

$

0

0

Hello,
I am looking for the max speed of I2C from XMC4500 as a Master. Can someone let me know what is the max supported by hardware chip and limitations from software device driver if any?

Regards,
Avinash

About FAT FS APP usage

April 4, 2016, 10:07 pm

≫ Next: XMC4500 Socket server

≪ Previous: XMC4500 Max I2C speed

$

0

0

Hi,

I am currently working on Field firmware update through SD card. I am working on XMC 1400 Dev. kit and connected SD card through SPI interface. Please guide me to use the FATFS App, which is

available in the DAVE 4. How can i use it for my implementation?. Anyone please guide me.






Thanks & Regards,

M. Ramarao.

---

XMC4500 Socket server

April 5, 2016, 5:53 am

≫ Next: April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

≪ Previous: About FAT FS APP usage

$

0

0

Hi

I'm trying to develop a socket server using xmc4500. Any example to start from?

thank you

April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

April 5, 2016, 9:25 am

≫ Next: April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

≪ Previous: XMC4500 Socket server

$

0

0

Today we released two new version of Device Description and a new version of the Device Pack to fix recent identified issues.

DAVE Devices Description:
The devices description XNC4700 and XMC4800 in the 196 pin package are updated to fix the following issues:

• Wrong pin connection to p0_tx_clkc signal has been corrected .Initially it was with P9.0 the corrected one is P9.1 (only XMC4800).
• Missing alternate function declaration for CCU81 CC80/1/2/3 have been corrected.

Further details can be found in the Release Note.


Device Pack update to v2.1.8:

• A not correct alignment of the bss and data section in XMC4000 linker script files may lead to not correct initialization of the first data in the respective section. This has been corrected

Further details can be found in the Release Note.

How to update:
When starting DAVE an update notification will appear. To install the update click on the notification and follow further instructions.
Alternatively the check for updates functionality can be used:
Press –Help -> Check for DAVE APP Updates (Device description updates and Device Pack update)


An updated zip file that includes the updates with all libraries to install the update locally can be downloaded from here.

April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

April 5, 2016, 9:27 am

≫ Next: More Demonstration at Embedded World 2016

≪ Previous: April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

$

0

0

Today we released two new version of Device Description and a new version of the Device Pack to fix recent identified issues.

DAVE Devices Description:
The devices description XNC4700 and XMC4800 in the 196 pin package are updated to fix the following issues:

• Wrong pin connection to p0_tx_clkc signal has been corrected .Initially it was with P9.0 the corrected one is P9.1 (only XMC4800).
• Missing alternate function declaration for CCU81 CC80/1/2/3 have been corrected.

Further details can be found in the Release Note.


Device Pack update to v2.1.8:

• A not correct alignment of the bss and data section in XMC4000 linker script files may lead to not correct initialization of the first data in the respective section. This has been corrected

Further details can be found in the Release Note.

How to update:
When starting DAVE an update notification will appear. To install the update click on the notification and follow further instructions.
Alternatively the check for updates functionality can be used:
Press –Help -> Check for DAVE APP Updates (Device Description updates and Device Pack update)


An updated zip file that includes the updates with all libraries to install the update locally can be downloaded from here.

More Demonstration at Embedded World 2016

April 6, 2016, 2:05 am

≫ Next: Communication problem in UART

≪ Previous: April, 05, 2016 New Patch Release of DAVE Device Descriptions and Device Pack.

$

0

0

Digital Power Control with XMC™
Infineon delivers solutions from microamps to megawatts with superior energy efficiency.
We offer highly reliable IGBTs, Power MOSFETs, Power Discretes, Protected Switches, Drivers, IGBT Modules, Intelligent Power Modules (IPMs), Linear Regulators, Motor Control Solutions, LED Drivers, and all forms of AC/DC, DC/DC, and digital power conversion.
Attachment 2238

XMC4000 Safety Package
Functional safety-related applications are becoming increasingly important in the industry. Infineon’s XMC4000 safety package helps industrial OEMs to develop TÜV-certified automation systems that conform to Safety Integrity Levels SIL2 and SIL3.
The XMC4000 safety package also helps cut development times for functional safety software test libraries to approximately one year. This kit was developed specifically for industrial applications such as factory automation, industrial motor control and robotics.
Attachment 2239

Multicoper Full System Solution Featuring IRMD505-1-D µIPM™-DIP
Full system solution for multicopters featuring XMC™ IRMD505-1-D sensorless motor drive reference kit with 3-phase integrated power modules Avnet-Xilinx Ultra Scale Kintex FPGA Reference Design – PMBus™ SupIRBucks
Attachment 2240

Attached Images

• digiral_power.PNG‎ (176.7 KB)
• XMC4_safety_package.PNG‎ (137.2 KB)
• multicopter.PNG‎ (174.2 KB)

Communication problem in UART

April 6, 2016, 3:38 am

≫ Next: XMC 2Go - I2C - RGB Sensor

≪ Previous: More Demonstration at Embedded World 2016

$

0

0

Hello Srikanth,

When the XMC device is first powered up, I expect the UART pin to be uninitialized and at its default low level.
The pin will then be initialized and changed to the high level, which is the passive state for the UART protocol.
After the initialization, will the first transmission be able to take place.

In this case, how does the other controller behaves during this time the GPIO of XMC device is being initialized?
Typically to avoid potential problems related to this, the pin is connected to a pull-up resistor.

Regards,
Min Wei