2010-11-22 15:05:40     Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Document created by Aaronwu Employee on Oct 16, 2013
Version 1Show Document
  • View in full screen mode

2010-11-22 15:05:40     Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Connor Griffith (UNITED STATES)

Message: 96098   

 

On the Processor Settings tab on the Project->Properties->C/C++ Build->Settings dialog, I'm not able to select a silicon revision for the BF537. The drop down box is greyed out. The command line argument generated by default is -mcpu=bf537-, which is an invalid argument for gcc.

 

Towards the top of the dialog, I see a warning that says, "The configuration support is not installed on the system."

 

The problem just arose today. I believe I created a project last week and this wasn't an issue. I tried completely wiping/reinstalling a couple times, but still get the same problem. For installation, I'm following the directions at http://docs.blackfin.uclinux.org/doku.php?id=toolchain:eclipse:install&s[]=install&s[]=eclipse.

QuoteReplyEditDelete

 

 

2010-11-22 19:46:14     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Connor Griffith (UNITED STATES)

Message: 96099   

 

I decided to work around the silicon revision problem by manually editing the xml in the project file. This isn't really a satisfactory fix, but at least now, the command line arguments are valid, and I can build some bare-metal binaries.

 

Since my hardware isn't in yet, I was wanting to use the similator for debugging. However, when I go to run the debug configuration I get 3 copies of this error:

 

"Error creating session" "Cannot run program "bfin-elf-gdb": Unknown reason"

 

The console also displays this warning:

 

****  WARNING: The "Debug" Configuration may not build  ****

****  because it uses the "Blackfin Bare Metal (bfin-elf)"  ****

****  tool-chain that is unsupported on this system.  ****

 

I'm not getting any hits for these errors in my google searches, so I think the most plausible cause of my problems is that my install is suspect. Is there an easy/good way to verify my install? Perhaps I should post some info from the help->about dialog?

QuoteReplyEditDelete

 

 

2010-11-22 20:01:49     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Mike Frysinger (UNITED STATES)

Message: 96100   

 

what version of eclipse and plugins are you using exactly ?

QuoteReplyEditDelete

 

 

2010-11-23 12:05:27     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Connor Griffith (UNITED STATES)

Message: 96142   

 

I grabbed Eclipse from http://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/heliossr1. It's the 32-bit Linux version running under Ubuntu 10.04 LTS - the Lucid Lynx.

 

From the About Eclipse dialog:

 

Eclipse IDE for C/C++ Developers

 

Version: Helios Service Release 1

Build id: 20100917-0705

 

Here's the list under the Installed Software tab of the Eclipse Installation Details dialog.

 

Blackfin GNU Toolchain Feature

    1.0.2.v201009141522     com.analog.gnu.toolchain.blackfin.feature.group

C/C++ GDB Hardware Debugging     7.0.0.201009241320     org.eclipse.cdt.debug.gdbjtag.feature.group

CollabNet Merge Client     2.2.1     com.collabnet.subversion.merge.feature.feature.group

Eclipse IDE for C/C++ Developers     1.3.1.20100916-1202     epp.package.cpp

Memory Mapped Registers View Feature     1.0.2.v201009141522     com.analog.gnu.debug.mmr.feature.group

Subclipse (Required)     1.6.15     org.tigris.subversion.subclipse.feature.group

Subclipse Integration for Mylyn 3.x (Optional)     3.0.0     org.tigris.subversion.subclipse.mylyn.feature.group

Subversion Client Adapter (Required)     1.6.12     org.tigris.subversion.clientadapter.feature.feature.group

Subversion JavaHL Native Library Adapter (Required)     1.6.13     org.tigris.subversion.clientadapter.javahl.feature.feature.group

Subversion Revision Graph     1.0.9     org.tigris.subversion.subclipse.graph.feature.feature.group

SVNKit Client Adapter (Not required)     1.6.12     org.tigris.subversion.clientadapter.svnkit.feature.feature.group

 

 

 

For reference, if needed, I'm attaching the Eclipse configuration info, an error log, and a file listing of my toolchain install in the /opt directory.

 

error_log

toolchain_install

eclipse_configuration

QuoteReplyEditDelete

 

 

2010-11-23 17:06:31     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Mike Frysinger (UNITED STATES)

Message: 96145   

 

do you have the toolchain in your PATH ?  eclipse works fine when my PATH is configured correctly.  when it is not, the silicon revision is unavailable.

QuoteReplyEditDelete

 

 

2010-11-24 13:46:31     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Connor Griffith (UNITED STATES)

Message: 96180   

 

I believe you got it. That's what I had done differently.

 

Previously, I started Eclipse from the command line where I had edited the .bashrc to include the path. Then I started it in Nautilus, in which case the tool plug-in apparently doesn't configure properly because it's not in PATH in that environment. I'm guessing the plug-in needs to check the versions on the tools to see which silicon revisions are supported?

 

It's important to note that I did edit the project settings to include the correct PATH (C/C++ Build->Environment), which was let me complete a build as stated in the previous post, but at that point, the initialization for Eclipse and the plug-in are apparently over. So, the key seems to be that you must have the toolchain in the PATH for whatever environment you decide to start eclipse in, otherwise the plug-in won't configure properly. And you'll be left with the invalid command line argument =mcpu=bf537-.

QuoteReplyEditDelete

 

 

2010-11-24 13:53:36     Re: Can't select processor silicon revision with Blackfin GNU Toolchain plugin

Connor Griffith (UNITED STATES)

Message: 96181   

 

I forgot to mention that this solved my simulator debug issue too (bfin-elf-gdb failed to start: Unknown reason).

Outcomes