xCORE-XA Module not working

[mon2]

Purchased and received the new xCORE-XA Module through Digikey earlier last week. Just started to test on a fresh Windows 7 platform using the 13.2 toolchain. Drivers have installed fine for this module (ie. J-link driver for the ARM component, etc.)

Attempting to follow the first (simple) LED flashing example and failing as follows:

a) feedback - the color of the LEDs for the XMOS and ARM cores is RED on the received module (not green as implied by the examples) - need to correct with the contract manufacturer of this assembly error and/or revise the supporting documentation to be accurate.

b) If the boot jumpers (J14 & J16) are configured for ARM then the related LEDs are flashing with some factory pre-loaded firmware. This confirms the same referenced LEDs are at least operational. That is, D2 and D4 are not defective.

Moved the dual jumpers (J14 & J16) to MSEL to allow for use of the external flash device as noted in the appnote.

LED jumper (J15) is configured for LED for the D13 routing.

c) Next, moving to created a fresh project using this example and target component XS1-XAU8A-1024-FB265-C5. Applied the source code supplied with the AN00141.

Code generates an error demanding the flag for -std=c99 for the ARM compiler via the makefile to resolve. Applied and now code is error free.

The following warning is posted:

Warning: XN11135 Attribute SystemFrequency is ignored when Oscillator is not specified.

From reading another post on this topic but for other XMOS devices, the XN file must be informed of the clock source.

However, since the XCORE led flashes, this is currently a non-issue.

Q1: What exactly is the format / syntax for this new XA device to resolve this warning ?

Q2: Where exactly is the following line to be applied ?

Documentation notes this flag but no details on where or how it should be applied.

XCORE_ARM_PROJECT = 1

The XCORE .xe compiled binary runs fine and flashes the noted RED led D4. A mix of LEDs onboard flash during the upload before flashing of D4.

The ARM compiled binary fails to flash the noted RED led D2. The ARM binary compiles error free. There is no activity of the same LEDs during the assumed ARM binary upload and D2 fails to flash.

Selected the ARM binary (without the .xe) -> right clicked and selected RUN as...ARM application to launch.

Q3: What is the issue ?

Assuming this code has been tested to work correctly, as a suggestion, consider to post the COMPLETE working code with XN file with MAKEFILE as a sample project for a quick import to get started. Invested over an hour to resolve this broken example without success. Will review the notes on the SiLabs website for more guidance of the Energy Micro / EFM32 core. This should have been a 5 min tutorial.

Q4: Schematics for this module ?

 

 

 

[yuvaraj]

Hi,

 

A1: There is no specific syntax / format need to be followed. In case, if you are creating new project using module board, you should select the target as xCORE-XA Module Board. The other one XS1-XAU8A-1024-FB265-C5 is used during our initial stage of development. However, this can can also be used in case of custom board design. But it is mandatory to provide the Oscillator details, since oscillator frequency selection may vary between users.

A2: XCORE_ARM_PROJECT is used internal to tool, so that when build is given it builds both ARM and xCORE source code together. If this flag is set to '0', even though you have any code on ARM, that will not get compiled. This flag can also be used in xCORE code, if any run time checks required when deploying communication / data transfer between xCORE and ARM.

A3: As mentioned in the application note AN00141 - Appendix B (Page No. 8), the SEGGER gdb sever application needs to be running not only for this application code, for all the ARM related codes that needs to get executed on the target board.

Other things like LED color will get resolved on our next release of document.

-Yuvaraj