jamesbowman

Aha yes, that was a typo. It says "Xilinx" now. Thanks.

OK, the latest version of the shell should be able to run on Windows: https://github.com/jamesbowman/swapforth Also, if pyreadline is installed, the shell uses it ( https://pypi.python.org/pypi/pyreadline). I have been able to do some limited testing on Windows 8, and things seem to be somewhat working. James.

Hmm, yes. You should be able to connect to it using any terminal program. The speed is 921600, and you *must* make sure that the terminal drops DTR (as below) because it is the reset signal. Pressing return gives 'ok': $ miniterm.py /dev/ttyUSB1 921600--- Miniterm on /dev/papilio: 921600,8,N,1 ------ Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ------ DTR inactive --- ok ok ok ok1 2 + . 3 ok ok ok ok ok ok I have updated the built .bit file to run at 80 MHz, please can you retry with it? https://github.com/jamesbowman/swapforth/raw/master/j1b/xilinx/j1-papilioduo.bit Thanks, James.

Hmm, if it gets to "Contacting..." then the Python part is working fine. I would check the COM port that it is talking on. On Linux the DUO appears at 2 ports, because the FTDI chip is a double, so I have to pick the higher port.

J1b on DUO is alive -- and may even be usable... I started a thread in the new forum: http://forum.gadgetfactory.net/index.php?/topic/2429-j1b-on-duo-tryout/

Is anyone inclined to give the J1b no DUO a tryout? The .bit file is at: https://github.com/jamesbowman/swapforth/raw/master/j1b/xilinx/j1-papilioduo.bit If you load it, it should be possible to talk to it over the UART at 921600: There are more details in the reference manual on page 5: https://github.com/jamesbowman/swapforth/raw/master/j1b/doc/j1b-reference.pdf And to get the whole system, clone this tree and look under j1b/: https://github.com/jamesbowman/swapforth

Hi @offroad, Glad to hear it is alive... The fastest I can get the 32-bit J1b running on the DUO's XC6 is about 180 MHz. And yes, four cores should fit -- just need to think of some suitable application! J.

I have the J1 CPU running on the Papilio Duo. It runs a standard 32-bit ANS Forth, communication is through the UART. It is working quite well; in fact I used it to run my slides for a presentation last week (slides were on microSD, buttons and VGA output from the Computing Shield). Is anyone interested in giving it a tryout? Let me know if so and I will put together a release. Thanks! J.

Aha! Thanks... just for the record the command line is: papilio-prog -b $SOMEPATH/bscan_spi_lx9.bit -f xilinx/j1-papilioduo.bitWorks great.

I am happily loading .bit files into the Papilio DUO using the command-line tool "papilio-prog", like this: $ papilio-prog -v -d 'Papilio DUO' -f xilinx/j1-papilioduo.bitUsing built-in device listJTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9Created from NCD file: j1-papilioduo_par.ncd;UserID=0x09470947Target device: 6slx9tqg144Created: 2015/08/13 10:43:45Bitstream length: 2724832 bitsUploading "xilinx/j1-papilioduo.bit". DNA is 0x995bf8001a2215ffDone.Programming time 503.7 msUSB transactions: Write 176 read 8 retries 7This is working fine. But when I power-cycle the DUO, I would expect it to load the same bitstream from flash. Instead it doesn't seem to run. Is there something I am doing wrong?

Hi all, I updated the Gameduino1 libraries a couple of months ago. It now builds cleanly with Arduino IDEs from 1.0.5 to 1.6.5. There are also more games and demos included. http://www.excamera.com/sphinx/gameduino/GD/index.html The source code for the GD1 library is here - if you have a patch then a pull request would be very welcome! https://github.com/jamesbowman/gd1 James.