Peter: Thank you for your comment about over reacting. If we have glass feelings, we will always be fragile. Of course, it is important to let someone know that they have been offensive. But I happen to know people who behave offensively and are not even aware of it. I think we could be a little magnanimous. ----- Original Message ----- From: "James Newton, Host" To: Sent: Monday, February 16, 2004 3:44 AM Subject: Re: [PIC]: PIC18F8720 insuccesses > Stay or leave as you wish. Don't call people names. > > > --- > James. > > > -----Original Message----- > From: pic microcontroller discussion list [mailto:PICLIST@MITVMA.MIT.EDU] On > Behalf Of Per > Sent: 2004 Feb 16, Mon 12:36 > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [PIC]: PIC18F8720 insuccesses > Importance: Low > > Please delete me as well. Some of us are professionals. > At one time that was: Many of us are pro's. > > I think you have overreacted, probably because of a word that in this case > was quite appropriate. > If you read the original question carefully, you'll see that this guy calls > many of us idiots, although in a more covered form: > We use MPLAB which is useless, he is going to make a much better tool, while > we apes struggle with MPLAB, etc. At the same time he asks for help at a > level that reveals that he does not know much at all about microprocessors. > So I think Olin's reaction (and comments) are both fair and approproate. > > Regards, > Per Linne > Sweden > > > ----- Original Message ----- > From: "James Newton, Host" > To: > Sent: Monday, February 16, 2004 4:43 AM > 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 -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads