Holly crap... anyways, try to remove ALL MPLAB version, then re-install the latest version of it.
Assuming your PBP 2.50b is in the usual c:\pbp folder and MicroCode point to it... I'm out of ressources....
Printable View
Holly crap... anyways, try to remove ALL MPLAB version, then re-install the latest version of it.
Assuming your PBP 2.50b is in the usual c:\pbp folder and MicroCode point to it... I'm out of ressources....
Maybe the original CD from MeLabs was corrupted! :DQuote:
Originally Posted by mister_e
That link suggest that one should comment those lines that produce the "overwriting previous address content" the 118 error from corresponding .INC file, that is in this case C:\PBP\18F4550.INC.Quote:
Originally Posted by mister_e
I can find only one line (line 20) that is equal in that file:
__CONFIG _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L
The strange thing here is, that when compiling USBDemo.pbp again it blames again also on the same commented line in USBDemo.asm !! :eek:
I would have expected that line to disappear from the the generated 118-error list...
Is it somewhere else also :confused:
I have tried to look for it but can only find one in C:\Program Files\Microchip\MPASM Suite, but the content is quit different looking there.
comment ALL CONFIG lines in your c:\pbp\xyz.INC file
Code:;****************************************************************
NOLIST
ifdef PM_USED
LIST
"Error: PM does not support this device. Use MPASM."
NOLIST
else
LIST
LIST p = 18F4550, r = dec, w = -311, w = -230, f = inhx32
INCLUDE "P18F4550.INC" ; MPASM Header
;__CONFIG _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L
;__CONFIG _CONFIG1H, _FOSC_HSPLL_HS_1H
;__CONFIG _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
;__CONFIG _CONFIG3H, _PBADEN_OFF_3H
;__CONFIG _CONFIG4L, _LVP_OFF_4L & _ICPRT_OFF_4L & _XINST_OFF_4L
NOLIST
endif
LIST
EEPROM_START EQU 0F00000h
BLOCK_SIZE EQU 32
Unless I'm mistaken...and I don't think I am...isn't that what I suggested back in Post #26?
I think it is...I really do. I suggested that the O/P read the thread, the whole thread, and nothing but the thread. Either the O/P didn't get it, or the O/P didn't read it, because it's pretty much spelled out in black&white what to do, what not to do, and why what is happening actually happens and where to find the files...
This is weird, totally crazy :confused:Quote:
Originally Posted by mister_e
When I comment those lines, I can see that they are commented, but when I compile USBDemo.pbp it produces the same errors (118) and when I then take a look at that 18F4550.INC file again, the comment marks are gone :eek:
Then I thought that I shall make a small experiment. From file properties I changed it to read-only and the tried to compile USBDemo.pbp... The first thing that happens is "save as" 18F4550. Ok, now I now that PBP does write it over again and again. Next I unchecked the read-only feature and compiled USBDemo.pbp, et voila, for the very first time it compiled without errors :)
What did happen? Why do we have to go via read-only ???? to solve such a persistent problem... incredible... Can you explain this? Can you??? If you can , please do... Thank you :-)
I burned it to PIC and did not yet test anything else than plug and unplug it for several times and I'm really glad that the USB port is still alive, that is for the very first time in my USB history... well, DT's hex with my config was also working, but that is another story...
I will try the communication to my PC tomorrow.... Not too much sweet at once...
I'm glad at this point, very glad... Thank you Steve!
PS. What if such errors (118) pops up again at some stage? It's kind of difficult to believe that the aid is "go via read-only"?... ???
I don't know why it happened to you... usually you just comment those line, you save the "INC file .... ET VOILA!
Not much
Rien d'autre à changer
Compile and run
Away you go
Yada yada.
USBDeview is a nice tool to uninstal/remove/monitor your HID devices... handy and free
http://www.nirsoft.net/utils/usb_devices_view.html
I forgot to say that I found that the B-type USB connector shield was not properly connected to GND. When I noticed that I did connect it as it should be connected. It is kind of funny that the connector, it self is not connected and this leads to that the shield is "floating"?:mad:Quote:
Originally Posted by mister_e
I have a feeling that fixing that shield connection to GND helped to solve other parts of the USB connection problem. It did of course not have any effect to the compile problems...
I could have tried to delete the file 18F4550.INC before that "read-only" phenomena, but unfortunately I did not try it.
Now of course I can not do that! Maybe good so, but the mystery thing remains, who wrote (or copied from...) it over as long as I got the the error 118 over and over again....:confused:
For now:
Darriel, Steve, skimask ... THANK YOU
Thank you very much indeed, thank you all who helped with this many-faceted and persistent problem,...:)
Whatever your problem is/was, the most important thing is to solve it, and understand why :D