"recipe for target" error

September 21, 2016, 12:26 pm

≫ Next: E_EEPROM_XMC1 returns INCONSISTENT_BLOCK after a few write-read-verify

Hi

I'm using 4.2.8 and have checked for updates as well as app updates.

I've made a new workspace "C:\Workspaces\DAVE-4.2\ADC".
In this workspace I created a new DAVE CE Project for a XMC4504-F100x512

Doing nothing more than this i get a "recipe for target" compiler error when I build the project.

Problem occurs almost at the end of the build, while building xmc_usbh.o
It did successfully build numerous library files before getting to xmc_usbh, which I've removed most of due to thread size limitations on forum

What am I missing?

Code:

10:50:57 **** Build of configuration Debug for project adc ****

"\"C:\\DAVEv4\\DAVE-4.2.4\\eclipse\\ARM-GCC-49\\bin\\make\"" --output-sync -j4 all 

'Building file: ../Startup/startup_XMC4504.S'

'Invoking: ARM-GCC Assembler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Startup/startup_XMC4504.o" -x assembler-with-cpp -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -Wall -Wa,-adhlns="Startup/startup_XMC4504.o.lst" -mfloat-abi=softfp -c -fmessage-length=0 -MMD -MP -MF"Startup/startup_XMC4504.d" -MT"Startup/startup_XMC4504.d Startup/startup_XMC4504.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Startup/startup_XMC4504.o" "../Startup/startup_XMC4504.S"

'Finished building: ../Startup/startup_XMC4504.S'



'Building file: ../Startup/system_XMC4500.c'

'Invoking: ARM-GCC C Compiler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Startup/system_XMC4500.o" -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Infineon/XMC4500_series/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries" -O0 -ffunction-sections -fdata-sections -Wall -std=gnu99 -mfloat-abi=softfp -Wa,-adhlns="Startup/system_XMC4500.o.lst" -pipe -c -fmessage-length=0 -MMD -MP -MF"Startup/system_XMC4500.d" -MT"Startup/system_XMC4500.d Startup/system_XMC4500.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Startup/system_XMC4500.o" "../Startup/system_XMC4500.c"

'Finished building: ../Startup/system_XMC4500.c'



'Building file: ../Libraries/XMCLib/src/xmc_usbh.c'

'Invoking: ARM-GCC C Compiler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Libraries/XMCLib/src/xmc_usbh.o" -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Infineon/XMC4500_series/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries" -O0 -ffunction-sections -fdata-sections -Wall -std=gnu99 -mfloat-abi=softfp -Wa,-adhlns="Libraries/XMCLib/src/xmc_usbh.o.lst" -pipe -c -fmessage-length=0 -MMD -MP -MF"Libraries/XMCLib/src/xmc_usbh.d" -MT"Libraries/XMCLib/src/xmc_usbh.d Libraries/XMCLib/src/xmc_usbh.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Libraries/XMCLib/src/xmc_usbh.o" "../Libraries/XMCLib/src/xmc_usbh.c"

Libraries/XMCLib/src/subdir.mk:111: recipe for target 'Libraries/XMCLib/src/xmc_usbh.o' failed

../Libraries/XMCLib/src/xmc_usbh.c: In function 'XMC_USBH_PowerControl':

../Libraries/XMCLib/src/xmc_usbh.c:403:43: error: 'XMC_SCU_PERIPHERAL_RESET_USB0' undeclared (first use in this function)

       XMC_SCU_RESET_AssertPeripheralReset(XMC_SCU_PERIPHERAL_RESET_USB0); /* reset USB */

                                           ^

../Libraries/XMCLib/src/xmc_usbh.c:403:43: note: each undeclared identifier is reported only once for each function it appears in

make: *** [Libraries/XMCLib/src/xmc_usbh.o] Error 1

make: *** Waiting for unfinished jobs....

'Building file: ../Libraries/XMCLib/src/xmc_usbd.c'

