gnupic: epic plus programmer troubles
Subject:
epic plus programmer troubles
From:
Bill Sack ####@####.####
Date:
27 May 2004 17:48:02 +0100
Message-Id: <40B61B46.3070008@acsu.buffalo.edu>
hi gnupicers,
i've been lurking on this list for a few months and have about decided
that it's time to hear from an absolute beginner who knows nothing and
hasn't the slightest clue ... me!
i'm a musician who's built a couple of projects using commercial servo
controllers, and i want to begin making smaller standalone autonomous
musical machines controlled by microcontrollers. i was really happy to
see the gputils and have been playing with them for a little while - not
programming any pics yet, just assembling and simming.
so i bought an epic plus because it seemed like it was supported by a
few gnupic programmers (ie: odyssey and pikdev). i've had no success in
linux getting it to do anything thus far, aside from blinking the status
led on and off. i don't think it's broken, as it does program pics when
using epic's software in win nt (but how much fun is it to have to boot
nt every time you wanna program a pic? not much fun).
odyssey says this when i try to program:
[bsack@blini projx]$ odyssey PIC16F84 write blinkc.HEX
Address: 0x000000, 0% done
odyssey: PIC16F84: Couldn't write program memory at address 0x0000
reading from a pic produces garbage output:
[bsack@blini projx]$ odyssey PIC16F84 read garbage.hex
Address: 0x002007, 100% done
[bsack@blini projx]$ gpdasm -pp16f84 garbage.hex
000000: 001f dw 0x1f ;unknown opcode
000001: 0000 nop
000002: 0000 nop
.....
i'm thinking this isn't an odyssey problem though, since i get similar
non-results using pikdev. pikdev's warning messages on write are:
Warning: [Prog memory] (addr = 0x0, device = 0x3fff, buffer = 0x3000)
Warning: [Prog memory] (addr = 0x1, device = 0x3fff, buffer = 0x8a)
Warning: [Prog memory] (addr = 0x2, device = 0x3fff, buffer = 0x2819)
Warning: [Prog memory] (addr = 0x4, device = 0x3fff, buffer = 0x3019)
etc. ad astra (i don't know what these warnings mean ...)
in either case (pikdev or odyssey), if the pic in the programmer has a
working program on it, it will still be there even after "erase" or
"write" operations.
the .hex files i've tried have been generated by various assemblers,
including gpasm and ccs pcml (yes, i actually bought it. pathetic, i
know, but i figure it'd probably take me ten years to learn enough
assembler to do what it'll take me 24 hours to do in c.) and, as i say,
they all work when programmed by epic's programmer.
can anyone help, or point me in the right direction? i've pretty much
run out of things to try. if i have not sent enough information, please
say so, i really just don't know ...
thanks,
bill
--
_________
Bill Sack
wsack(a)acsu.buffalo.edu
----------------------
