Question 1

[#7290] Blackfin GNU tool chain Eclipse plug-in does not support ADSP-BF60x

Accepted Answer

[#7290] Blackfin GNU tool chain Eclipse plug-in does not support ADSP-BF60x 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-08-27 03:27:52 Close Date 
 2012-08-30 08:54:45 
 Priority: 
 Medium High Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Fixed Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 All 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Blackfin GNU tool chain Eclipse plug-in does not support ADSP-BF60x 
 Details: 
 1, Install the Blackfin GNU tool chain Eclipse plug-ins into Juno 
 2, Create a new project 
 3, Try to choose BF609 
 Follow-ups 
 --- Andrew McLachlan 2012-08-30 09:52:58 
 Fixed in Blackfin GNU tool chain Eclipse plug-in v1.0.6. 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 Untitled.png image/png 58976 Andrew McLachlan 
 
 Attachments: 
 
 Untitled.png

Question 2

[#7318] Ensure that -mmulticore -mcore0 is set on Eclipse ADSP-BF561/BF60x project creation

Accepted Answer

[#7318] Ensure that -mmulticore -mcore0 is set on Eclipse ADSP-BF561/BF60x project creation 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-09-11 05:32:22 Close Date 
 2012-10-10 03:32:56 
 Priority: 
 Medium High Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Fixed Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Ensure that -mmulticore -mcore0 is set on Eclipse ADSP-BF561/BF60x project creation 
 Details: 
 #7317 and #7313 outline an issue with running a program on Core 0 that could 
 have easily been avoided. 
 Although #7317 (GCC should generate code for Core 0 by default) would mean that 
 an out-of-the box BF609 single project would run on Core 0, an App-per-core 
 project set-up would fail, if we were to create two projects. 
 We therefore require the setting of "-mmulticore -mcore0" during New project 
 creation in Eclipse too. And, perhaps, the ability to toggle the core nicely 
 in the Tools Settings. 
 Follow-ups 
 --- Andrew McLachlan 2012-10-10 04:34:27 
 Fixed in plug-ins version 1.0.7. 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 No Files Were Found

Question 3

[#7317] GCC should generate code for Core 0 by default

Accepted Answer

[#7317] GCC should generate code for Core 0 by default 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-09-11 05:26:23 Close Date 
 2012-10-02 05:36:28 
 Priority: 
 Medium High Assignee: 
 Stuart Henderson 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Fixed Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 All 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: GCC should generate code for Core 0 by default 
 Details: 
 Building file: ../src/fooBar.c 
 Invoking: Blackfin ELF C Compiler 
 bfin-elf-gcc -O0 -g3 -Wall -c -fmessage-length=0 -mcpu=bf609-any -MMD -MP 
 -MF"src/fooBar.d" -MT"src/fooBar.d" -o 
 "src/fooBar.o" "../src/fooBar.c" 
 Building target: fooBar 
 Invoking: Blackfin ELF C Linker 
 bfin-elf-gcc -mcpu=bf609-any -o "fooBar" ./src/fooBar.o 
 Finished building target: fooBar 
 The above program is built for Core 1 instead of Core 0 (-mmulticore -mcore0), 
 so loading it onto Core 0 cause a crash/error. 
 This tracker issue is about making the default build target Core 0. 
 Follow-ups 
 No Messages Were Found 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 No Files Were Found

Question 4

[#7313] bfin-gdbproxy crashes when attempting to load an executable on Windows

Accepted Answer

[#7313] bfin-gdbproxy crashes when attempting to load an executable on Windows 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-09-06 09:23:59 
 Priority: 
 High Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 N/A Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 Windows 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Open Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: bfin-gdbproxy crashes when attempting to load an executable on Windows 
 Details: 
 1, cd <a working directory> 
 2, Run bfin-gdbproxy in CMD 
 Remote proxy for GDB, v0.7.2 
 3, Run bfin-elf-gdb in a separate CMD 
 4, In bfin-elf-gdb -- target remote:2000 
 5, load fooBar (attached) 
 6, See crash box (screenshot attached) 
 This happens using a gnICE jtag or ICE-100B (modified to work with GNU tools). 
 Connected to ADSP-BF609. 
 Follow-ups 
 --- Jie Zhang 2012-09-06 11:04:04 
 "File not found." for fooBar and Capture.PNG. 
 --- Andrew McLachlan 2012-09-06 11:11:39 
 The fooBar binary is just an empty "int main() { return 0; }" 
 program. 
 The Capture.PNG was a screenshot showing my version, which is in the 
 description anyway, and a picture of the oh so helpful crash box. 
 Let me know if you are able to reproduce the issue using the steps above 
 and an empty main program built for bf609-any. 
 --- Jie Zhang 2012-09-06 11:14:19 
 What's the command line you used for building fooBar? 
 --- Andrew McLachlan 2012-09-06 11:22:26 
 Building file: ../src/fooBar.c 
 Invoking: Blackfin ELF C Compiler 
 bfin-elf-gcc -O0 -g3 -Wall -c -fmessage-length=0 -mcpu=bf609-any -MMD -MP 
 -MF"src/fooBar.d" -MT"src/fooBar.d" -o 
 "src/fooBar.o" "../src/fooBar.c" 
 Building target: fooBar 
 Invoking: Blackfin ELF C Linker 
 bfin-elf-gcc -mcpu=bf609-any -o "fooBar" ./src/fooBar.o 
 Finished building target: fooBar 
 --- Jie Zhang 2012-09-06 11:38:53 
 After "target" but before "load", try this: 
 (gdb) info thread 
 What do you see? 
 --- Andrew McLachlan 2012-09-06 11:42:12 
 E:\EclipseSDK\workspace\fooBar\Debug>bfin-elf-gdb 
 GNU gdb 6.6 
 This GDB was configured as "--host=i386-mingw32msvc 
 --target=bfin-elf". 
 (gdb) target remote:2000 
 Remote debugging using :2000 
 [New Thread 1] 
 [New Thread 2] 
 0xffa0883a in ?? () 
 (gdb) info thread 
 2 Thread 2 (Core 1 DBGSTAT [0x1000]) 0x038c00a3 in ?? () 
 * 1 Thread 1 (Core 0 DBGSTAT [0x0018]) 0xffa0883a in ?? () 
 (gdb) 
 --- Jie Zhang 2012-09-06 13:09:51 
 This issue should have been fixed in trunk. You are trying to load program into 
 Core 1, which is locked. The gdbproxy in 2012R1 release has a bug which prevent 
 it from loading the program. Two workarounds are available: 
 1. Build the program for Core 0 instead of Core 1 with proper GCC options 
 "-mmulticore -mcore0". So this bug will not triggered. Actually I 
 think GCC should generate code for Core 0 by default. 
 2. You can build gdbproxy from the trunk and replace the executable in 2012R1 
 installation with the one. With the new gdbproxy, you can load the program into 
 Core 1 even it's locked, but if you want to execute it, you will need add option 
 "--unlock-on-connect" to gdbproxy to unlock the Core 1. 
 --- Andrew McLachlan 2012-09-07 04:24:44 
 Thanks. So there are three items here: 
 1, I need to check when the gdbproxy bug that prevents the program from 
 loading 
 will make it into the Release. 
 2, "GCC should generate code for Core 0 by default" 
 Chase up to see if we can make it so. 
 2, The Eclipse plug-in needs to ensure the -mcore option is set when 
 creating Projects for Devonshire (and presumably similar for ADSP-BF561). 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 fooBar application/octet-stream 32992 Andrew McLachlan 
 fooBar application/octet-stream 32992 Andrew McLachlan 
 Capture.PNG image/png 234920 Andrew McLachlan

Attachments:

5305.Capture.PNG

fooBar.zip

5277.fooBar.zip

Question 5

[#7305] bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows

Accepted Answer

[#7305] bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-09-03 03:39:40 Close Date 
 2012-09-28 12:25:54 
 Priority: 
 High Assignee: 
 Jie Zhang 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Rejected Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 Windows 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows 
 Details: 
 Trying to connect to ADSP-BF609 rev 1.2 with ICE-100B 
 (firmware version is 2.0.7) 
 http://docs.blackfin.uclinux.org/doku.php?id=hw:jtag:ice100b says 
 that the firmware must be >= 1.0.7 
 -- GNU tools running under Cygwin on Windows 7 64bit -- 
 $ bfin-jtag.exe 
 cable probe 
 Found USB cable: ICE-100B 
 (no more output) 
 $ bfin-gdbproxy.exe 
 Remote proxy for GDB, v0.7.2, Copyright (C) 1999 Quality Quorum Inc. 
 MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood 
 Blackfin adaption Copyright (C) 2008 Analog Devices, Inc. 
 GDBproxy comes with ABSOLUTELY NO WARRANTY; for details 
 use `--warranty' option. This is Open Source software. You are 
 welcome to redistribute it under certain conditions. Use the 
 '--copying' option for details. 
 Found USB cable: ICE-100B 
 error: bfin: cable initialization failed 
 -- Ubuntu running through Virtualbox -- 
 $ sudo ./bfin-gdbproxy 
 Remote proxy for GDB, v0.7.2, Copyright (C) 1999 Quality Quorum Inc. 
 MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood 
 Blackfin adaption Copyright (C) 2008 Analog Devices, Inc. 
 GDBproxy comes with ABSOLUTELY NO WARRANTY; for details 
 use `--warranty' option. This is Open Source software. You are 
 welcome to redistribute it under certain conditions. Use the 
 '--copying' option for details. 
 Found USB cable: ICE-100B 
 ICE-100B firmware version is 2.0.7 
 IR length: 5 
 Chain length: 1 
 Device Id: 00000010100000000100000011001011 (0x028040CB) 
 Manufacturer: Analog Devices, Inc. (0x0CB) 
 Part(0): SDU (0x2804) 
 Stepping: 0 
 Filename: ./../share/urjtag/analog/sdu/sdu 
 warning: bfin: no board selected, 3 parts are detected 
 warning: bfin: parts: [BF609 BF609] SDU 
 notice: bfin: jc: waiting on TCP port 2001 
 notice: bfin: jc: (you must connect GDB before using jtag console) 
 notice: bfin-gdbproxy: waiting on TCP port 2000 
 $ sudo ./bfin-gdbproxy 
 Remote proxy for GDB, v0.7.2, Copyright (C) 1999 Quality Quorum Inc. 
 MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood 
 Blackfin adaption Copyright (C) 2008 Analog Devices, Inc. 
 GDBproxy comes with ABSOLUTELY NO WARRANTY; for details 
 use `--warranty' option. This is Open Source software. You are 
 welcome to redistribute it under certain conditions. Use the 
 '--copying' option for details. 
 Found USB cable: ICE-100B 
 ICE-100B firmware version is 2.0.7 
 IR length: 5 
 Chain length: 1 
 Device Id: 00000010100000000100000011001011 (0x028040CB) 
 Manufacturer: Analog Devices, Inc. (0x0CB) 
 Part(0): SDU (0x2804) 
 Stepping: 0 
 Filename: ./../share/urjtag/analog/sdu/sdu 
 warning: bfin: no board selected, 3 parts are detected 
 warning: bfin: parts: [BF609 BF609] SDU 
 notice: bfin: jc: waiting on TCP port 2001 
 notice: bfin: jc: (you must connect GDB before using jtag console) 
 notice: bfin-gdbproxy: waiting on TCP port 2000 
 Follow-ups 
 --- Andrew McLachlan 2012-09-03 04:44:28 
 running under CMD (run As Administrator), I get similar results to Cygwin: 
 bfin-jtag: 
 jtag> cable probe 
 Found USB cable: ICE-100B 
 error: libusb error: libusb_open() failed: -12 
 bfin-gdbproxy: 
 Found USB cable: ICE-100B 
 error: bfin: cable initialization failed 
 --- Mike Frysinger 2012-09-05 15:11:37 
 this is expected behavior documented in the wiki: 
 http://docs.blackfin.uclinux.org/doku.php?id=hw:jtag:ice100b#use_different_usb_pids_for_visualdsp_and_urjtag_gdbproxy 
 --- Andrew McLachlan 2012-09-06 08:12:22 
 I now understand the set-up. Sadly, this means that it isn't very straight- 
 forward to debug a CCES project and then swap to debugging a GNU project 
 without messing with drivers and jumpers. 
 --- Jie Zhang 2012-09-06 11:04:50 
 Not a bug. 
 --- Mike Frysinger 2012-09-06 13:26:14 
 yes, as long as the VDSP windows drivers use their own usb stack (rather than 
 the usermode usb driver), there's not much the open source side can do. once 
 (if?) they convert to the usermode usb driver, then things will "just 
 work" with urjtag. 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 No Files Were Found

Question 6

[#7300] kernel build with busybox 1.20 by trunk head toolchain and uClibc 0.9.33.2 boot up fails

Accepted Answer

[#7300] kernel build with busybox 1.20 by trunk head toolchain and uClibc 0.9.33.2 boot up fails Submitted By: Mingquan Pan Open Date 2012-08-31 02:08:57 Close Date 2012-10-08 05:08:12 Priority: High Assignee: Mingquan Pan Sonic Zhang Stuart Henderson Board: N/A Silicon Revision: Resolution: Fixed Fixed In Release: N/A Processor: ALL Host Operating System: toolchain rev.: kernel rev.: State: Closed Found In Release: 2012R2 Is this bug repeatable?: N/A Summary: kernel build with busybox 1.20 by trunk head toolchain and uClibc 0.9.33.2 boot up fails Details: kernel build with busybox 1.20 by trunk head toolchain boot up fails. ## Booting kernel from Legacy Image at 01000000 ... Image Name: bf609-0.0-3.5.0-ADI-2012R1-pre-0 Image Type: Blackfin Linux Kernel Image (gzip compressed) Data Size: 8942598 Bytes = 8.5 MiB Load Address: 00001000 Entry Point: 0028da80 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting Kernel at = 0028da80 Linux version 3.5.0-ADI-2012R1-pre-00831-g3fee378-dirty (test@test-OptiPlex-390) (gcc version 4.3.5 (ADI-trunk/svn-5865) ) #2 Fri Aug 31 13:23:10 CST 2012 register early platform devices bootconsole [early_shadow0] enabled ERROR: Not running on ADSP-BF609: unknown CPUID 0x0000 Rev 0.0 bootconsole [early_BFuart0] enabled early printk enabled on early_BFuart0 Board Memory: 128MB Kernel Managed Memory: 128MB Memory map: fixedcode = 0x00000400-0x00000490 text = 0x00001000-0x001becb0 rodata = 0x001becd4-0x0024eb10 bss = 0x0024f000-0x00262314 data = 0x00262320-0x0028a000 stack = 0x00288000-0x0028a000 init = 0x0028a000-0x009ce000 available = 0x009ce000-0x07f00000 DMA Zone = 0x07f00000-0x08000000 Hardware Trace active and enabled Blackfin support (C) 2004-2010 Analog Devices, Inc. Compiled for ADSP-BF609 Rev 0.0 Blackfin Linux support by http://blackfin.uclinux.org/ Processor Speed: 500 MHz core clock, 100 MHz SCLk, 100 MHz SCLK0, 100 MHz SCLK1 and 250 MHz DCLK NOMPU: setting up cplb tables Instruction Cache Enabled for CPU0 External memory: cacheable in instruction cache L2 SRAM : uncacheable in instruction cache Data Cache Enabled for CPU0 External memory: cacheable (write-back) in data cache L2 SRAM : uncacheable in data cache Built 1 zonelists in Zone order, mobility grouping off. Total pages: 32258 Kernel command line: root=/dev/mtdblock0 rw clkin_hz=(25000000) earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=10.100.4.50:10.100.4.174:192.168.0.1:255.255.255.0:bf609-ezkit:eth0:off PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory available: 118840k/131072k RAM, (7440k init code, 1783k kernel code, 813k data, 1024k dma, 1172k reserved) NR_IRQS:299 Configuring Blackfin Priority Driven Interrupts console [ttyBF0] enabled, bootconsole disabled console [ttyBF0] enabled, bootconsole disabled Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 devtmpfs: initialized Blackfin Scratchpad data SRAM: 4 KB Blackfin L1 Data A SRAM: 16 KB (9 KB free) Blackfin L1 Data B SRAM: 16 KB (16 KB free) Blackfin L1 Instruction SRAM: 64 KB (51 KB free) Blackfin L2 SRAM: 256 KB (256 KB free) NET: Registered protocol family 16 Blackfin DMA Controller ezkit_init(): registering device resources ezkit_init(): request emac pins failed bio: create slab at 0 SCSI subsystem initialized bfin-spi bfin-spi.0: master is unqueued, this is deprecated bfin-spi bfin-spi.0: bfin-spi probe success bfin-spi bfin-spi.1: master is unqueued, this is deprecated bfin-spi bfin-spi.1: bfin-spi probe success usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c-bfin-twi i2c-bfin-twi.0: Blackfin on-chip I2C TWI Contoller, regs_base@ffc01e00 i2c-bfin-twi i2c-bfin-twi.1: Blackfin on-chip I2C TWI Contoller, regs_base@ffc01f00 NET: Registered protocol family 23 Switching to clocksource bfin_cs_cycles NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 msgmni has been set to 232 io scheduler noop registered (default) bfin-uart: Blackfin serial driver bfin-uart.0: ttyBF0 at MMIO 0xffc02000 (irq = 96) is a BFIN-UART physmap platform flash device: 01000000 at b0000000 physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x008821 Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method Using auto-unlock on power-up/resume cfi_cmdset_0001: Erase suspend on write enabled Creating 3 MTD partitions on "physmap-flash.0": 0x000000000000-0x000000080000 : "bootloader(nor)" 0x000000080000-0x000000480000 : "linux kernel(nor)" 0x000000480000-0x000001000000 : "file system(nor)" m25p80 spi0.1: w25q32 (4096 Kbytes) Creating 3 MTD partitions on "m25p80": 0x000000000000-0x000000080000 : "bootloader(spi)" 0x000000080000-0x000000200000 : "linux kernel(spi)" 0x000000200000-0x000000400000 : "file system(spi)" CAN device driver interface bfin_can bfin_can.0: bfin_can device registered(®_base=ffc00a00, rx_irq=55, tx_irq=56, err_irq=57, sclk=100000000) DWMAC100 No HW DMA feature register supported Enhanced/Alternate descriptors RX IPC Checksum Offload not configured. stmmac_dvr_probe: warning: cannot get CSR clock stmmac: probed eth0: PHY ID 20005c90 at 1 IRQ 0 (stmmac-0:01) active Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) input: bfin-rotary as /devices/platform/bfin-rotary/input/input0 i2c /dev entries driver bfin_wdt: initialized: timeout=20 sec (nowayout=0) dma_alloc_init: dma_page @ 0x0540e000 - 256 pages at 0x07f00000 usbcore: registered new interface driver usbhid usbhid: USB HID core driver TCP: cubic registered NET: Registered protocol family 17 can: controller area network core (rev 20090105 abi 8) NET: Registered protocol family 29 eth0: device MAC address 06:72:82:ba:e9:17 No MAC Management Counters available IP-Config: Gateway not on directly connected network Freeing unused kernel memory: 7440k freed Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 Hardware Trace: 0 Target : <0x001be964> { _dump_stack + 0x0 } Source : <0x001bea04> { _panic + 0x68 } CALL pcrel 1 Target : <0x001be9f2> { _panic + 0x56 } Source : <0x0000c3b2> { _test_taint + 0x2a } RTS 2 Target : <0x0000c388> { _test_taint + 0x0 } Source : <0x001be9ee> { _panic + 0x52 } JUMP.L 3 Target : <0x001be9ec> { _panic + 0x50 } Source : <0x001bebaa> { _printk + 0x26 } RTS 4 Target : <0x001beba6> { _printk + 0x22 } Source : <0x0000e406> { _vprintk_emit + 0x11e } RTS 5 Target : <0x0000e3fe> { _vprintk_emit + 0x116 } Source : <0xffa00d30> { __common_int_entry + 0xcc } RTI 6 Target : <0xffa00cce> { __common_int_entry + 0x6a } Source : <0xffa00b18> { _return_from_int + 0x58 } RTS 7 Target : <0xffa00b18> { _return_from_int + 0x58 } Source : <0xffa00aee> { _return_from_int + 0x2e } IF !CC JUMP pcrel 8 Target : <0xffa00ac0> { _return_from_int + 0x0 } Source : <0xffa00cca> { __common_int_entry + 0x66 } JUMP.L 9 Target : <0xffa00cc8> { __common_int_entry + 0x64 } Source : <0xffa00fa8> { _do_irq + 0x1c } RTS 10 Target : <0xffa00fa2> { _do_irq + 0x16 } Source : <0xffa00474> { _asm_do_IRQ + 0x60 } RTS 11 Target : <0xffa0046c> { _asm_do_IRQ + 0x58 } Source : <0x00012672> { _irq_exit + 0x4a } RTS 12 Target : <0x0001266e> { _irq_exit + 0x46 } Source : <0x0003c13c> { _rcu_irq_exit + 0x4c } RTS 13 Target : <0x0003c136> { _rcu_irq_exit + 0x46 } Source : <0x0003c128> { _rcu_irq_exit + 0x38 } IF CC JUMP pcrel (BP) 14 Target : <0x0003c126> { _rcu_irq_exit + 0x36 } Source : <0x0003c094> { _rcu_idle_enter_common + 0x38 } RTS 15 Target : <0x0003c08e> { _rcu_idle_enter_common + 0x32 } Source : <0x0003c072> { _rcu_idle_enter_common + 0x16 } IF !CC JUMP pcrel Stack info: SP: [0x0401fe64] <0x0401fe64> /* kernel dynamic memory (maybe user-space) */ FP: (0x0401ff04) Memory from 0x0401fe60 to 04020000 0401fe60: 00000000 [00000000] 0401fe88 001bea08 00010e08 00207e2c 0000f80a 002532bc 0401fe80: 00000001 0401feb0 0401fed4 00010c28 00010e08 00000001 0401dd60 0401dd60 0401fea0: ffffe000 054af728 054b8c50 0401dd60 00000100 00000008 00000000 0401fec8 0401fec0: 00269230 00000001 0401fec8 0401fec8 0401de80 0401ff04 00010e14 00010e08 0401fee0: 00000001 054b8b00 00000000 ffffe000 054af728 054b8c50 00000000 00000000 0401ff00: 00000000 (00000000) 00000000 00000000 00000000 000067e0 054b8c50 0401ff20: 054af728 054bce58 00008000 00000000 00000000 04020000 054bce58 054bce58 0401ff40:<054bcda0> ffa00f6a 00002002 054bcd6b 00000001 054bcd6a 00000000 00000000 0401ff60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0401ff80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0401ffa0: 00000000 00000000 00000000 00000001 000002b8 054dfd04 054dfea0 054dff80 0401ffc0: 000001c8 054b8b00 054dff80 00000000 00000001 00000002 00000117 054af728 0401ffe0: 054b8c50 000067e0 0000001b 054b8bf0 00000001 00000001 00000001 00002806 Return addresses in stack: frame 1 : <0xffa0097e> { _system_call + 0x6a } address : <0x054bcda0> /* kernel dynamic memory (maybe user-space) */ Follow-ups --- Sonic Zhang 2012-09-10 07:33:27 There are 2 issues in the new uClibc 0.9.33.2. One is the vfork blackfin implementation is missing. The other is the FDPIC dynamic library loader is not compatible with the FDPIC dynamic library generated by Blackfin GNU toolchain. --- Sonic Zhang 2012-09-21 02:29:25 Now FDPIC buildroot Linux image can boot up on bf609 with 2 patches attached. Patch 1 shows where the FDPIC library loader crash occurs. Patch 2 changes the type of var i from unsigned int to int. The following loop is a decreasing loop, stop condition “i>=0” always meets in case of unsigned int. --- Stuart Henderson 2012-09-25 09:38:18 this should be fixed now. --- Mingquan Pan 2012-10-08 06:09:39 Yes, it boots up now. Close. Files Changes Commits Dependencies Duplicates Associations Tags File Name File Type File Size Posted By uClibc-0.3.99.2-2.patch application/octet-stream 398 Sonic Zhang uClibc-0.3.99.2-1.patch application/octet-stream 454 Sonic Zhang Attachments: uClibc-0.3.99.2-1.patch.zip uClibc-0.3.99.2-2.patch.zip

Question 7

[#7299] Blackfin GNU tool chain Eclipse Memory Mapped Registers View plug-in uses outdated proc files and does not support ADSP-BF60x

Accepted Answer

[#7299] Blackfin GNU tool chain Eclipse Memory Mapped Registers View plug-in uses outdated proc files and does not support ADSP-BF60x 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-08-30 10:34:19 
 Priority: 
 Medium Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 N/A Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Open Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Blackfin GNU tool chain Eclipse Memory Mapped Registers View plug-in uses outdated proc files and does not support ADSP-BF60x 
 Details: 
 The Blackfin GNU tool chain Eclipse Memory Mapped Registers View plug-in 
 uses out-dated proc files for MMR definitions and does not support ADSP-BF60x. 
 The proc XML files for discovering MMR definitions are dated 2009 and 
 should be spruced up to mirror the newly released CrossCore Embedded Studio. 
 Support for ADSP-BF60x is also not available in the MMR View plug-in. 
 Follow-ups 
 No Messages Were Found 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 No Files Were Found

Question 8

[#7293] Blackfin GNU tool chain Eclipse plug-in reports "This discovery method is deprecated" when used with Juno Release

Accepted Answer

[#7293] Blackfin GNU tool chain Eclipse plug-in reports "This discovery method is deprecated" when used with Juno Release 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-08-27 07:35:35 
 Priority: 
 Medium Assignee: 
 Nobody 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 N/A Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 All 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Open Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Blackfin GNU tool chain Eclipse plug-in reports "This discovery method is deprecated" when used with Juno Release 
 Details: 
 1, Install Eclipse Juno release 
 2, Install the Blackfin GNU tool chain Eclipse plug-ins into Juno 
 3, Create a new "Blackfin Linux FDPIC GNU Toolchain (bfin-linux-uclibc)" project for BF538 
 4, Visit Properties > C/C++ Build > Discovery Options 
 at the bottom of the dialog reads 
 "This discovery method is deprecated, use 'Preprocessor Include Paths' instead" 
 The discovery appears to still work, but will be phased out in Kepler, I presume. 
 Follow-ups 
 No Messages Were Found 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 DeprectatedJunoFDPIC.PNG image/png 100304 Andrew McLachlan

Attachments:

DeprectatedJunoFDPIC.PNG

Question 9

[#7292] Blackfin GNU tool chain Eclipse plug-in reports "WARNING: The "Debug" Configuration may not build"

Accepted Answer

[#7292] Blackfin GNU tool chain Eclipse plug-in reports "WARNING: The "Debug" Configuration may not build" 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-08-27 06:59:30 Close Date 
 2012-08-30 08:55:14 
 Priority: 
 Medium Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Fixed Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 All 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Blackfin GNU tool chain Eclipse plug-in reports "WARNING: The "Debug" Configuration may not build" 
 Details: 
 1, Install the Blackfin GNU tool chain Eclipse plug-ins into Juno 
 2, Create a new "Blackfin Linux FDPIC GNU Toolchain (bfin-linux-uclibc)" project for BF538 
 3, Build the project 
 **** Build of configuration Debug for project test **** 
 **** WARNING: The "Debug" Configuration may not build **** 
 **** because it uses the "Blackfin Linux FDPIC GNU Toolchain (bfin-linux-uclibc)" **** 
 **** tool-chain that is unsupported on this system. **** 
 **** Attempting to build... **** 
 make all 
 'Building file: ../system/adi_initialize.c' 
 'Invoking: Blackfin FDPIC C Compiler' 
 bfin-linux-uclibc-gcc -D_DEBUG -I"C:\Users\amclach\Desktop\CCES Workspace	est\system" -O0 -g3 -Wall -c -fmessage-length=0 -mcpu=bf549m-any -MMD -MP -MF"system/adi_initialize.d" -MT"system/adi_initialize.d" -o "system/adi_initialize.o" "../system/adi_initialize.c" 
 'Finished building: ../system/adi_initialize.c' 
 ' ' 
 'Building file: ../src/test.c' 
 'Invoking: Blackfin FDPIC C Compiler' 
 bfin-linux-uclibc-gcc -D_DEBUG -I"C:\Users\amclach\Desktop\CCES Workspace	est\system" -O0 -g3 -Wall -c -fmessage-length=0 -mcpu=bf549m-any -MMD -MP -MF"src/test.d" -MT"src/test.d" -o "src/test.o" "../src/test.c" 
 'Finished building: ../src/test.c' 
 ' ' 
 'Building target: test' 
 'Invoking: Blackfin FDPIC C Linker' 
 bfin-linux-uclibc-gcc -mcpu=bf549m-any -o "test" ./system/adi_initialize.o ./src/test.o 
 'Finished building target: test' 
 ' ' 
 The issue is that the `bfin-linux-uclibc-ldr` command has not been filled in for the Blackfin Loader Tools Settings. 
 Workaround: add bfin-linux-uclibc-ldr explicitly to command entry box. 
 Additional: the Loader settings are not necessarily needed for this type of project set-up. 
 Ideally, we'd have an "Artifact type: Loader file" and make visible|enable/invisible|disable 
 the Loader tools settings according to the Artifact selection. 
 Follow-ups 
 --- Andrew McLachlan 2012-08-30 09:53:26 
 Fixed in Blackfin GNU tool chain Eclipse plug-in v1.0.6. 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 No Files Were Found

Question 10

[#7291] Blackfin GNU tool chain Eclipse plug-in does not specify -mcpu for Assembly source

Accepted Answer

[#7291] Blackfin GNU tool chain Eclipse plug-in does not specify -mcpu for Assembly source 
 Submitted By: Andrew McLachlan 
 Open Date 
 2012-08-27 05:34:16 Close Date 
 2012-08-30 08:55:00 
 Priority: 
 Medium High Assignee: 
 Andrew McLachlan 
 Board: 
 N/A Silicon Revision: 
 Resolution: 
 Fixed Fixed In Release: 
 N/A 
 Processor: 
 ALL 
 Host Operating System: 
 All 
 toolchain rev.: 
 kernel rev.: 
 State: 
 Closed Found In Release: 
 2012R1 
 Is this bug repeatable?: 
 N/A 
 Summary: Blackfin GNU tool chain Eclipse plug-in does not specify -mcpu for Assembly source 
 Details: 
 1, Install the Blackfin GNU tool chain Eclipse plug-ins into Juno 
 2, Create a new project for BF538 
 3, Build the project 
 make all 
 'Building file: ../src/fff.asm' 
 'Invoking: Blackfin ELF Assembler' 
 bfin-elf-as -o "src/fff.o" "../src/fff.asm" 
 make all 
 'Building file: ../src/fff.c' 
 'Invoking: Blackfin ELF C Compiler' 
 bfin-elf-gcc -O0 -g3 -Wall -c -fmessage-length=0 **-mcpu=bf538-any** -MMD -MP -MF"src/fff.d" -MT"src/fff.d" -o "src/fff.o" "../src/fff.c" 
 Follow-ups 
 --- Andrew McLachlan 2012-08-30 09:53:13 
 Fixed in Blackfin GNU tool chain Eclipse plug-in v1.0.6. 
 Files 
 Changes 
 Commits 
 Dependencies 
 Duplicates 
 Associations 
 Tags 
 File Name File Type File Size Posted By 
 Capture2.PNG image/png 24593 Andrew McLachlan 
 Capture.PNG image/png 25798 Andrew McLachlan

Attachments:

Capture.PNG

Capture2.PNG

Electronic Design Services - PartnerZone

Parent for all content moved from GNU Archive: FAQ