'Invoking: ARM-GCC C Compiler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Libraries/XMCLib/src/xmc_usbd.o" -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Infineon/XMC4500_series/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries" -O0 -ffunction-sections -fdata-sections -Wall -std=gnu99 -mfloat-abi=softfp -Wa,-adhlns="Libraries/XMCLib/src/xmc_usbd.o.lst" -pipe -c -fmessage-length=0 -MMD -MP -MF"Libraries/XMCLib/src/xmc_usbd.d" -MT"Libraries/XMCLib/src/xmc_usbd.d Libraries/XMCLib/src/xmc_usbd.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Libraries/XMCLib/src/xmc_usbd.o" "../Libraries/XMCLib/src/xmc_usbd.c"

'Finished building: ../Libraries/XMCLib/src/xmc_usbd.c'



'Building file: ../Libraries/XMCLib/src/xmc_usic.c'

'Invoking: ARM-GCC C Compiler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Libraries/XMCLib/src/xmc_usic.o" -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Infineon/XMC4500_series/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries" -O0 -ffunction-sections -fdata-sections -Wall -std=gnu99 -mfloat-abi=softfp -Wa,-adhlns="Libraries/XMCLib/src/xmc_usic.o.lst" -pipe -c -fmessage-length=0 -MMD -MP -MF"Libraries/XMCLib/src/xmc_usic.d" -MT"Libraries/XMCLib/src/xmc_usic.d Libraries/XMCLib/src/xmc_usic.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Libraries/XMCLib/src/xmc_usic.o" "../Libraries/XMCLib/src/xmc_usic.c"

'Finished building: ../Libraries/XMCLib/src/xmc_usic.c'



'Building file: ../Libraries/XMCLib/src/xmc_vadc.c'

'Invoking: ARM-GCC C Compiler'

"C:\DAVEv4\DAVE-4.2.4\eclipse\ARM-GCC-49/bin/arm-none-eabi-gcc" -MMD -MT "Libraries/XMCLib/src/xmc_vadc.o" -DXMC4504_F100x512 -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries\XMCLib\inc" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc/Libraries/CMSIS/Infineon/XMC4500_series/Include" -I"C:\Workspaces\DAVE-4.2\ADC\adc" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Dave\Generated" -I"C:\Workspaces\DAVE-4.2\ADC\adc\Libraries" -O0 -ffunction-sections -fdata-sections -Wall -std=gnu99 -mfloat-abi=softfp -Wa,-adhlns="Libraries/XMCLib/src/xmc_vadc.o.lst" -pipe -c -fmessage-length=0 -MMD -MP -MF"Libraries/XMCLib/src/xmc_vadc.d" -MT"Libraries/XMCLib/src/xmc_vadc.d Libraries/XMCLib/src/xmc_vadc.o" -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -g -gdwarf-2 -o "Libraries/XMCLib/src/xmc_vadc.o" "../Libraries/XMCLib/src/xmc_vadc.c"

'Finished building: ../Libraries/XMCLib/src/xmc_vadc.c'





10:51:10 Build Finished (took 13s.16ms)

↧

E_EEPROM_XMC1 returns INCONSISTENT_BLOCK after a few write-read-verify

September 21, 2016, 10:05 pm

≫ Next: The Example code of AP32337 - XMC1000 - Software update

≪ Previous: "recipe for target" error

Issue:
On write-read-verify of emulated data eeprom, after a few cycles of write-read-verify, the read will return E_EEPROM_XMC1_OPERATION_STATUS_INCONSISTENT_BLOCK on XMC1302-Q040-0064.

Questions:
Has anyone faced emulated data eeprom write-read-verify reliability issue using DAVE4 E_EEPROM Appls v4.1.6 or later on XMC1302-Q040-0064?

Regression:
1. create a instance of emulated data eeprom, with size 512, and allocate 2 block of data, 96bytes, and 32bytes each.
2. perform a erase at the start of code.
3. setup a 100ms timer to make changes to data eeprom content. The content is read, incremented, and write back to emulated data eeprom.
4. insert breakpoint after READ or WRITE or GETINFO functions.

