ebattaglia42

Members
  • Content Count

    7
  • Joined

  • Last visited

About ebattaglia42

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @attila As an update, I was playing around with it again today and somehow burnt out the attiny85 and the atmega328p. They were powered at 3.3V, were somewhat readable, and then suddenly stopped entering programming mode. I was unable to recover them with other ISPs. Do you know why they could have burnt out? In both cases, an unsuccessful write was performed first. I did not touch the fuses, at least intentionally.
  2. Hi @attila, Thanks for the response. I think its a great addition. I'm currently powering the attiny85 with 3.3v, so the logic should work out. I actually get less reliability at lower clock rates. It only enters programming mode above 500kHz, and even then only works 10% of the time. At 2MHz it enters around 90% of the time, but verifications still fail. I'm pretty sure the chips are good, because they verify fine on other programmers at 3.3V.
  3. Hi, I've been experimenting with the AVR protocol in waveforms on the electronics explorer, and I've been getting some weird results. For most speeds the board is not identified correctly, and for the speeds that do work, verification always fails after writing flash. The connection is sometimes stable enough to read/write fuses. I've tested with a few boards (2 attiny85, 2 atmega328p). All of them program fine with other ISP options. I imagine I'm just doing something wrong, so could anyone point me in the direction of some resources? My simplest test case is just an ATtiny85 connec
  4. Thanks for the response @JColvin. I can see how the jumpers could be considered an improvement. The swappable design is definitely awesome, but so many of my designs are dependent upon semi permanent connections to the boards inputs, so its just so much sexier to have them all be small pre-cut jumpers. I didn't know that the jumpers were color-coded - that's helpful. Did I also miss a way to access the oscilloscope inputs via jumpers? Cause that was one of the only other big cons the board had for me, for the same reasons.
  5. I use the electronics explorer daily, and I'm always finding new features and abilities. It's a tool that I absolutely adore, and couldn't imagine prototyping without it anymore. Unfortunately, I know these devices have a lifespan as I've seen and used older boards with barely useable breadboards. Given that these devices are no longer being manufactured, is there any way that I could replace the two large breadboards on top to extend its lifespan? Will the glue release with enough heat? I should mention that I know the analog explorer exists, but I massively prefer the ability to p
  6. Thank you so much. The eeprom rewrite program fixed the board.
  7. Hi, My Digilent Electronics Explorer has worked fine for several months. Today it was not being recognized by my computer (Unknown Device) so I followed the instructions in this forum to reinstall the driver, but when I tried installing the Digilent USB Device or Digilent Onboard USB drivers, I ran into problems. The board is still not recognized by waveforms, and waveforms becomes incredibly slow whenever the board is connected. Deleting the driver fixes waveforms, but doesn't help recognize the board. I desperately need this board to work for several important projects happening right n