XMC™ Forum Discussions

Hallo All,
someone of us has found the same problem?

I have developed a control with FOC Lib (ver. 4.2.45) using the Q024 version of XMC1302 with 64kB flash size.

Now I am trying to migrate to SAME PROCESSOR (with 64kB) but in TSSOP-28 pin-out and, surprise!!, that version of Lib is not supported. I have to work with ver 4.2.12!

This is really strange. I cannot make any Device Migration but I have to develop different solutions.

So, first I would like to know:

• differences between 4.2.12 and 4.2.45 in FOC LIB in order to understand if I can use the older version without any problem
  
• why the 28-pin version is not supported? 28-pin version has same GPIO Ports (P0.x, P1,x and P2.x) and 4 more I/O's
  

This is a little bit difficult to understand for me. I am a little bit worried about using an older version of FOC Lib.

Thank you very much for your support

Best Regards

Fabio Show Less

Greetings,

XMC product used : XMC4700 - 2048 - 357kb ram - 144pin, XMC link - (jlink) debugger

The application that I am developing is hitting the internal RAM limits. My PCB design has an external RAM that I would like to use for storing larger buffers.
My application also has an external flash that we are using with a file system also configured using the EBU.

I have configured the EBU pins so that all three areas are enabled.
EBU Region 1 : 0x6400 0000 for external RAM
EBU Region 2,3 for FLASH.
EBU Region 0 : Unused

I have configured the linker file with a section for the external SRAM

And in my application code I use

__attribute__((aligned(4))) uint8_t test_buffer[1024] __attribute__ ((section ("EXT_RAM"))) = {0};

To ensure that the linker sticks this buffer into the external RAM.

When I try to debug this code with and set a break point where I access this memory the break point does not occur and the code simply goes to the wazoo.

When I probed my pins I could see that the chip select for the external ram was not activated,
I am not sure how the EBU actually toggles the pins when an access occurs so that I can probe it.


I am having a hard time finding an example code/ configuration that shows how to access external ram and interface with. Any help would be awesome!

Additional Notes :
I am using XMC-link probe to debug which is J-link with VSCODE as the IDE.

Thank you in advance. Show Less

Hallo All,
since this chip shortage is a disaster we are in deep trouble since there is no XMC1302 in T038 packaging available.

Some of the most important dealers have some part of the XMC1402. So, considering that the two versions in T038 package seems to have exactly the same PIN-OUT,
do you think it will be really painful to switch betwwen XMC1302 to XMC1402, same FLASH SIZE?

We tried to migrate in DAVE the project from one device to the other, but there is no possibility to do this.
Of course we can build a totally new project (is based on FOC library, to drive a PMSM motor), but before making tests
that are very time-consuming we prefer to ask....maybe is there something we are missing?

Thank you very much for your help!

Ciao to ALL

Fabio Show Less

Hello,

I am currently using the XMC 2 GO kit and if i add the APP "ADC_MESUREMENT_0" and generate the code and build the project i always get an error ('XMC_VADC_GLOBAL_SHS_AREF_EXTERNAL_VDD_UPPER_RANGE' undeclared (first use in this function) and i can't solve it.
I am new with this microcontrollers so i have some dificulties. The error can be seen in the attached image and it is present in the library.
Can you help me please solving this error? Show Less

I seem to have encountered an bug in the library
XMClib v2.2.0
@file xmc_can.c
@date 2020-03-17.
function
XMC_CAN_STATUS_t XMC_CAN_MO_ReceiveData (XMC_CAN_MO_t * can_mo)

Line 746 looks like this:
while ((rx_pnd! = 0U) || (new_data! = 0U));

this form hangs in an infinite loop, since new_data == 1.

in working library XMClib v2.1.24 xmc_can.c from 2019-06-26 this line looks different:
while ((rx_pnd! = 0U) && (new_data! = 0U));

And it works, the actual function of the new version is different only in this place. Show Less