NOTE: problem surface on XMC1302 Q040-0064. Problem does NOT surface on XMC1302 T038-0200.

Environment:
1. DAVE v4.2.8
2. E_EEPROM APP v4.1.6 andv4.1.8
3. Windows 7 Pro 64bit
4. 1st Target XMC1302 Q040-0064 64kB chip.
4. 2nd Target XMC1302 T038-0200 200kB chip (bootkit)

.7z ZIP contains a DAVE4 project that was purpose built to show this issue can be provided upon request. Following is the extract of the .c/.h

Code:

#include <DAVE.h>



typedef uint64_t U64;

typedef uint32_t U32;

typedef uint16_t U16;

typedef uint8_t U8;

typedef int64_t S64;

typedef int32_t S32;

typedef int16_t S16;

typedef int8_t S8;

typedef _Bool FLAG;



#define K_PAGE                6

#define K_LO_CNT        96

#define K_HI_CNT        32



typedef struct {

        E_EEPROM_XMC1_OPERATION_STATUS_t status;

        E_EEPROM_XMC1_STATUS_t status_2;

        U16 busy_Read_HI, busy_Read_LO;

        U16 busy_Write_HI, busy_Write_LO;

        U8 lo_Vol[K_LO_CNT], hi_Vol[K_HI_CNT];

} DE2_REC;





typedef struct {

        DE2_REC de2;

} RUN_TIME;



RUN_TIME my;



void DE2_Read_Reliability() {

        U8 i = 0;

        my.de2.status_2 = E_EEPROM_XMC1_GetStatus();

        if (my.de2.status_2 == E_EEPROM_XMC1_STATUS_IDLE) {

                for (i=0; i<K_HI_CNT; i++) my.de2.hi_Vol[i] = 0;

                my.de2.status = E_EEPROM_XMC1_Read(DE2_HI_VOL, 0, &my.de2.hi_Vol[0], K_HI_CNT);

                if (my.de2.status!=E_EEPROM_XMC1_OPERATION_STATUS_SUCCESS) {

                        my.de2.status_2 = E_EEPROM_XMC1_GetStatus();

                        if (my.de2.status_2 == E_EEPROM_XMC1_STATUS_IDLE) {

                                my.de2.status = E_EEPROM_XMC1_Write(DE2_HI_VOL, &my.de2.hi_Vol[0]);

                        } else my.de2.busy_Write_HI++;

                } else {

                        for (i=0; i<K_HI_CNT; i++) my.de2.hi_Vol[i]++;

                        my.de2.status_2 = E_EEPROM_XMC1_GetStatus();

                        if (my.de2.status_2 == E_EEPROM_XMC1_STATUS_IDLE) {

//DIGITAL_IO_SetOutputHigh(&DIGITAL_IO_0);

                                my.de2.status = E_EEPROM_XMC1_Write(DE2_HI_VOL, &my.de2.hi_Vol[0]);

//DIGITAL_IO_SetOutputLow(&DIGITAL_IO_0);

                        } else my.de2.busy_Write_HI++;

                }

        } else my.de2.busy_Read_HI++;

}

↧

The Example code of AP32337 - XMC1000 - Software update

September 21, 2016, 10:06 pm

≫ Next: XMC4800 Firmware update

≪ Previous: E_EEPROM_XMC1 returns INCONSISTENT_BLOCK after a few write-read-verify

Try this

http://www.infineon.com/dgdl/Infineo...b5e955bcf&sd=t

↧

XMC4800 Firmware update

September 21, 2016, 11:57 pm

≫ Next: Hardware supported copter simulator

≪ Previous: The Example code of AP32337 - XMC1000 - Software update

Beside this you may need these files which are described in the application note.

Attached Files

Copy to Desktop.zip‎ (54.0 KB)

↧

Hardware supported copter simulator

September 22, 2016, 4:31 am

≫ Next: Sept 7, 2016 New Release of DAVE, DAVE APPs and other Libraries

≪ Previous: XMC4800 Firmware update

