Searching \ for '[PIC]:Newbie's first attempt' 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/begin.htm?key=pic
Search entire site for: 'Newbie's first attempt'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]:Newbie's first attempt'
2002\08\25@200011 by Scott Pierce

flavicon
face
Hi all,

I finally got my PIC programmer (El Cheapo) working so I thought I would
try my hand at a simple program.  I wrote a program to count from 0 to 255
and display the contents of the count register on portb.  I have a 10 LED
dip package connected to portb, two of the LEDs are not connected.  The
pause routine I put in is simply to allow me some time to view the contents
of portb.  I realize that the tris command is obsolete and not recommended
but I'm learning from a couple different books (Myke Predko's, and Easy
Pic'n) and using the tris command seemed to be the easiest solution for my
first program.  In MPLAB I set up the PIC using XT for the resonator, 4Mhz
for the speed, WDT disabled.  The program compiles and burn into memory
just fine but when I plug the chip into the circuit, nothing seems to
happen.  I am 99% sure I set up the circuit properly as I have checked and
re-checked all the connections at least 10 times.  I also stepped through
the program listed below in MPLAB and it seemed to execute properly.  Using
watch windows in MPLAB everything checked out.  As for the circuit, I
started out using a 330 Ohm dip package in series with the anode pins of
the LED dip package.  Next I tried tying the cathode pins of the LED
package to portb and the anode pins of the LEDs to 330 Ohm resistors.  No
LEDs turned on in either configurations.  Any help is greatly appreciated.

Sincerely,
Scott Pierce



;== Scott Pierce ================================================ 8/24/2002 ===
;
; Counts from 0 to 255 and displays contents on portb
;
;
;==============================================================================
;
       list    p=16f84a
       radix   hex
;
;==============================================================================
;
portb   equ     0x06
count   equ     0x0c
counti  equ     0x0d
countj  equ     0x0e
;
;==============================================================================
;
       org     0x00
;
;==============================================================================
;
start   movlw   0x00
       tris    portb   ;set portb to all outputs
       movlw   0xff    ;set portb high
       movwf   portb   ;set portb to all 0's
       clrf    counti  ;set counti to 0
       clrf    countj  ;set countj to 0
       clrf    count   ;set count  to 0
;
;==============================================================================
;
dispcnt movf    count,w ;move contents of count into work register
       movwf   portb   ;output contents of count to portb
       call    pause
       incf    count,f ;increment count by one, results stored in file reg
       goto    dispcnt ;start loop over again
;
;==============================================================================
;
pause   movlw   0x0f    ;set counter to 254
       movwf   counti  ;move work register to counti file register
loadj   movlw   0x0f    ;set countj to 255
       movwf   countj  ;move work register to countj file register
decj    decfsz  countj,f;decrement countj, if zero skip next instruction
       goto    decj    ;loop decj again until countj = 0
       decfsz  counti,f;decrement counti, if zero skip next instruction
       goto    loadj   ;loop loadj again until counti = 0
       return          ;when nested loops are done, return to dispcnt loop
;
;==============================================================================
;
       end
;
;==============================================================================

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@202124 by Tony Nixon

flavicon
picon face
Scott Pierce wrote:

Don't forget PORTA works even though you are not using it. The inputs
will float if left as unconnected inputs, so set them as outputs to keep
the chip happy.

> start   movlw   0x00
         tris    porta   ;<<<<< ADDED
{Quote hidden}

The counter values were not as you say in your comments. You also had
the delay kept in a permanent loop. The code changes appear below.


> pause   movlw   0x0f    ;set counter to 254

        movlw 0xFE      ;set counter to 254

>         movwf   counti  ;move work register to counti file register
> loadj   movlw   0x0f    ;set countj to 255
        movlw 0xFF      ;set countj to 255

>         movwf   countj  ;move work register to countj file register
> decj    decfsz  countj,f;decrement countj, if zero skip next instruction
>         goto    decj    ;loop decj again until countj = 0
>         decfsz  counti,f;decrement counti, if zero skip next instruction

        goto    decj   ;loop loadj again until counti = 0
