What devices will run Java bytecode?

Slow ones ?

Well they don't have to be slow!

-- "When you have to choose between a first-rate company with a second-rate product and a second-rate company with a first-rate product, it's never an ideal choice. " -Ed

Sun used to make a Java chip. I don't know what happened to that.

Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.

Sun used to make a Java chip. I don't know what happened to that.

Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.

Sun used to make a Java chip. I don't know what happened to that.

Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.

JStamp?

I can't name a whole bunch of them but I've used JStamp and its pretty easy. I never benchmarked it, but at 74 Mhz it is pretty fast.

--
|\/|  /|  |2  |<
mehaase(at)sas(dot)upenn(dot)edu

Well . .. maybe everything is relative.

I'm just imagining encrypting or dycrypting with a 4096 bit PGP key

--
"When you have to choose between a first-rate company with a 
second-rate product and a second-rate company with a first-rate 
product, it's never an ideal choice. " -Ed (www.overclockers.com)

LOL

I obviously don't know enough about java to write to right questions.

--
"When you have to choose between a first-rate company with a 
second-rate product and a second-rate company with a first-rate 
product, it's never an ideal choice. " -Ed (www.overclockers.com)
"

Have you looked at some of the Blackberry devices? e.g.

It appears that development for this device is primarily Java based. There is developer info on their website - It looks comprehensive, although I haven't used it.

If you find a list of Java enabled devices, then post back and let us know. However, I think it might be a case of trawling each manufacturer's web site, or maybe post your question on a handhelds newsgroup, if such a thing exists - I would guess it does.

Regards,

Paul.

--
Remove _rem_ before replying by email.

Mummm, it was a really stupid idea ?

test

This is from my link-list (untested)

And there are ARM-micros which are able to run java-byte code (?).

hope it helps

Greetings Klaus

"Correlious" schreef in bericht news: snipped-for-privacy@z14g2000cwz.googlegroups.com...

ARM now has Jazelle, which defines a Java-compatible instruction set and allows for a Java co-processor.

ARM core whith JAVA support :)

This message was sent using the comp.arch.embedded web interface o

Hello,

For an embedded Java application you need stick with J2ME.

The JOP is a bytecode execution w/o OS on an FPGA.

A nice design and fast, but requires some understanding of hardware and the tools and hardware extensions are limited.

A lot of the ARM core devices run a Linux 2.6 and this allows you to have a JVM working. Some link were already posted, but I do like the

Very cheap and huge community behind it. For a $100 dollar you get a XScale preconfigured and lots of extendable hardware.

What kind of application do you intend?

Luc The Perverse wrote:

I'm curious, does anybody know how much additional cost overhead is involved with this combination (Jazelle and a Java co-processor) over a comparable PIC or Atmel AVR processor, which wasn't designed to work with Java?

A friend of mine is a desktop developer and often argues that development time is dramatically reduced by programming in interpreted languages, such as Java because developers don't have to worry about memory leaks, buffer overflows, etc. In the embedded systems world, however, I can easily fathom a situation where cost of manufacturing would eventually outweigh the costs saved by programming in Java.

For example, let's say that it costs a company $20,000 to develop the software for some embedded system project in Java and $100 per device to manufacture this product with some kind of Java co-processor included. If we were to sell 20,000 units in the first year, we would be up to $2,020,000 in costs, which includes the cost of developing the software and manufacturing of each device. Now lets say that it takes double the money to develop the code for the same product in a combination of C and Assembly. So that's $40,000 to develop the code; but, we no longer require the Java co-processor, so our product (in this fictional example) costs only $50 to manufacture each unit. Again, we sell 20,000 units of our product. In this example, our overhead for the first year is $1,040,000, which is a little more than half that of the original product that we developed in Java.

I'm not trying to start a language war here or anything. I would just like to know how close to a real world situation my example actually is.

Thank you,

--
Sean

This one takes bytecode directly: