----- Original Message ----- From: To: Sent: Sunday, February 15, 2004 9:51 PM Subject: [OT]: was [PIC]: PIC18F8720 insuccesses > Well, I'll have to keep that in mind when I am not willing to try the the > tools provided by the manufacturer to solve my problem. The OP said he had tried MPLAB and hated it. Personally I don't see what is to hate about it but to each his own. I wouldn't bother with writing machine code myself but if someone wants to do so that does not make them an idiot. Sure it is slow tedious and a lot of work but so is doing a PIC project compared to going to Radio Shack and buying a $20 timer (for example). But that is what this is all about - learning and the ability to put your own spin on something. Even though I am fluent in C++ and could have used a C compiler I have done all of my micro programming in ASM. I will probably switch at least partially to C in the future to save time but I am glad that I am fluent in assembly, it helps my C++ programming, and I find it interesting and enjoyable. Maybe the OP feels the same way about machine code. In any case, he knew that there was an IDE available, he chose not to use it and he asked for debugging help or a verified working HEX file so he could test his hardware, not for opinions on his build environment. If you like machine code, help. If you don't, don't. Save your energy for answering my questions. ;-) > I 100% disagree with your decision James, Olin is an excellent resourse, > one whom I would say is to valuable to lose. My above comments standing, if PICLIST were under my control I would not have banned Olin. He is certainly one of the primary sources of advice and while he may think he knows a little more than even he does, (most of) his input will be missed by everyone. I don't remember any past warnings, but I do know that there have been enough remarks by Olin in the past that he has found himself a spot right on the edge of the asshole page in my book. However I know I can be there at times myself, and I think that many (at least a whole type) of motivated, intelligent, and/or successful people have some sort of hardware/software mod in the brain that creates those tendencies. "Wound a little tight" if you will. Re-reading Olin's post might make me say wound a lot tight, given the circumstances. If I worked for Olin and was trying to code a project in machine code for no apparent reason, I would think HE was the idiot if he didn't react that way. Here I agree with you, James, that this isn't appropriate behavior, but I think a ban (especially immediately without discussion and hearing response from Olin and/or the OP) is rash. I posted a reaction to Olin's post, so you know I don't think it should go unnoticed. But I don't think that the pattern of behavior is so consistent, especially when viewed as a ratio of good posts to bad posts, that it can't be handled on list. I've been around long enough to know that while Olin may be his own biggest fan, he's not a bad guy to have around. If I were his boss, I probably wouldn't be his best friend and there certainly would be some serious confrontations, but I doubt think I'd fire him either. Unless there is a mass of the list that disagrees, I think we should be allowed to handle Olin's attitude individually, as necessary. All in favor... Nick > > -Duane > > > On Sun, 15 Feb 2004, James Newton, Host wrote: > > > 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: 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