xrun: Binary not correctly downloaded to target device Topic is solved

Technical questions regarding the XTC tools and programming with XMOS.
Post Reply
aelder
Active Member
Posts: 37
Joined: Mon Sep 24, 2012 1:45 pm

xrun: Binary not correctly downloaded to target device

Post by aelder »

Elsewhere in the fourm I have read that this error comes from
- power supplies
- clocks
- USB cables
- WIN10 XTAG-3 issues

I'm trying to bring up a new design on custom hardware and am wondering if there is any way to narrow down the error report.

I've also been trying to get
xflash --erase-all
to work as a reference point, but that doesn't seem to work either. In fact it doesn't even work on the xCORE 200 eXplorer board I have:

Code: Select all

C:\Program Files (x86)\XMOS\xTIMEcomposer\Community_14.3.2\targets\XCORE-200-EXPLORER>xflash -l

Available XMOS Devices
----------------------

  ID    Name                    Adapter ID      Devices
  --    ----                    ----------      -------
  0     XMOS XTAG-3             o45FAPya        O[0]


C:\Program Files (x86)\XMOS\xTIMEcomposer\Community_14.3.2\targets\XCORE-200-EXPLORER>xflash --erase-all --target-file XCORE-200-EXPLORER.xn
Error: F03136 No devices attached - Cannot run the enquirer until a device is found
so that is weird. Any suggestions on how to proceed?


View Solution
aelder
Active Member
Posts: 37
Joined: Mon Sep 24, 2012 1:45 pm

Post by aelder »

Trying to run something gives

Code: Select all

C:\asi\sw\utility\asi2700>xrun --verbose --jtag-speed 1 asi2700_xmos_factory.xe
cmd xgdb
cmd -q
cmd --return-child-result
cmd --ex
cmd "set $xcore_id=0"
cmd --ex
cmd "set $xcore_boot=1"
cmd -x
cmd C:\Users\MAXSON~1\AppData\Local\Temp/.xrun7864-L8GC86NA/xeload_auto.gdb
cmd --ex
cmd quit
cmd "asi2700_xmos_factory.xe"
cmd %??uÄ
cmd
0x00000000 in ?? ()
Loading image to XCore 0
Loading section .crt, size 0xac lma 0x40000
Loading section .init, size 0x1a lma 0x400ac
Loading section .fini, size 0x2e lma 0x400c6
Loading section .text, size 0x4df0 lma 0x400f4
Loading section .eh_frame, size 0x24 lma 0x44ee4
Loading section .cp.rodata, size 0x12 lma 0x44f08
Loading section .cp.rodata.4, size 0x478 lma 0x44f1c
Loading section .cp.const4, size 0x24 lma 0x45394
Loading section .cp.rodata.string, size 0xae lma 0x453b8
Loading section .cp.rodata.cst4, size 0x78 lma 0x45468
Loading section .ctors, size 0x44 lma 0x454e0
Loading section .dtors, size 0x44 lma 0x45524
Loading section .dp.data, size 0x840 lma 0x45568
Loading section .dp.data.4, size 0x34 lma 0x45da8
Loading section .dp.rodata, size 0x18 lma 0x45de0
Loading section .dp.rodata.4, size 0x44 lma 0x45df8
Start address 0x40000, load size 24116
Transfer rate: 130 KB/sec, 1507 bytes/write.
xrun: Binary not correctly downloaded to target device
 
User avatar
mon2
XCore Legend
Posts: 1913
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Post by mon2 »

Hi. Can you post the relevant parts of your schematic for a review?

1) Is the power sequencing correct?

2) Ample current for each voltage rail?

3) Based on the many reviewed designs to date, most are related to poor assembly of the PCB itself so be sure to check the soldering of the XMOS device for starters.
matthew1
Active Member
Posts: 48
Joined: Mon Oct 19, 2015 2:12 pm

Post by matthew1 »

There's a known issue with xrun/xflash on Windows with tools 14.3.2. Please can you try updating to 14.3.3 which includes a fix?

https://www.xmos.com/support/tools

Regards,

Matthew.
XMOS
aelder
Active Member
Posts: 37
Joined: Mon Sep 24, 2012 1:45 pm

Post by aelder »

Our hardware engineer found a bad PLL voltage, so this is now fixed. Something electrical wrong - as implied here.
Post Reply