>         goto    loadj   ;loop loadj again until counti = 0
>         return          ;when nested loops are done, return to dispcnt loop


--
Best regards

Tony

mICros
http://www.bubblesoftonline.com
spam_OUTsalesTakeThisOuTspambubblesoftonline.com

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@204119 by Sean Alcorn (SYD)

flavicon
face
Scott,

I am pretty much a newbie myself and not offended by the term either. I
was just about to reply when I saw Tony's reply come through.

I don't know about you, but I find HEX simply confusing. Most
unnatural! :-)

Instead of;

> start   movlw   0x00

have you considered;

start   movlw   b'00000000'
tris   porta
tris   portb

Also, Tony missed this one (- I think)

>         movlw   0xff    ;set portb high
>         movwf   portb   ;set portb to all 0's

Your comment says you are setting portb all low, but isn't the hex that
you've moved to W in the previous line 255? It makes no difference in
your program, but the point is that it *could* :-(

Just a suggestion, but I find binary easier to work in. When you need
to manipulate one pin, you simply count from the right of your byte and
that's the digit you change.

Cheers,

Sean

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@210024 by Scott Pierce

flavicon
face
Thanks for the advice Tony.  I tried what you suggested still with no luck
though.  I set porta to all outputs and changed the goto statement.  I
originally had the values for the counters set at 0xff (255) but changed
them so I could step through the program in MPLAB without having to press
the step button 512 times.  I know the polarity on the LEDs are correct as
I just checked them by connecting a 330 Ohm resistor to one of them and it
lit up.  I even tried a much more simple program where I moved 0xff into
the work register then moved that value into portb, then looped
infinitely  with:
loopme  goto loopme

That program didn't work either.  Is it possible I might have burned up
portb somehow?  I assume the PIC would still allow itself to be programmed
even if a port was burned up, would it not?  Thanks again.

Sincerely,
Scott Pierce



At 10:18 AM 8/26/2002 +1000, you wrote:
{Quote hidden}

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@210643 by Scott Pierce

flavicon
face
Sean,

I am fairly comfortable with hex and I guess the only reason I'm using hex
is because it's less typing :)

I have changed the code many times since last night trying to get it to
work.  One of my trials was changing portb to 0xff (b'11111111') to
initially show that portb was actually working.  Granted it would have only
been a slight flash and probably not even long enough to see the port go
from low to high.  In changing my code I forgot to change a lot of my
comments and I apologize if it is confusing.

Thanks for the suggestions!

Sincerely,
Scott Pierce

At 10:39 AM 8/26/2002 +1000, you wrote:
{Quote hidden}

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@211516 by Tony Nixon

flavicon
picon face
Hi Scott,

Does the programmer verify what was programmed into the chip?

What clock source are you using for the PIC, RC, crystal, resonator ??

Is the OSC FUSE set accordingly?

For example, if you have a 4MHz crystal with 2 18p caps, then use HS
mode.

Is MCLR tied to 5V?

Is the WDT disabled?

In the PIC circuit, are there series resistors with each LED and IO pin?

Best regards

Tony


Scott Pierce wrote:
{Quote hidden}

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\25@215620 by Pic Dude

flavicon
face
Scott,

First, slap yourself on the wrist for use of 'tris'.  I'll let
it slide this time. :-)  I copied your code into MPLAB and
simulated it successfully.  So that's okay.  The problem must
be with the circuit.  Can you email that or ascii-draw it here?

Few things I can think of:
- Some programmers will not give you feedback if the programming
 fails.  Test this by building one of the LED flashers from
 the piclist site, etc.  IE: something *known* to work.
- Is MCLR connected to +ve?
- You're resetting your delays with '0F' which is 16.  With 2
  counters, you have a delay of 256 loop cycles.  At 4Mhz, each
  instruction is 1 micro-second, so that's not much of a
  delay.  Change those to 'FF' or so for now.

Either way, even though you say that the circuit is correct,
there may be something that a fresh and more experienced pair
of eyes may pick up.

