Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Problems Keil DS-5 and Linux for BeagleBoard

Status
Not open for further replies.

do interior

Member level 3
Member level 3
Joined
Feb 21, 2002
Messages
55
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,288
Location
Brasil
Activity points
355
For various reasons I felt compelled to try to enter the world of embedded Linux, and chose to start with BeagleBoard, which has not yet arrived, and the DS-5 of Keil:

https://www.keil.com/arm/ds5/

After installing the Windows version, decided to play a bit and installed the Git with it got the version of Linux for ARM OMAP:

git clone git: / / git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6

When you try to mount the design, the following error:

**** Build of configuration Default for project Omap ****

make all
'uname' will fail, recognized as an internal command
or external, a program vel oper or a batch file.
-x was unexpected at this time.
Makefile: 535: C: / msysgit/msysgit/linux-omap-2.6/arch / / Makefile: No such file or directory
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
process_begin: CreateProcess (NULL, gcc-print-file-name = include, ...) failed.
Makefile: 1173: *** multiple target patterns. Stop.

The first error refers to the following line of the makefile:

Subarch: = $ (shell uname-m | sed -es/i.86/i386 / -es/sun4u/sparc64 / \
-e s / arm .* / arm /-e s/sa110/arm / \
-e s/s390x/s390-and /-e s/parisc64/parisc / \
-e s / .* ppc / powerpc /-e s / mips .* / mips / \
-e s / sh [234] .* / sh /)

And I imagine many others derive from it, because he can not set the architecture, and not because, I imagine, that this statement was written for Linux and obviously does not work in Windows!
On the other hand, the DS-5 was made for Windows, and if he can not resolve these incompatibilities what good are they?
The makefile has to be changed?
The DS-5 has to be changed?
I have to be changed?
I'm delirious when I think of compiling a Linux kernel in windows?

Added after 3 minutes:

I found another makefile, it has a subarch: = arm,

Subarch: = $ (shell uname-m | sed -es/i.86/i386 / -es/sun4u/sparc64 / \
-e s / arm .* / arm /-e s/sa110/arm / \
-e s/s390x/s390-and /-e s/parisc64/parisc / \
-e s / .* ppc / powerpc /-e s / mips .* / mips / \
-e s / sh [234] .* / sh /)
Subarch: = arm

This solves one problem, but still several others:

**** Build of configuration Default for project OMAP ****

make all
'uname' will fail, recognized as an internal command
or external, a program vel oper or a batch file.
-x was unexpected at this time.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
The system will fail can find the path specified.
Makefile: 1173: *** multiple target patterns. Stop.

In this line, 1173, has this:
$ (clean-dirs):
$ (Q) $ (MAKE) $ (clean) = $ (patsubst _clean_ %,%,$@)

Besides the problem of uname ...
 

Unfortunately, building the Linux kernel from within Windows is virtually impossible. You might be able to do so if you were working with a networked file system where the remote file system understood things like symlinks, but I've never successfully done that. DS-5 for Windows is much more about building applications on top of an existing Linux system and doesn't provide a tremendous amount of kernel debug support, but is a very nice tool for performing application build and debug.

---------- Post added at 08:49 ---------- Previous post was at 08:32 ----------

Unfortunately, building the Linux kernel from within Windows is virtually impossible. You might be able to do so if you were working with a networked file system where the remote file system understood things like symlinks, but I've never successfully done that.

Apparently I was wrong. It seems some folks have used Cygwin as it seems to have some mechanism to replicate symlinks. I'm not sure why DS-5 doesn't provide this sort of mechanism, but I don't think that DS-5 includes all of the other standard Linux utilities required, such as 'tar' and 'ls'. Seems like a good question to bug ARM about.

See the Cygwin site at /ml/cygwin/2007-07/msg00856.html: Claudio Scordino - Re: Compiling a Linux kernel using Cygwin. I'm too new to the list to post URLs.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top