And if you want to enable 3rd parties to develop applications for
your device you would IMO be pretty crazy to do it in native
code. It's considerations like that which are driving the adoption
of Java in consumer electronics.
We got pretty insane learning every bug and limitation and quirk
On Tuesday 03 February 2009 12:32:48 Jamie Lokier wrote:
Chris Gray wrote:
On Monday 02 February 2009 22:01:12 Jamie Lokier wrote:
I didn't use Java because I thought it wouldn't fit, to be honest.
There's about 10MB free on my 64MB device (32 allocated to video
coprocessors, away
Chris Gray wrote:
On Monday 02 February 2009 22:01:12 Jamie Lokier wrote:
I didn't use Java because I thought it wouldn't fit, to be honest.
There's about 10MB free on my 64MB device (32 allocated to video
coprocessors, away from Linux; the rest is used by Linux, utils etc.)
I found
Jonathan Wong wrote:
Hi Jamie,
My solution is to use Sigma's GCC 2.95.3 when building a program that
links
to their libraries, but use newer GCC for other programs (that don't use
Sigma's libraries at all).
And then use JNI to call Sigma's libraries? That dashes my hopes to port
Jamie Lokier wrote:
On my video player, the control program just runs the media player in
a child process and talks over a pipe to it, in simple text commands.
So the control program can be in any language, in theory.
small
This is also quite handy when the codec crashes or gets stuck...
the
On Monday 02 February 2009 22:01:12 Jamie Lokier wrote:
I didn't use Java because I thought it wouldn't fit, to be honest.
There's about 10MB free on my 64MB device (32 allocated to video
coprocessors, away from Linux; the rest is used by Linux, utils etc.)
I found that's actually not enough
On Monday 02 February 2009 22:16:07 Jamie Lokier wrote:
Jamie Lokier wrote:
On my video player, the control program just runs the media player in
a child process and talks over a pipe to it, in simple text commands.
So the control program can be in any language, in theory.
small
This is
Jonathan Wong wrote:
I won't need a web browser, just a thin client to communicate with a
central server.
You can write a client in any language. Java seems a bit heavy and
hard to get going, if you don't specifically need Java on it.
I was just told our device doesn't have RAM at all, only
On Sunday 01 February 2009 06:44:38 Jamie Lokier wrote:
EM8623 is an ARM7 I believe, with no MMU.
For SMP8634 and beyond, they switched to MIPS with MMU :-)
The codesourcery toolchain uses ARM EABI, but the Sigma Designs
libraries as OABI, so watch out. You have to use the right
Hi Jamie,
My solution is to use Sigma's GCC 2.95.3 when building a program that links
to their libraries, but use newer GCC for other programs (that don't use
Sigma's libraries at all).
And then use JNI to call Sigma's libraries? That dashes my hopes to port whatever I do on the
Sigma to
Hi Chris,
I'm pretty sure Mika can still be compiled with gcc 2.95.3, J9 might be more
problematic - but if it's physically possible the Apogee guys can do it. :-)
I don't need the latest and greatest JVM there is. Just something that works and is easy to
program. Mika compiled with gcc
Hi Chris,
Can I use your Mika? Is the EM8623 an ARM9 or ARM7?
I need to create a media player and include web connectivity (very thin web client). Do I use CLDC
or CDC? It could come down to size constraints, though.
I was told codecs are included in the processor. Is that possible, or just
Jonathan Wong wrote:
Can I use your Mika? Is the EM8623 an ARM9 or ARM7?
EM8623 is an ARM7 I believe, with no MMU.
For SMP8634 and beyond, they switched to MIPS with MMU :-)
The codesourcery toolchain uses ARM EABI, but the Sigma Designs
libraries as OABI, so watch out. You have to use the
Hi Jamie,
I won't need a web browser, just a thin client to communicate with a central
server.
I was just told our device doesn't have RAM at all, only 8MB ROM. Is that
possible?
All these EABI/OABI stuff seems complicated. I have to compile different parts of my application
with different
My hardware has only 8MB ROM.
My zImage is just 1.9 MB. And this is all that is needed in ROM, as it
contains the root file system as the boot strategy is just using
initRANMFS for everything.
On boot time the zImage is loaded into RAM and extracts itself and the
root file system.
This
On Tuesday 27 January 2009 06:09, Jonathan Wong wrote:
Anyone happens to know the minimum size of IBM's J9? Anyone tried to run
J9 on uCLinux?
I don't know off the top of my head, but I could find out for you. It will
depend on the type of Java profile you need to support, for example the
Hi,
What is the minimum size of uCLinux?
My hardware has only 8MB ROM.
Anyone happens to know the minimum size of IBM's J9? Anyone tried to run
J9 on uCLinux?
My hardware specs:
Video Controller
EM8623 and SMP864x/865x Video Processor
ROM Size
8 MB
HDD Type
IDE ATAPI
17 matches
Mail list logo
