Hello Martin
Re your first question if you are looking to use uCLinux then pick a
suitable processor. Unless the hardware budget is very, very, very tight
you will save endless amounts of time, energy, thus money using a
processor with suitable hardware resources. You'll get excellent and
fre
This illustrates the two extremes of development methodology and I won't
pick sides, ... If you are planning to work with uClinux you will
need to get some grasp of command line and Linux operation anyway.
To clarify, the approach I outlined uses the standard Win32 ports of the
GCC tool chain
Running on Windows 7 ...
$ m68k-uclinux-c++ -v
gcc version 4.3.3 (Sourcery G++ Lite 4.3-209)
On 19/01/2010 19:44, Oleks Zhadan wrote:
Hi,
I am pretty sure that one of the free lite revisions from
http://www.codesourcery.com/sgpp/lite/coldfire/portal/subscripti...@template=lite
has c++ support
On 08/02/2010 12:27, Philippe De Muyter wrote:
Hello all,
I don't know if this is the best place to ask, but as I see some ARM-related
trafic here, here is my question :
Could you point me to ARM cortex a9 based development or evaluation boards
with a (uc)linux port of course ?
http://www.
Ciao Fabio
Excuse the pedantic posting. It is CodeSorcery, not CodeSurgery. Though
the English in me likes the proximity :)
Sorcery: Stregoneria
Surgery: Chirurgia
CSLite is fine for compiling user apps.
Why are you messing with elf2flt?
ATB
On 21/03/2010 20:56, Fabio Giovagnini wrote:
H
Here's the problem: I need to program some hardware via 2 pins of the
PIO (1 clock, 1 data). Timing constraints are tight - 10ms clock cycle
time. All this, of course, whilst I maintain very high level services
(CAN bus, TCP/IP). The downstream unit also ACKS by asserting a PIO pin,
configured
On a Coldfire 5233/5235/5307, you can use one of the programmable
interrupt timers to get a 10ms interval. This is a less evil solution
than using the timer tick. I don't know if all Coldfire processors
have more than one PIT though since I am by no means a Coldfire
expert. Note that on at leas
Why does the latest release still use obsolete command line options for
tail? And does anyone know how I can fix this on Ubuntu 9 without
manually extracting everything? The POSIX env. variable trick appears to
be ignored :(
Thx++
___
uClinux-dev m
You could try editing it and changing the tail command, providing your
editor is smart and doesn't touch the rest of the file.
Other wise , use head and tail to pull the script off the front, change it
and then put it back together.
Lastly, try the attached tail script. Put in ~/bin or so
Dave,
On 25/03/2010 04:04, Dave Rensberger wrote:
After I manually added the 'asm' link, the uClibc build stopped reporting that error, but still
went on to report that all of the syscall symbols ("__NR_*") were undeclared (even though
they're clearly declared n the "unistd.h" file.
Not su
I am trying to build the September 2003 version of the 2.4 kernel for
the SSV 5280 Coldfire (no MMU) using the CodeSorcery m68k-ucLinux tools
on Windows 7/Cygwin. This tool chain works for user-mode binaries.
Questions arising -
1. Does anyone know if the Code Sorcery cross compiler works with
I've got an extremely simple SIGINT handler that throws a C++
exception to ensure proper cleanup etc. I can see from console spew that
the signal handler is being called but the exception is not caught. What
appears is more generic:
terminate called after throwing an instance of 'signal_excep
Hello Wolfgang
If you throw an exception from the context of your signal handler, why do you
expect that it is thrown in the context of the main thread?
I think your expectations are flawed.
This is precisely why I am asking the question :). given that the
application has a single main thread
If you look at the documentation for signal handlers, you'll see that they
get called asynchronous to normal program flow
Thanks Gavin for that confirmation.
Would it be fair to say that the article here understates the threading
issues?
http://www.ibm.com/developerworks/linux/library/l-cp
I'm writing firmware for a BF526 based device that has to operate in
very low power mode for extended periods of time. Prototypes typically
sleep for ~30s, keeping code in SDRAM in self-refresh mode, wake for a
few seconds to do the necessary processing, then return to sleep. With
existing code
Apologies if this is the wrong list. Directions appreciated if so.
I'm running Linux version 3.0.8-ADI-2011R1 on a standard BF526 EZBRD.
I'm trying to establish if suspend to memory is working in general on
the 526 or, for some reason, simply not on this board.
The boot log indicates the RTC
16 matches
Mail list logo
