• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikesmith

  • Rank

Profile Information

  • Gender
    Not Telling
  1. mikesmith

    A few OS X problems

    Jack, thanks for the offer. The closest I have to a Windows machine is a VM; the bitfile does appear to load and verify correctly. I am more inclined to view this as a fine opportunity to upgrade to the new Papilio, as at least one of my ZPU tinkering plans will require a lot more RAM than the '500 board has.
  2. mikesmith

    A few OS X problems

    Jack, thanks; I should have noted what I'd tried in more detail - I am indeed looking at the second serial port and at the bitrate set in the sketch setup function. Regardless of the port I'm looking at though, I'd expect to be seeing the serial LED blinking since the sketch looks like it should be transmitting regularly. If there's nothing known to be problematic with the v2.04 (typo above, sorry) boards, then is there anything else I can try to establish confidence in the board (or to confirm that it's died)?
  3. mikesmith

    A few OS X problems

    I tried running through the quickstart on Windows as well, but I have the same issue (timing out waiting for the bootloader) The AVR8 example also fails. If I tell it to write to flash, the program and verify phases all pass, but I don't get any serial output from the QuickStart example. Every now and then there's a burst of activity on the RX LED, but neither the Serial Monitor nor Teraterm can make anything of it. This is all on a v2.05 Papilio One/500K, if that makes any difference...
  4. mikesmith

    A few OS X problems

    Thanks for the heads-up on the AVR8; I guess the only path forward there would be with a bootloader similar to the ZPU. It might be interesting to someone else, but for me I was only interested in getting *something* to work to validate that I had a working board and bootloader. Feel free to ping me if you want me to try something...
  5. mikesmith

    A few OS X problems

    I dusted off my One/500K board today to see where things were up to, and got a bit hopeful about the ZAP IDE; I've wanted for a long time now to play with the ZPU, but it's just never worked out. There are still a few problems - since issues are disabled on the github page this seems like the only place to make a list. When attempting to build and upload using the AVR8 core, compilation fails because the IDE attempts to run "cp. exe".When attempting to run the flash-the-bootloader pass for the ZPU core, flashing fails because this line in platform.txt:tools.papilioprog.erase.pattern="{path}/bin/papilio-prog.exe" -cIn general there aren't any OS X binaries in hardware/zpuino to substitute here.The Papilio QuickStart example uses what seems to be an outdated call to Serial.print: Serial.print(thisByte, BYTE);which seems like it needs to be Serial.write(thisByte); After flashing zpuino-1.0-PapilioOne-S3E500-Vanilla-1.0.bit using the OS X Papilio Loader GUI (had to temporarily unload the FTDI kext as discussed elsewhere), attempting to build and upload the patched QuickStart example ultimately fails with: Cannot get programmer version, abortingI tried invoking the uploader manually, including at 115200 baud, with no luck either: ./build/macosx/work/Arduino.app/Contents/Resources/Java/hardware/tools/zpu/bin/zpuinoprogrammer -s 115200 -R -d /dev/cu.usbserial-00001214B -b /var/folders/v1/5v5zh56164x0ltx6gpbhyldm0000gn/T/build5681735252102643770.tmp/Papilio_QuickStart.cpp.bin -vvvvvvvvvvOpened device '/dev/cu.usbserial-00001214B'Connecting...[1391668753.446547] Tx: 0x7e 0x01 0x1e 0x0e 0x7e[1391668753.647616] Tx: 0x7e 0x01 0x1e 0x0e 0x7e[1391668753.848701] Tx: 0x7e 0x01 0x1e 0x0e 0x7eI built a fresh copy of the programmer from the HDL repo as discussed elsewhere here, with the same results (so I'm wondering how I can tell whether the ZPU is even alive in my FPGA?).