Newfound Electronic's Warp-13 PIC Programmer

From: Ing. Marco Tuzzi (nospam_at_here.com)
Date: 02/18/05


Date: Fri, 18 Feb 2005 11:04:24 +0100

Hi guys.
I'm having some troubles in making this programmer work.
I have an old version of this programmer, mounting a PIC16F73 with a 4MHz
quartz crystal.
I tried to upgrade the firmware to program new PICS but Bluepole 1.6 (new
firmware) works only on new boards, mounting 20MHz Crystal resonators.
I changed the crystal and programmed another 16F73 but it's not working. The
original chip with 4 MHz crystal is not working either!
I use MPLAB 6.50 and a PICSTAR Plus to program new firmware. I import the
HEX and program the chip. Is it right that after I import an HEX file in
MPLAB, if I look to Program Memory I don't see the real content that will be
programmed onto the chip? I need the .COF file to see in program memory
right? If it's not hte case, I have a problem, since HEX file and program
memory contents after import don't match!
The chip on the programmer seem correctly powered but the crystal doesn't
seem to be oscillating. What can it be? Errors in programming (as I said,
program memory and hex file contents don't match, but that could just be a
problem due to .cof file missing)? Broken hardware?
Can someone help me out?
Maybe if anyone could post od version firmware... It's called RedBack.
Thank you for any advice.
-----------------------
Eng. Marco Tuzzi



Relevant Pages

  • Newfound Electronics Warp-13 PIC Programmer
    ... I tried to upgrade the firmware to program new PICS but Bluepole 1.6 (new ... HEX and program the chip. ... if I look to Program Memory I don't see the real content that will be ... If it's not hte case, I have a problem, since HEX file and program ...
    (sci.electronics.design)
  • Newfound Electronics Warp-13 PIC Programmer
    ... I tried to upgrade the firmware to program new PICS but Bluepole 1.6 (new ... HEX and program the chip. ... if I look to Program Memory I don't see the real content that will be ... If it's not hte case, I have a problem, since HEX file and program ...
    (sci.electronics.equipment)
  • Re: Prism2 firmware upload support.
    ... > as the actual product ID for determining which hex file to load. ... > firmware so it can be merged into the hex file before we burn the new ... Yes - I've started with extracting the PDA information in a way so that it ... which is enough to drive prism2dl together with the PDA ...
    (freebsd-hackers)
  • Re: Prism2 firmware upload support.
    ... Has anyone looked at the existing symbol firmware loading code in freebsd ... upload/download of firmware (and propalby an extra SIOCGPRISM2INFO to give ... as the actual product ID for determining which hex file to load. ... to preclude it coming back up, do the firmware upload, and then call ...
    (freebsd-hackers)