Great job of Gerhard building this amazing copter simulator! :-)

↧

Sept 7, 2016 New Release of DAVE, DAVE APPs and other Libraries

September 22, 2016, 4:00 pm

≫ Next: Get active on XMC, DAVE Forums and Be Rewarded!

≪ Previous: Hardware supported copter simulator

thanks. we need this

↧

Get active on XMC, DAVE Forums and Be Rewarded!

September 23, 2016, 3:30 am

≫ Next: Get active on XMC, DAVE Forums and Be Rewarded!

≪ Previous: Sept 7, 2016 New Release of DAVE, DAVE APPs and other Libraries

From our Apple Watch winner Niclas:

Attachment 2600

Thank you for your active participation and contribution! :)

Attached Images

IMG_20160911_1714000.jpg‎ (187.6 KB)

↧

Get active on XMC, DAVE Forums and Be Rewarded!

September 23, 2016, 3:31 am

≫ Next: TC23x MultiCAN+ sample code

≪ Previous: Get active on XMC, DAVE Forums and Be Rewarded!

From our Apple Watch winner Niclas:

Attachment 2601

Thank you for your active participation and contribution! :)

Attached Images

IMG_20160911_1714000.jpg‎ (187.6 KB)

↧

TC23x MultiCAN+ sample code

September 23, 2016, 3:55 am

≫ Next: XMC1100 : Driving WS2812 LED

≪ Previous: Get active on XMC, DAVE Forums and Be Rewarded!

Hello,

I am using Aurix TC23x (single core TQFP 100 version) .I need sample code of initializing MultiCAN+ module.
I am bit confused in terms fCAN & fCLC which registers i need to set for setting these frequencies.

Also i wanted to use CAN FD feature of it. Anybody is having sample code?

↧

XMC1100 : Driving WS2812 LED

September 23, 2016, 8:31 am

≫ Next: what is time stamp mode in multican xmc4500 ????

≪ Previous: TC23x MultiCAN+ sample code

Hi all,

I'm driving a string of WS2812 LEDs with XMC1100 . WS2812 is an RGB LED with builtin controller, datasheet http://cdn.sparkfun.com/datasheets/C...LED/WS2812.pdf The WS2812 requires an unusual waveform but with a quite tight signal timing, +/- 150ns (see page 4 of datasheet).

Currently I am using a bit banging approach which relies on a lot of NOPs, this works, but is sensitive to compiler, optimisation and other variances.

So the question is, is there anything in XMC1100 (e.g. with CCUs) that might be able to generate the required waveform more efficiently and more reliably? And ideally, easily portable between different XMC MCUs.

Cheers

↧

what is time stamp mode in multican xmc4500 ????

September 24, 2016, 12:22 am

≫ Next: DAVE TIP of the day: How to build and include a static library?

≪ Previous: XMC1100 : Driving WS2812 LED

Hi,
I am working on XMC4500, in Multican there is a Timestamp mode is there, in reference manual the information regarding Timestamp not understanding can anybody tell
what is the purpose of that mode?

Thanks and Regards,
Harshan.

↧

DAVE TIP of the day: How to build and include a static library?

September 26, 2016, 5:28 am

≫ Next: Git Icon Decorations in Git 4

≪ Previous: what is time stamp mode in multican xmc4500 ????

I am able to get the code to compile and link just fine and I am able to debug it with DAVE 4.3.2. However, I have two remaining questions:

1. Since my main application is set "Active", the library project is not active but it is open. How do I get DAVE not to "gray out" the source code when I view and modify the library source?

2. If I modify the library source, how do I get DAVE to automatically compile the necessary library code when I build my active application project?

Thanks in advance.

↧

Git Icon Decorations in Git 4

September 26, 2016, 10:30 am

≫ Next: BS50015-1TAD SSmart Hi-Side Power Switch tripping issue.

≪ Previous: DAVE TIP of the day: How to build and include a static library?

... answering my own question here.

