|
|
|
Re:Building an ENC28J60 Ethernet Dev Board
|
|
Date: 2006/03/13 17:09
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
|
Can you post your hex file for the pic, I am trying to ascertain whether it's the pic which is the problem.
|
|
|
|
|
|
Re:Building an ENC28J60 Ethernet Dev Board
|
|
Date: 2006/03/13 17:09
|
By: Ian
|
Status: Moderator
|
|
|
Karma: 5  
|
|
| Posts: 85 |   | |
|
I have uploaded the hex file to the bottom of the article. Have you tried writing a simple few line program for the PIC just to flash the LED. That would demonsrate if you have built the PIC section of the circuit correctly.
|
|
|
|
|
|
Re:Building an ENC28J60 Ethernet Dev Board
|
|
Date: 2006/03/13 17:10
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
Ian, I can't find it, can you attach it again. Regarding the led, I am trying this as we speak, at the moment no leds are on, so something is wrong with the program. Can you confirm that your led is flashing (LATD0) and did you use any special sequence when powering up, i.e. is there a switch you are pressing or something like that. I am using LVP, but this wouldn't change things would it?
|
|
|
|
|
|
Hex File
|
|
Date: 2006/03/13 17:10
|
By: Ian
|
Status: Moderator
|
|
|
Karma: 5  
|
|
| Posts: 85 |   | |
|
The .hex file is at the bottom of the article, under the links section. Yes the LED is on RD0. If you noticed it, sorry for the eariler typo. LVP shouldn't make any difference as long as it verifies ok.
|
|
|
|
|
|
Re:Hex File
|
|
Date: 2006/03/13 17:11
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
Ian, I found the hex file. Here is what I have done: I downloaded the stack from microchip website (your link is wrong by the way!!!!!!!) I made the changes you specify, and compiled. I then compared your hex to my hex with a text difference program and they are completely different, can you explain that? What I suggest to you, is to repeat the above sequence and see if you still arrive at the same hex file. This is why I am saying that this project is not working. Clearly it is working for you, but from your instructions it is not possible to repeat your results.
|
|
|
|
|
|
New Thread in Forum
|
|
Date: 2006/03/13 17:12
|
By: Ian
|
Status: Moderator
|
|
|
Karma: 5  
|
|
| Posts: 85 |   | |
|
Which of my links is wrong? There are many obvious reasons why my hex isn't the same as yours. I just uploaded my lastest hex which I think has a slightly different website in. I have now replaced the hex for you with one following the exact procedure listed in the article. Even now it will probably be different to the version you compilied. It is very likely that I'm using a different version of the complier to the one you have, mine is the Student Edition and does not run code optimization. It is possible to repeat the results as some people on the forum have done. I have added a new post to the forum suggesting ways of testing the different parts of the circuit you have built. Forum Post I have checked my board schematic again and I can't find any error in it, is your board identical to it?
|
|
|
|
|
|
Re:New Thread in Forum
|
|
Date: 2006/03/13 17:42
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
Ian, thanks for your time We are using similar versions: My mplab is 7.30 - (which is the currently recommended one) My C18 is 3.02 Demo (Student ver, is called now Demo) My stack is MCHPStackENC8722v302.exe, I assume this is what you are using. Can you do this for me - recompile your program, then from your output window copy all the text, and post it so that I can see which optimizations you are using. I have just compared your new hex with my one and it is shorter, so you must be running some optimizations (I disabled all my optimizations as per your suggestion). By the way, if you uninstall your compiler, and then reinstall it, you get your 58 days full optimizations once again.
|
|
|
|
|
|
Re:HEX FILE
|
|
Date: 2006/03/13 20:49
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
Ian, I hope you find my message, the discussion disappeared suddenly.
Your hex file is now the same size as mine, but there are about 10 lines which are different. Can you think of any changes you might have made which are not mentioned?
|
|
|
|
|
|
Re:HEX FILE
|
|
Date: 2006/03/13 23:53
|
By: Ian
|
Status: Moderator
|
|
|
Karma: 5  
|
|
| Posts: 85 |   | |
|
I guess those difference are in the first 10 lines. They are likely to be from a slightly differnet complier or the linker files may have been updated between 3.00 and 3.02.
I wouldn't worry about it tho. Have you tried the steps I suggested in the other forum post to check that you hardware is built correctly?
Forum Post
Ian
Post edited by: mat, at: 2006/03/13 23:59
|
|
|
|
|
|
Re:HEX FILE
|
|
Date: 2006/03/14 12:30
|
By: xx
|
Status: Visitor
|
|
|
|
|
|
|
Ian, Are you sure there are no changes you are forgetting.
If you are not sure, it would help me very much if you can check the dates of your files to see if you did not change any files other than compile.h and maindemo.c, and then check with windiff that there are no other changes in those 2 files.
Regarding your question I do not have all the hardware at the moment so I can't comment on those tests.
|
|
|
|
|
|
Re:HEX FILE
|
|
Date: 2006/03/14 12:44
|
By: Ian
|
Status: Moderator
|
|
|
Karma: 5  
|
|
| Posts: 85 |   | |
|
Given that my article changes the enc28j60.c file and the compile.h file and you have apparently changed the maindemo.c and the compile,h then it is unspurising that your hex is different to mine.
I object to you saying this project doesn't work when you haven't built the hardware. Get the hardware running and then worry about the hex not being exactly the same, it is most likely to be the slight version difference between our MPLabs and MCC18 producing slightly different code.
Ian
|
|
|
|