Cheers,
-Neil.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2002\08\26@002229 by Kevin Moll

picon face
Disclaimer: Other newbie trying to answer a question.

I think you need to enable the pull-up resistors for portb.  IIRC, the
internal pull-ups are disabled when you change PORTB to output.  Because you
have the LED bar tied to ground and the PIC can't source any current when
the output is high (if the pull-ups are disabled), the LED's will never
light up.  A simple test would be to turn the LED bar around and tie it to
VCC instead of GND.  You'll get the complement of what you're expecting.
Otherwise, you can add external pull up resistorts or set an OPTION bit (I
don't remember which) to enable the internal pullups.

Kevin

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\26@025658 by Wouter van Ooijen

face picon face
Sorry I did not even look at your code, but it might be advisable to
take one step back at verify that both your programmer and you target
hardware are operating properly. My page at http://www.voti.nl/wisp628
has blink-a-led .hex files and circuit diagrams for most flash pics, try
the appropriate one, then (when it works) start worrying again about
your own program (or maybe switch to Jal?).

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\26@055652 by Bob Barr

flavicon
face
On Mon, 26 Aug 2002 00:22:02 -0400, Kevin Moll wrote:

>Disclaimer: Other newbie trying to answer a question.
>
>I think you need to enable the pull-up resistors for portb.  IIRC, the
>internal pull-ups are disabled when you change PORTB to output.  Because you
>have the LED bar tied to ground and the PIC can't source any current when
>the output is high (if the pull-ups are disabled), the LED's will never
>light up.  A simple test would be to turn the LED bar around and tie it to
>VCC instead of GND.  You'll get the complement of what you're expecting.
>Otherwise, you can add external pull up resistorts or set an OPTION bit (I
>don't remember which) to enable the internal pullups.
>

The port B internal pullups have no effect whatsoever on a port pin
that is set for output.
They are only connected to pins that are defined as inputs in the
TRISB register. And if they're turned on, of course. :=)

Regards, Bob

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\26@100652 by Pic Dude

flavicon
face
At first glance, it would seem to be okay, except that
the 10k resistor on MCLR may not be holding it high enough.
Try a 1K or directly connecting MCLR to +ve.  That's just
a guess though.

If not, the resonator may be a problem.  Seems that many
have had problems with non-Murata resonators, so perhaps
you could try an RC oscillator for now.  Remember to change
the config switches.

Even though you set the config switches in the code, you
may be able to override it with the command-line options
during programming.  Perhaps you have some of this causing
a problem?

Check the resistor array.  Perhaps you've got a DIP with
a single common, rather than 8 individual resistors?  I
mention this since a local store has done that to me on
a couple occassions -- given me the wrong one.

Cheers,
-Neil.



> {Original Message removed}

2002\08\26@102139 by Pic Dude

flavicon
face
Kevin Moll scribbled:
> I think you need to enable the pull-up resistors for portb.  IIRC, the
> internal pull-ups are disabled when you change PORTB to output.

Didn't you just contradict yourself here?

Pull-ups should have no effect for pins set as outputs, and no
external pull-ups should be necessary for lighting LED's.

Cheers,
-Neil.



> {Original Message removed}

2002\08\26@160407 by Olin Lathrop

face picon face
> ... and the PIC can't source any current when
> the output is high (if the pull-ups are disabled),

Yes, it can.  Port B has full totem pole drivers.  The pullups are disabled
for output pins because they don't make any sense then.  The pullups can be
useful when the pin is an input, because inputs are high impedence.  This
allows, for example, a switch to be sensed by the PIC by connecting it
between a port B input pin and ground.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\26@222744 by Charles Rogers

flavicon
face
----- Original Message -----
From: "Scott Pierce" <piclistspamKILLspamCALCLINKS.NET>
To: <.....PICLISTKILLspamspam.....MITVMA.MIT.EDU>
Sent: Sunday, August 25, 2002 7:54 PM
Subject: [PIC]:Newbie's first attempt


> Hi all,
>
> I finally got my PIC programmer (El Cheapo) working so I thought I would

Scott:

You may think your El Cheapo is working, maby it is, maby it's not!!!  I
built and re-built an
El Cheapo,  it passes "ALL" the specified tests in the build/test section,
programms and verifies
just like Myke says it should but the simple fact is "It just don't work".
You should verify it with
a working programmer to make sure.  This newbie has been through every thing
you describe,
so think about the El Cheapo!!!   I sent Myke eight (8) different e-mails
concerning the
El Cheapo and have yet to receive my first reply!  I built somebody's KIT81,
a P16Pro and
invested in a PS+ and all work very well, just like to tinker I guess.

Charlie R.



> try my hand at a simple program.  I wrote a program to count from 0 to 255
> and display the contents of the count register on portb.  I have a 10 LED
> dip package connected to portb, two of the LEDs are not connected.  The
> pause routine I put in is simply to allow me some time to view the
contents
> of portb.  I realize that the tris command is obsolete and not recommended
> but I'm learning from a couple different books (Myke Predko's, and Easy
> Pic'n) and using the tris command seemed to be the easiest solution for my
> first program.  In MPLAB I set up the PIC using XT for the resonator, 4Mhz
> for the speed, WDT disabled.  The program compiles and burn into memory
> just fine but when I plug the chip into the circuit, nothing seems to
> happen.  I am 99% sure I set up the circuit properly as I have checked and
> re-checked all the connections at least 10 times.  I also stepped through
> the program listed below in MPLAB and it seemed to execute properly.
Using
{Quote hidden}

8/24/2002 ===
> ;
> ; Counts from 0 to 255 and displays contents on portb
> ;
> ;
>
;===========================================================================
===
> ;
>         list    p=16f84a
>         radix   hex
> ;
>
;===========================================================================
===
> ;
> portb   equ     0x06
> count   equ     0x0c
> counti  equ     0x0d
> countj  equ     0x0e
> ;
>
;===========================================================================
===
> ;
>         org     0x00
> ;
>
;===========================================================================
===
> ;
> start   movlw   0x00
>         tris    portb   ;set portb to all outputs
>         movlw   0xff    ;set portb high
>         movwf   portb   ;set portb to all 0's
>         clrf    counti  ;set counti to 0
>         clrf    countj  ;set countj to 0
>         clrf    count   ;set count  to 0
> ;
>
;===========================================================================
===
> ;
> dispcnt movf    count,w ;move contents of count into work register
>         movwf   portb   ;output contents of count to portb
>         call    pause
>         incf    count,f ;increment count by one, results stored in file
reg
>         goto    dispcnt ;start loop over again
> ;
>
;===========================================================================
===
> ;
> pause   movlw   0x0f    ;set counter to 254
>         movwf   counti  ;move work register to counti file register
> loadj   movlw   0x0f    ;set countj to 255
>         movwf   countj  ;move work register to countj file register
> decj    decfsz  countj,f;decrement countj, if zero skip next instruction
>         goto    decj    ;loop decj again until countj = 0
>         decfsz  counti,f;decrement counti, if zero skip next instruction
>         goto    loadj   ;loop loadj again until counti = 0
>         return          ;when nested loops are done, return to dispcnt
loop
> ;
>
;===========================================================================
===
> ;
>         end
> ;
>
;===========================================================================
===
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
>
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\26@233645 by Kevin Moll

picon face
> > ... and the PIC can't source any current when
> > the output is high (if the pull-ups are disabled),
>
> Yes, it can.  Port B has full totem pole drivers.  The pullups are
disabled
> for output pins because they don't make any sense then.  The pullups can
be
> useful when the pin is an input, because inputs are high impedence.  This
> allows, for example, a switch to be sensed by the PIC by connecting it
> between a port B input pin and ground.
>

Thanks for pointing that out.  I miscounted all the NOT symbols floating
around on the logic diagram of the PORTB pins in the datasheet, and I've
been under the impression that the reason for the pull-ups was to change
PORTB output between open-collector and push-pull.  By the datasheet saying
that the pullups were disabled when PORTB was changed to output, I thought
it meant that it defaulted back to open-collector.  Luckily none of my
projects so far have relied on the pullups :)

Kevin

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2002\08\27@023059 by Nate Duehr

face
flavicon
face
Another newbie disappointment story with the El Cheapo:

Last week, I spent the majority of my free time fiddling with an El
Cheapo after purchasing Myke's very good book.  (I have no complaints
with the book.  The diagrams in many cases are exact duplicates of the
PIC datasheets, but newbies usually don't download datasheets to look
at, and the PIC is a relatively simple architecture, so there's not much
else Myke could do there... and having the textual description to
UNDERSTAND those diagrams is worth a million...)

