|
No, you have a problem... WRITING the value TWICE is not correct.
You DO need up-to-date PBP and MPLAB (MPASM) as there was an EEPROM issue going back to v2.45 I think. Half the problem was Microchips Assembler too. Latest versions of everything work as expected in this department. Unfortunately I don't have that particular PIC to confirm your results.
http://www.picbasic.co.uk/forum/showthread.php?t=547
|
Thanks , Mel, but ...
My PbP and MPASM are the last versions : I verified it this morning ... and re-loaded PbP and its patch
PbP 2.46 Patched and MPASM 5.02 ...
Sorry, Mel ...
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
|
You have CONFIRMED you are invoking the latest PBP and MPASM and not an old installed version by mistake or error in path statements?
|
Sorry ...
YES, I do confirm ... old versions are always thrown to the trash box ...
PbP used version seen in the MPLAB / Output/ Build window too ...
Alain
Last edited by Acetronics2; - 6th April 2006 at 15:18.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
|
Just because I'm a nice girl, I've ordered one... hopefully, I'll have a 18F1320-I/P tomorrow...
|
Humour at the end
Hi, Mel
And you know why I tried to use the 18F1320 ???
Just because 16F648 and 16F88 are not so easy to find by one part ...
This gadget will be published this summer inside THE only FREE model Webzine ( http://aeronews.free.fr/index.html ) ... no money to earn for me .. or so little !!!
.... Funny, I got This from Jeff Schmoyer ...
" If it works well with the 16F88, you might want to stick
to that device. You might also want to compare the
erratas from Microchip on the devices you are using. "
What to think of that ???
Thanks for your Help,
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
|
That's maybe just another Microchip way of reinvent the wheel.... This may be another specific device who need another special method to write to eeprom and plah plah... BUT how about if you use the assembler method stated in the datasheet AND/OR errata to write to the eeprom?
Could also be another MPASM problem... wich is still possible. Did you contact Microchip tech-Support http://support.microchip.com Usually they answer within 24 hours
Sorry Alain i don't have any handy 18F1320 to test it. I'll order some sample for myself too to play with them when health permit to stay awake more than 1 hour steady.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
I'm thinking that swapping a $2 part for the most expensive item on the menu at Le Cinq next time I'm in Paris is a good investment *smiles*
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks