Searching \ for '[pic:] Wisp628/Xwisp2 and 18F2685.' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=wisp
Search entire site for: 'Wisp628/Xwisp2 and 18F2685.'.

Exact match. Not showing close matches.
PICList Thread
'[pic:] Wisp628/Xwisp2 and 18F2685.'
2006\10\06@050656 by Jan-Erik Soderholm

face picon face
Hi.
Just got a question from someone who was trying to flash a
PIC18F2685 using his Wisp628 (1.10 firmware) using XWisp2.
He gets some errors that *looks* communications error
between the Wisp628 and the target, but Iäm not sure.

Anyway,

The 2685 device is not in the list of suported devices
but the 2680 is. It seems as the diff is a larger prog mem
(64kb in the 2680 vs. 94kb in the 2685).

The 2685 shares the same Prog Spec as a lot of other
supported PIC18 devices.

Now, is there any obvious reason the 2685 would not
work with this setup ?

Jan-Erik.



2006\10\06@054814 by Rob Hamerling

face picon face
Hi Jan-Erik,

On 10/6/06, Jan-Erik Soderholm <spam_OUTjan-erik.soderholmTakeThisOuTspamtelia.com> wrote:
.
{Quote hidden}

I just added this one and three similar ones to xwisp_16.cfg. For the
2865 I have specified:

Name          = 18F2685
DataSheet     = DS39761
PgmSpec       = DS39622
Algorithm     = PIC18A
DeviceID      = 2720
ProgSize      = 96K
DataSize      = 1024
ProtectMask   = C03F
WriteBurst    = 64
FuseFixedZero = 00CF1F1F0086F5003FC03FE03F40

I couldn't test it yet, I've no such PIC here yet, but I think it
should work like any of the others of this group.
However I noticed a minor change in the programming algorithm (for the
Wisp628 firmware) for all members of this large group (38 PICs). This
might be the cause of errors for this PIC.
Note: Wisp628 firmware version 1.11 is the most recently published,
I'm working on firmware 1.12.... have some patience!

Regards, Rob

PS: Did my message about a "Users Guide and Command Reference for
Xwisp2" come through here? I didn't receive my announcement message
back from PIClist. See http://www.robh.nl/xwisp2.html or the llink
within http://www.robh.nl/picsoft.php#xwisp2.



--
Rob Hamerling, Vianen NL (http://www.robh.nl/)

2006\10\06@060438 by Alan B. Pearce

face picon face
>PS: Did my message about a "Users Guide and Command Reference for
>Xwisp2" come through here? I didn't receive my announcement message
>back from PIClist. See http://www.robh.nl/xwisp2.html or the llink
>within http://www.robh.nl/picsoft.php#xwisp2.

I received a message through the PICList about "XWisp2 documentation" with a
PIC tag on Wednesday 4th at 14:11 BST, posted 14:00 BST.


2006\10\06@061506 by Rob Hamerling

face picon face
On 10/6/06, Alan B. Pearce <.....A.B.PearceKILLspamspam@spam@rl.ac.uk> wrote:
> >PS: Did my message about a "Users Guide and Command Reference for Xwisp2" come through here?
>
> I received a message through the PICList about "XWisp2 documentation" with a
> PIC tag on Wednesday 4th at 14:11 BST, posted 14:00 BST.

Thanks Alan, that's the message I meant and missed.


--
Rob Hamerling, Vianen NL (http://www.robh.nl/)

2006\10\06@070307 by Jan-Erik Soderholm

face picon face
OK.
I had another Wisp628 user who had a similiar problem
with a 18F4420 and in that case a firmware upgrade from
1.10 to 1.11 solved it. It that case everything programmed OK,
but the verify failed but the device still worked as expected.

The currect Wisp628 user is currently upgrading (or so he
said at least...).

B.t.w., I also saw the note about the docs... :-)

Jan-Erik.



More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...