My background: Simple electronics, lots of RF stuff, and LOTS of
computer programming and system administration experience.  I remember
soldering 16K of extra RAM into my first "PC" (it wasn't an IBM, that's
for sure!) years ago... so no newbie to a soldering iron or scared of
messing with components.

I decided (like many newbies, I assume) that I wanted to delve deeper
into uController hardware and since I have two friends, one who's a PIC
guy, the other who swears by Atmel's, I realized that NOW -- while I
know them, we all talk regularly and all that -- is a great time for me
to do dumb things and ask questions with both micro's.

I'm not afraid to "let the smoke out" of some components to learn
something... and have done it before.  Might as well give those guys a
laugh or two when I call with dumb questions about "why did it blow up
when I did X?"  (GRIN)

My El Cheapo, when completed, (checked over carefully by myself and a
friend who's been designing PIC controller applications for about five
years now, some hobby, some professional contract stuff) is extremely
input voltage sensitive.

The tests in the older version of the software on the CD regularly
report that the delay line either "didn't return a HI voltage value" or
"didn't return a LOW voltage value" correctly.

The only clue from that version of the software is to "check the
polarity of XYZ"... yep, been checked.  It's correct.  Verified by a
third-party looking at my board.  Grabbed a VOM and went through the
circuit.  Reheated anything that even so much as LOOKED like the solder
wasn't "just right"...

