Jam Byte-Code Player for 8051

Hallo all,

I'm trying to implement Jam Byte-Code player using the source code(8051 Jam byte code player) provided by Altera. The code only supports version 1 Jam byte-code. But the Quartus II tool generates Version 2 Jam byte-code. What to do?

Thanks a lot in advance.

Dani

Reply to
dani
Loading thread data ...

"dani" schrieb im Newsbeitrag news: snipped-for-privacy@g14g2000cwa.googlegroups.com...

there are even more 'variants' of the JAM/STAPL code, and even more issues. Unfortunatly it seems that while Altera is still using JAM internally it has completly dropped any support of JAM for 3rd party developers. I guess they where pissed off when the attemp to promote JAM as JEDEC standard failed. So Altera decided to "show off" and stopped publishing uptodate versions of the JAM tools.

So basicall you are on your own, with no support from Altera, grab the latest what they have for download (what is ages old ASFAIK) and start updating the player to support whatever Quartus thinks the current JAM should support. You may have even to reverse engineer Q generated JAM files on that path.

of course it all depends what you need todo, I implemented a simple JTAG bitstream loader for AVR, the all program code occupies less than 200 code words and uses very simple bytecode player.

my 3cents Antti

Reply to
Antti Lukats

Thanks Antti,

Altera always talking about how successful the Jam Player is. I thought this is the right way to implement CPLD update in field using software. They publish the source code for Jam Byte-Code Player. But I'v never found a description of the Jam Byte-Code format. And the source code from Altera is also not well commented. If they do not really support the Jam player, they shouldn't promote it as an easy using, portable stuff.

Regards

Dani

Reply to
dani

"dani" schrieb im Newsbeitrag news: snipped-for-privacy@o13g2000cwo.googlegroups.com...

oh well they promote it :) just not updating the user resources and no support.

there are several non altera uses of JAM as well, as example FS2 and Actel are using JAM, Xilinx tools can generate JAM (STAPL) but there is always a potential problem that the versions do have mismatch or something prevents the JAM useage. If you are working only with JAM files from single tool you should be ok though.

Antti PS several FPGA vendors promote their JTAG stuff, Altera JAM, Xilinx XSVF, Lattice ispVM, etc.. all of them have problems. XSVF is changed with every new version of impact, the old player doesnt accept the new commands... everywhere about the same story

Reply to
Antti Lukats

Do you have any other information source which could be insteresting for me? You can just drop me the links which I find on the Web.

Thanks

Dani

Reply to
dani

Is there another alternative to loading up an ALTERA FPGA????

george

Reply to
GMM50

"GMM50" schrieb im Newsbeitrag news: snipped-for-privacy@g43g2000cwa.googlegroups.com...

sure! you can use either slave serial mode or make your own jtag "micro" loader.

Antti

Reply to
Antti Lukats

The C source code for the Jam Bytecode Player version 2.2 is available at

formatting link
Altera has not published a version ported to the 8051 platform, because of the large memory requirements of the application, but an 8051 expert should be able to create an optimized version.

The Jam STAPL format is a JEDEC standard, JESD71. The Jam Bytecode v2.0 format is an Altera format, and is not promoted as an industry standard. However, it is not a secret -- the player source code is public, and the format specification is available under NDA. If you would like the Jam Bytecode format specification please file a Service Request with our support center through

formatting link
requesting the information. The applications engineer assigned to your service request will send you an non-disclosure agreement (NDA) that requires signature to receive the specification.

Hope this helps. Subroto Datta Altera Corp.

Reply to
Subroto Datta

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.