I added a C/C++ Perspective and then all the decorators showed up. I switched back to the DAVE IDE perspective and the decorators stayed. Exit DAVE and restart, decorators are gone.

By the way, any customization of toolbar icons within the DAVE IDE perspective get messed up as well. Maybe it is a perspective thing in general?

↧

BS50015-1TAD SSmart Hi-Side Power Switch tripping issue.

September 26, 2016, 3:29 pm

≫ Next: Modbus TCP

≪ Previous: Git Icon Decorations in Git 4

Quote:

Originally Posted by decosse

... One thought I am having is that I did not employ a Vs Snubber circuit and starting to think that it is transient on the Vs side that is causing the issue
...

I have confirmed that the problem is definitely being caused by the lack of the snubber - even with non-ideal values a quick test improved the situation no-end!
I completely underestimated the impact of the Vs contribution

↧

Modbus TCP

September 27, 2016, 1:12 am

≫ Next: ThreadX support

≪ Previous: BS50015-1TAD SSmart Hi-Side Power Switch tripping issue.

Hi,

Are you using in your project SYSTIMER APP?

Regards,
Jesus

↧

ThreadX support

September 27, 2016, 1:15 am

≫ Next: Xmc4500 plc

≪ Previous: Modbus TCP

Hi,

In expresslogic web page, under legacy downloads you can find example of ThreadX for XMC products: http://rtos.com/downloads/threadx_legacy_downloads
For more details please contact directly expresslogic.

Regards,
Jesus

↧

Xmc4500 plc

September 28, 2016, 2:03 am

≫ Next: Bluetooth Communication

≪ Previous: ThreadX support

A curious question: how to write PLC program and program it to XMC microcontrollers?

↧

Bluetooth Communication

September 28, 2016, 10:09 am

≫ Next: Multicore Programming on Tricore

≪ Previous: Xmc4500 plc

Quote:

Originally Posted by GiffordHladek

I cant understand that how it is possible with pin scurity. yes its joke in bluetooth world

how can you say this is joke? anything is possible..

↧

Multicore Programming on Tricore

September 29, 2016, 1:14 am

≫ Next: Regular PWM vs Randomized Sigma-Delta (LED driver)

≪ Previous: Bluetooth Communication

Hi,

Thought some of you might be interested to hear that some of the aspects that I addressed here, have been poored into an application note that you'll find here:

Code:

http://www.altium.com/white-papers/appnote-aurix-multi-core-tricore-programming-essentials

In addition we made a matching offline desktop recording that follows the same storyline:

Code:

http://go.altium.com/tasking-tricore-webinar-september-2016-recording.html

Best regards,

Henk-Piet Glas
Technical Product Specialist

↧

Regular PWM vs Randomized Sigma-Delta (LED driver)

September 29, 2016, 1:41 am

≫ Next: Sept 29, 2016 DAVE APP Patch Release

≪ Previous: Multicore Programming on Tricore

I came to a project where some LED lamps are being controlled with Randomized Sigma-Delta PDM. Each lamp has one MCU and about 100 cold white LEDs and more 100 warm white LEDs.

The PCB is divided in the main part (with the first 10 LEDs, MCU and a few sensors) and the rest just dumb LEDs with current driver.

The MCU uses 4 PDM outputs: 2 (cold light PDM + warm light PDM) used on the main part and the other 2 carried on to the rest of the board.

I was wondering why not use simple PWM? Is that only due to EMI? If so, is it possible to estimate (magnitude at leas) how worse the EMI could be using normal PWM with constant pulse width within a cycle?

The way I see you cannot use too low frequencies with normal PWM because you probably see the flickering and also not to high frequencies to avoid high EMI.

But I was wondering if you still can use normal PWM with good/similar results (so it's even much easier to verify the result with an o'scope later compared to random pulses, for example.).

Here's the reference for the datasheet explaining the Randomized Sigma Delta PDM:

XMC BCCU

and the Regular PWM is the normal PWM you usually find in MCU's which you only set the frequency and the duty cycle and you get a regular square wave.

↧