The error always follows the amount of voltage provided the programmer,
which doesn't make a lot of sense to me, but I'm no designer... if I
input too low a voltage the test software screams that the voltage
returned from programmer's delay line isn't high enough, if a higher
voltage is provided it screams that the low voltage swing isn't
present.

Looking at it with a VOM, it's swinging alright... or at least it seems
to be swinging according to the little help screens in the older
software to the level ranges indicated.

Of course, one major hurdle here is that in the older software, the
board layout's the same, but there are typos in the software.  It keeps
referring to part numbers that simply don't exist on the newer board.  I
can't think of the reference right now, but the circle around the
component and the component silkscreened name in the picture on the
software don't match the component name on the board, but the locations
match and the layout looks the same.  Sigh... couldn't the CD with the
book actually match the board in the front cover?

We tried it on three different PC's and a total of four parallel ports.
One parallel port was even an ISA add-on card, "dedicated to the
programmer" as some of Myke's instructions I've seen have seemed to
recommend.  That seemed to help some but not much.

The original cable was a 10-foot-long one, and reading some other posts
we saw that might be a problem (gee, all my other parallel devices do
fine at 10'... surprise surprise!) so we found a 3-footer.  We also
pin-checked the entire cable as requested by the site.  All a waste of
time.

Our other disappointment is that NEITHER I nor the other person who was
looking over my shoulder (we both work in computers and networking for a
living and I have for over 10 years now) could get the latest version of
the software to install properly after downloading it from the website.

All instructions were followed, the requirements for Admin priveledges
on the one Win2K machine of the bunch (there were three machines tried)
were done, the VB Runtimes and all that rot... the new software on ALL
THREE  2machines complains after installation about "path not found".

This is just unacceptable software packaging, in my opinion... (But hey,
what do I know about software products, I remember soldering RAM into
early PC's and all and know a myriad of OS's long since dead and most of
the "latest-and-greatest" ones...)

The Win2K box complains (as the docs mention) about some system software
being out of date, and even after following the step-by-step
instructions for dealing with this issue on Myke's site... it
consistently does this every time.  Various other "hey I've got an idea"
moments and trials occurred over the course of many hours also... just
to get a VB app to load?!  No wonder I'm a Linux bigot!  (GRIN)  Man I
was mad.  (Rarely do my computers "beat" me at their games... BIG GRIN.
I even considered finding a bootleg copy of the VB development
environment to install before Myke's software to try to get the VB
crap-ola straightened out, but decided that this silly little programmer
wasn't worth that much effort.)

So I put together a Tait programmer on an experimenter breadboard and it
works.  It's crappy and built on a breadboard with leads running over to
the PC, etc... looks like hell.  But it works.

Had other difficulties finding a machine to put DOS/Windows on out here
in the garage... (I really gotta try the Unix tools... I got plenty of
Linux boxes around, and would happily even load a BSD or two to try...
heh heh.) ... but that's just me.  I'm typing this on an iMac running
Debian Linux, from the garage on the wireless ethernet... (GRIN).

However, my experience with Myke's El Cheapo was REALLY bad.  Not so
much that I wouldn't recommend the book, but it wasted a HUGE amount of
my time unnecessarily, made me angry, and in general... wasn't what I
got into this for... a bit of fun.

Get an F84 and make up a Tait programmer if you want to go
super-duper-cheap... really.  If Myke's board doesn't work first or
second try, chuck it on the workbench (or in the trash, but we're all
good little pack-rats here, right?) put on your thinking cap and build
something else... or order a "commercial" programmer from one of the
fine folks here on this list.

I really am disappointed.  Maybe more at my inability to fix this silly
thing than at Myke.  Especially after spending a week probing around in
the FAQ's, archives, and other places... and finding a MYRIAD of good
ways to program these little beasties.

The El Cheapo is living up to its name, thus far.

Basically if you're a newbie reading the list, I'm not trying to be down
on Myke's book.  The book's good.  Very good.  Buy the book.  GOOD
STUFF(TM).

But don't get too excited when you see a PCB in the front cover.  It's
not a very good programmer *in my newbie opinion* and if you're like me,
you'll be all excited about seeing that PCB... "Hey!  That's going to
save me some time/effort/money/whatever"... take your pick.  It didn't
work out that way for me.  It might for you.

Hearing that Myke is non-responsive to another poster's e-mails was a
surprise this evening when reading posts here.  That is *NOT* the spirit
I've seen here on the list so far.  Admitedly, I haven't tried to
contact Myke.  I figured (especially with another programmer working)
that it wasn't worth bothering him.  But after reading the other
poster's frustrated comments, I thought I'd say something as a newbie.

In three months, I may look back on this e-mail and laugh, knowing that
I found something wrong with my El Cheapo that was 100% my fault (highly
likely, but how can I tell?  There's no reasonable troubleshooting doc
for it, and I can't get the latest software even loaded past the crappy
interdependencies and DLL hell of the MicroSloth Operating System, and
I'm clueless... I will ADMIT it freely.)

I didn't bother even trying to contact Myke, as I figured with thousands
of books out there and probably thousands of people with "strange"
problems with the software and hardware... why bother... just buy or
build something that works... don't bother Myke.  The book is worth $45
by itself.

There's plenty of designs for free programmers.  The $20 I spent locally
on components was high (our local shop gets a huge premium for having
things "in-stock" and if I'd have gone mail-order with shipping it would
have been $12 US, but I'm a typical impatient newbie!), and I'd prefer
to have put that $20 towards an EPIC or more likely, a Warp-13
programmer now... but blowing a few bucks in the learning process is
definitely expected...

How many PIC's and other components will I blow up learning?  Probably
more than that $20 worth of parts, eventually... and I can always pull
that stuff off that board and use it for other things...

But I *did* waste at least three days or four futzing around with the El
Cheapo, and that will give me pause whenever I see a PCB in the front
cover of a book at the bookstore ever again.

I'd have gladly paid $10-$30 US more for the book and more parts for the
El Cheapo if it had "just worked"...

I've spent much more money on much smaller and less useful computer
books, that's for sure.  (Hell, I'm part of a team of people that
survey's bookstores for O'Reilly and Associates and gets free books from
them just because I couldn't afford my computer book habit and a couple
hours in a bookstore a month for a free book is a god-send for a
computer bookworm like me!)

The $45 (roughly, online outlets were lower -- again, that newbie
impatience!  HEY... the local Borders has a copy!  And with shipping...
heck, it's only costing me $5 more to get it from the bookstore TODAY!
GRIN...) price tag on the book and the PCB included were a big sales
draw to me, and of course, now I know better... Caveat Emptor.

Nate

(Eagerly reading and absorbing all this wonderful "PIC Stuff".
Imagine!  A "computer" as powerful -- well, less RAM, and er, um... a
slightly less "user friendly" interface to the outside world... heh heh
-- as my first PC on a 16 pin CHIP!  WHOOO HOOO!  Gonna have some *FUN*
now!)


On Mon, 2002-08-26 at 20:16, Charles Rogers wrote:
> {Original Message removed}

2002\08\27@100313 by myke predko

flavicon
face
Hi Nate,

I'm sorry you've had this tale of woe with the El Cheapo - I'm glad that you
did find the book useful.

Could you please contact me off line?  I would like to understand exactly
what you were seeing with the El Cheapo in terms of voltages and actual
problems.

myke
{Original Message removed}

2002\08\27@161001 by Nate Duehr

face
flavicon
face
Will do Myke.  Sorry if I seemed at all overly negative in any way.  The
book's great and I truly have no idea what's going on with the newer
software loads on any of the machines that won't load it properly.

I have a consulting client that needs assistance with a Unix machine
that is having er... um... security issues today, and two other clients
that need website updates and all that fun stuff.

I'm sure you're super-busy too, so I didn't bother you with it... I've
certainly had my fair share of "solutions" that didn't quite work out
correctly for my customers before... so no worries!

Give me a couple of days and I'll send you more details after going back
through the test suite with the VOM and making notes.  Watch... I'll get
lucky and you'll see something in the test results that's a "smoking
gun" pointing right at something dumb I did.  (GRIN)

Meanwhile, this sudden flurry of activity from customers will mean
there's some "play money" to put toward PIC stuff!  (GRIN)

Nate

On Tue, 2002-08-27 at 08:01, myke predko wrote:
> Hi Nate,
>
> I'm sorry you've had this tale of woe with the El Cheapo - I'm glad that you
> did find the book useful.
>
> Could you please contact me off line?  I would like to understand exactly
> what you were seeing with the El Cheapo in terms of voltages and actual
> problems.
>
> myke
> {Original Message removed}

2002\08\28@044821 by Rob Hamerling

flavicon
face
Nate Duehr wrote:
> Will do Myke.  Sorry if I seemed at all overly negative in any way.  The
> book's great ....

For those who are now tempted to buy Myke's book "Programming and
Customizing PICmicro Microcontrollers" I want to share an
experience. I ordered it in March 2002 at Amazon. I got a book
with hunderds(!) of errors.  I reported this to Myke, who informed
me that I must have received an old print. When I informed Amazon
I got it refunded. Nevertheless these errors costed me a lot of
time.... So beware you get a recent print (how??).
Regards, Rob.

--
Rob Hamerling, Vianen, NL phone +31-347-322822
homepage: http://www.robh.nl/

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email EraseMElistservspam_OUTspamTakeThisOuTmitvma.mit.edu with SET PICList DIGEST in the body


2002\08\28@090710 by Alan B. Pearce

face picon face
>I don't know about you, but I find HEX simply confusing.
>Most unnatural! :-)

So just wait until you have been working in HEX all day, and then try and
add up the cheque book in HEX :))))

Don't ask how I know how this feels :)

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listservspamspam_OUTmitvma.mit.edu with SET PICList DIGEST in the body


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