Sorry to break the rules. Here's the correct tag. > -----Original Message----- > From: pic microcontroller discussion list [mailto:PICLIST@MITVMA.MIT.EDU] > On Behalf Of adastra > Sent: Monday, February 16, 2004 2:11 AM > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [PIC]: Olin has been Deleted! (was insuccesses) > > I have changed the subject of this post because I think that many people > who may not have been following the original thread will want to weigh > in on this. > > I personally think that James' assertion that "No amount of excellent > advice is worth being called an idiot" is simply absurd. Olin is > obviously one of the most valuable and prolific contributors to this > list and certainly has earned a bit of extra grace in my book. > > In any case, the supposed cure is far out of balance with the offence. > I seriously doubt that the anonymous OP was psychologically damaged by > the suggestion that his request was idiotic... certainly not to the > extent of needing the list host's "protection." On the other hand, I > regard the loss of Olin's (mostly) very thoughtful and helpful input as > a very great loss indeed. And you might want to notice that unlike many > the ugly "flame wars" of the past, this was at least PIC related. > > I ask James to please reconsider this hasty and unwarranted action. > > Foster > > > > -----Original Message----- > > From: pic microcontroller discussion list > [mailto:PICLIST@MITVMA.MIT.EDU] > > On Behalf Of James Newton, Host > > Sent: Sunday, February 15, 2004 8:43 PM > > To: PICLIST@MITVMA.MIT.EDU > > Subject: FW: [PIC]: PIC18F8720 insuccesses > > > > Olin has been deleted from the PICList. > > > > No amount of excellent advice is worth being called an idiot. > > > > > > --- > > James. > > > > > > ----- Original Message ----- > > From: "Olin Lathrop" > > To: > > Sent: Sunday, February 15, 2004 10:10 AM > > Subject: Re: [PIC]: PIC18F8720 insuccesses > > > > > > > No Religion wrote: > > > > This is my code, as shown by IC-Prog: > > > > 0000: D00F 0000 0000 0000 0000 0000 0000 0000 > > > > 0008: 0000 0000 0000 0000 0000 0000 0000 0000 > > > > 0010: 0000 0E00 6E92 6E93 6E94 6E95 6E96 6E97 > > > > 0018: 6E98 6E99 6E9A 0000 0000 0000 0000 0000 > > > > 0020: 0EFF 6E80 6E81 6E82 6E83 6E84 6E85 6E86 > > > > 0028: 6E87 6E88 0000 0000 0000 0000 0000 0000 > > > > 0030: D7DE 0000 0000 0000 0000 0000 0000 0000 > > > > > > You can't be serious! You actually expect someone else to > disassemble > > this? > > > Think again. > > > > > > > And this is the configuration: > > > > Config1 = 2500 > > > > Config2 = 000F > > > > Config3 = 0080 > > > > Config4 = 0081 > > > > Config5 = C0FF > > > > Config6 = E0FF > > > > Config7 = 40FF > > > > ID Value = 0123456789ABCDEF > > > > > > > > Is there anything wrong in my machine code > > > > > > I doubt to many people are going to waste time trying to find out. > Get > > > real. > > > > > > > (for this quick test > > > > I don't want to nor I think I need to install MP-Lab. > > > > > > This is rediculous. You are asking for help with code you haven't > even > > > bothered to run past the MPLAB simulator. Come back when you've > done > > your > > > homework. Until then I've got better things to do. > > > > > > > I tried it and hated it, > > > > > > What didn't you like? > > > > > > > I will write my own source level debugger and > > > > assembler and release it to the PD after I'm finished). > > > > > > I'm not holding my breath. > > > > > > > It's supposed to be a BRA to 0010, where it will meet a NOP > > > > (no reason in particular) > > > > > > The preferred method is to wave a dead fish of the manual during a > full > > moon > > > and pick whatever instruction it drips on first. > > > > > > > Finally (through some NOPs, > > > > again, just to leave some space for inserting other code for > > > > experiments) > > > > > > This is going from the rediculous to the idiotic. With proper > assembler > > > source you could insert any number of instructions later. > > > > > > > Addresses don't represent bytes, but instruction words. > > > > > > Actually it's the other way around on the 18 family. > > > > > > > I know it's tedious to go through machine code. > > > > > > Duh! > > > > > > > but if you're kind enough, > > > > > > You're being an idiot, and I don't have time to waste on idiots. > > > > > > > Or, in alternative, could some kind soul post a small .HEX file > > > > with a demo program that just turns some port pins ON and some > > > > others OFF, just to see if my problem lies in my hardware or in > > > > my code? > > > > > > There are many samples out there, including a bunch on my own web > site. > > > However, they are all written in assembler so I won't bother you > with > > them. > > > > > > > I hope to get your valuable help. > > > > > > I bet, but you won't get it until you respect my time. > > > > > > > I really don't know what to experiment else. > > > > > > Write your code in assembler, then test it with the MPLAB simulator. > > Once > > > you've taken reasonable steps to understand and diagnose the > problem, > > THEN > > > you can come back and ask again. Posting unsimulated raw machine > code > > will > > > just get you dismissed as an idiot. > > > > > > > > > ***************************************************************** > > > Embed Inc, embedded system specialists in Littleton Massachusetts > > > (978) 742-9014, http://www.embedinc.com > > > > > > -- > > > http://www.piclist.com hint: To leave the PICList > > > mailto:piclist-unsubscribe-request@mitvma.mit.edu > > > > -- > > http://www.piclist.com hint: To leave the PICList > > mailto:piclist-unsubscribe-request@mitvma.mit.edu > > -- > 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: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads