Overview Features Coding ApolloOS Performance Forum Downloads Products Order Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
Please visit our Apollo-Discord Server for support.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Documentation about the Vampire hardware

Vampire II A600, Crashed While Updating 2.8 Core.

Michael Farrell

Posts 18
05 Apr 2018 21:53


My A600 has been a little strange since I had it recapped,
and it locks up sometimes.

While updating to the 2.8 core, my machine froze, and now won't power on.

So, I removed the Vampire, and the A600 boots fine.
I ordered a USB blaster (Cheap chinese one) which arrived today.

I followed the Apollo Wiki, downloaded the Altira 13.1 software, attached the Blaster, set the hardware to USB Blaster (0), loaded the .jic, and tried to flash.

The software gives the following message:

Info (209060): Started Programmer operation at Thu Apr 05 21:40:44 2018
Error (209040): Can't access JTAG chain
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Thu Apr 05 21:40:45 2018

Is my board dead??


Roy Gillotti

Posts 517
05 Apr 2018 23:26


I got that before and freaked out a bit too, but it ended up being a simple things.
 
The problem with programming, It could be one or two things. If you are using Windows, you need to run the program in Administration mode. Another issue I had with my cheap USB blaster was I needed to use a better USB cable than what it came with.

I find the socket on the V600 a bit problematic and often I need jiggle it even though it's fully bolted down to get good contact again.


Shane Stringer

Posts 22
06 Apr 2018 01:21


I got the same error.  What I had to do, was power on the Amiga *before* I started the flashing software.  Then it worked.

Actually, I got a verify error after flashing 2.7, but it seemed to work fine, and it allowed me to flash 2.8 no problem.


David Eriksson

Posts 8
06 Apr 2018 06:47


I also had some problems with the USB-Blaster that I solved by using another USB-cable. They seem to be picky.


Leigh Russ

Posts 151
06 Apr 2018 09:35


Regarding the freezing issues, I had similar after upgrading to 2.7 and turned out to be connectivity between the socket and CPU.

I also had similar issues when upgrading to Gold2 ages ago, and solved it by sanding the socket down (as mentioned in the troubleshooting in the Wiki pages). That sorted it that time, and this time I solved it by changing the socket.

More details on my findings can be found here

CLICK HERE


Michael Farrell

Posts 18
06 Apr 2018 19:17


Thanks for the replies guys!

Roy Gillotti wrote:

If you are using Windows, you need to run the program in Administration mode.

No, that made no difference.

Roy Gillotti wrote:

Another issue I had with my cheap USB blaster was I needed to use a better USB cable than what it came with.

I've tried a different cable, one that works with my external USB drive, so, it's quite short, and probably fine.
It also made no difference though!

Roy Gillotti wrote:

I find the socket on the V600 a bit problematic and often I need jiggle it even though it's fully bolted down to get good contact again.

I've removed it from the Amiga altogether, so, that's unlikely to be the problem!

Shane Stringer wrote:

I got the same error.  What I had to do, was power on the Amiga *before* I started the flashing software.  Then it worked.

OK, maybe I'll try putting it back in the A600 before my last attempt with different USB ports/cables/machines. Thanks.

Leigh Russ wrote:

Regarding the freezing issues, I had similar after upgrading to 2.7 and turned out to be connectivity between the socket and CPU.

Thanks. But the A600 crashed a few times before I actually fitted the Vampire, so, it's definitely a problem with it after it's been recapped, rather than a vampire problem!

Ok, so, I'll try all this again on a different machine, with different cables, and with it in the A600, and see what happens!

Thanks all for the replies!



Roy Gillotti

Posts 517
06 Apr 2018 19:21


Michael Farrell wrote:

  I've removed it from the Amiga altogether, so, that's unlikely to be the problem!
 

 
Well you can't flash it without the Amiga powering the vampire/FPGA. Also it's a well reported problem that the socket can cause intermittent issues. Leigh Russ literally re-soldered on a different Socket, the one used with the Furia accelerator and it improved the stability.


Michael Farrell

Posts 18
06 Apr 2018 20:14


Roy Gillotti wrote:

Well you can't flash it without the Amiga powering the vampire/FPGA

Ah HA! Excellent, thanks. That'll save me a lot of messing about.


Michael Farrell

Posts 18
06 Apr 2018 20:55


Now it's better, but worse!

Better in that it's in the A600, and can be programmed, but worse in that it still fails.

Now I get the following:
 
  Info (209060): Started Programmer operation at Fri Apr 06 20:49:21 2018
  Info (209016): Configuring device index 1
  Info (209017): Device 1 contains JTAG ID code 0x020F40DD
  Error (209040): Can't access JTAG chain
  Error (209040): Can't access JTAG chain
  Error (209015): Can't configure device. Expected JTAG ID code 0x020F40DD for device 1, but found JTAG ID code 0xFFEDFFFF.
  Error (209053): Unexpected error in JTAG server -- error code 35
  Error (209012): Operation failed
  Info (209061): Ended Programmer operation at Fri Apr 06 20:49:58 2018
 


Roy Gillotti

Posts 517
07 Apr 2018 00:25


Michael Farrell wrote:

Now it's better, but worse!
 
  Better in that it's in the A600, and can be programmed, but worse in that it still fails.
 
  Now I get the following:
 
  Info (209060): Started Programmer operation at Fri Apr 06 20:49:21 2018
  Info (209016): Configuring device index 1
  Info (209017): Device 1 contains JTAG ID code 0x020F40DD
  Error (209040): Can't access JTAG chain
  Error (209040): Can't access JTAG chain
  Error (209015): Can't configure device. Expected JTAG ID code 0x020F40DD for device 1, but found JTAG ID code 0xFFEDFFFF.
  Error (209053): Unexpected error in JTAG server -- error code 35
  Error (209012): Operation failed
  Info (209061): Ended Programmer operation at Fri Apr 06 20:49:58 2018
 

yeah this looks more in common with the issues I've seen before, sometimes just trying it again on a different USB port will make it work. Try running as administrator if you haven't done so already.


Michael Farrell

Posts 18
07 Apr 2018 10:27


Roy Gillotti wrote:

yeah this looks more in common with the issues I've seen before, sometimes just trying it again on a different USB port will make it work. Try running as administrator if you haven't done so already.

OK, so I tried a decent USB cable, with a ferrite shield attached, so I assume it's good!

And, success!

Info (209021): Performing CRC verification on device(s)
Info (209011): Successfully performed operation(s)

Fully working Vampire II again!

Thanks for all your help.


Vojin Vidanovic
(Needs Verification)
Posts 1916/ 1
07 Apr 2018 10:30


Michael Farrell wrote:

  OK, so I tried a decent USB cable, with a ferrite shield attached, so I assume it's good!
 
....

  Fully working Vampire II again!

Glad result was good, too bad it was down to the cheap USB cables!

posts 12