XMC™ Forum Discussions

Hello Infineon,

My project requires using the SMIF (Octal SPI) to transfer from external flash memory into XMC7200 internal RAM through P-DMA.

Based on the 1-D definition of P-DMA in the XMC7200, the maximum transfer size is dependent on the "X_COUNT",

Where "X_COUNT" have a maximum of 256 iterations,

Which equals a maximum of 256*1 Bytes = 256 B of data transferred every P-DMA transfer,  assuming 8-bit data element each transfer.

1. Is there a maximum sequential P-DMA transfer constraint that we should be aware through this approach (SMIF (Octal SPI) to Internal RAM through P-DMA)?

2. If I have 16kB (64 sets of 256 B) of total data to be transferred through P-DMA, is there any easy way to automate and chain this 64 sets of transfer together without the microcontroller being involved after P-DMA transfer have started?

3. Or must the microcontroller be involved after each 256B of data transferred through every P-DMA transfer?

4. If so, is the overhead time spent between each P-DMA reprogramming and triggering significant or in the microsecond order of magnitude?

Hi,

Looking at the latest ModusToolBox 3.2 I couldn't find an Ethercat Example for the board KIT_XMC48_RLX_ECAT_V2.1, is there any plan to port the Dave example to MTB as well?

Best Regards,

Marcelo Macedo - FAE at Neutronics

I am running bldc motor with the help of hall sensor but not able to get full no load speed.This motor has 1000 rpm but getting only upto 3500 rpm.

I am using example code to drive this motor whether this code support 10000 rmp.

My motor is working at 48v,750 W.Could you help to resolve this problem 

Dear All，

               I use the DAVE ide v4  with the nano library， calling the SPI-MASTER-EnableSlaveSelectSignal() and SPI-MASTER-DisableSlaveSelectSignal() functions cannot raise or lower the CS pin of SPI. However, when sending data through SPI, when using an oscilloscope to check the status of SCL and MOSI pins, they generate waveforms that are normal, but the CS pin remains in a high level state. 

              Configure this CS pin as an IO port, manually pull up or down the CS pin, but use the BUSY flag in the TBUF register as the completion of sending. When pulling up the CS pin, there will be a situation where there is still one byte that has not been sent, but the CS pin has been pulled up.

             What may be the reason why the two API functions generated by calling cannot control the CS pin state; How can I avoid manually raising or lowering the CS pin when there is still one byte of data not sent?

Thanks.

XMC4500-E144F1024 AC #

Hello,

Now I can use one TIMER to set one time interval and trigger one event as shown in the picture below.

And project is also attached.

Is it possible that I only use one timer to trigger different event according to different time interval?

Thanks!

BR,

Lila

I would to know what would be an alternative to SAF-XC167CI-16F40F BB for new designs ,that does not require significant code changes.

I also have the old "XMC4800_AUT_Base-V2.1" with obsolete BCM5241 PHYs. Years ago I downloaded the demo software from the website, inserted the secret SSC source part and the board was up and running.

Now I also bought the newer "XMC4800_RELAX_ECAT_V2.1" with ADIN1200 PHYs and I was wondering how I can access the demo project source. I searched the website, I searched the ModusToolbox and I searched the Github with no success. 

Due to the SSC source limitation I know that it is not possible to get the entire project, but isn't there a project with the SSC part removed? Can someone please give me a hint?

Hi,

I am trying to implement the "OTW_Firmware_Upgrade" program in my XMC7100 Lite v1 board. I have implemented Lcs and is able to access other sample programs. 

When I try to implement "OTW_Firmware_Upgrade". I get the error:

 Status: failed

 Messages:

 [1]: there was an error retreiving the asset 'https://github.com/mcu-tools/mcuboot' commit 'v1.9.1-cypress' - Cloning into 'v1.9.1-cypress'..., fatal: unable to access 'https://github.com/mcu-tools/mcuboot/': SSL certificate problem: unable to get local issuer certificate, command 'C:/Users/<user>/ModusToolbox/tools_3.2/modus-shell/bin/bash -c git -C C:/Users/<user>/mtw/secureboot/mtb_shared/mcuboot clone --origin cypress --no-checkout --filter=blob:none https://github.com/mcu-tools/mcuboot v1.9.1-cypress', directory 'C:/Users/<user>/ModusToolbox/tools_3.2/dashboard', child process exited with error code 128

 [2]: Project 'bootloader_cm0p' in application directory 'C:/Users/<user>/mtw/secureboot/OTW_Firmware_Upgrade' - the getlibs operation failed

 [3]: Project 'dfu_cm7' in application directory 'C:/Users/<user>/mtw/secureboot/OTW_Firmware_Upgrade' - the getlibs operation failed

mcuboot v1.8.1-cypress
mcuboot v1.7.2-cypress
mcuboot v1.7.0-cypress
mcuboot v1.6.1-cypress
mcuboot v1.5.0-cypress
...
mtb-example-xmc7000-otw-firmware-upgrade        latest-v2.X
mtb-example-xmc7000-otw-firmware-upgrade        latest-v1.X
mtb-example-xmc7000-otw-firmware-upgrade        release-v2.0.0
mtb-example-xmc7000-otw-firmware-upgrade        release-v1.1.0
mtb-example-xmc7000-otw-firmware-upgrade        release-v1.0.0