PDA

View Full Version : Self update of devices



Ioannis
- 30th April 2009, 08:03
I am sorry if this has been covered before but cannot find it.

I want to add support to Microcode Studio and PBP for the 16F727 device (relatively new).

Most of the registers are common with other chips, but how can a new .inc file make the Microcode studio and PBP aware of the new file?

I wish they updated the files more often...

Ioannis

Acetronics2
- 30th April 2009, 09:25
Hi, Ioannis




;************************************************* ***************
;* 16F727.INC *
;* *
;* By : Leonard Zerman, Jeff Schmoyer *
;* Notice : Copyright (c) 2008 microEngineering Labs, Inc. *
;* All Rights Reserved *
;* Date : 04/21/08 *
;* Version : 2.50b *
;* Notes : *
;************************************************* ***************
NOLIST
ifdef PM_USED
LIST
include 'M16F72x.INC' ; PM header
device pic16F727, XT_osc, wdt_on, protect_off
XALL
NOLIST
else
LIST
LIST p = 16F727, r = dec, w = -302
INCLUDE "P16F727.INC" ; MPASM Header
__config _CONFIG1, _XT_OSC & _WDT_ON & _CP_OFF
NOLIST
endif
LIST

#define EEDATA PMDATA
#define EEADR PMADR
#define EEDATH PMDATH
#define EEADRH PMADRH
#define EECON1 PMCON1



But, I keep on thinking Downloading the PBP 2.50 "C" PATCH wouldbe simpler than pasting that file into your directory ...



PICBASIC PRO(TM) Compiler 2.50c, (c) 1998, 2008 microEngineering Labs, Inc.

regards

Alain, who posted a while ago about this the new relase ... Never read Friend's Posts ??? Booooooooooooooooooooooo !

Ioannis
- 30th April 2009, 09:58
Sorry my dear friend, I guess I missed that post! I also did not notice that there is new patch for the compiler. Sure I will update soon. Now where did I put that receipt....

One more. I tried to edit the .ini file in the Microcode studio directory,but seems it has no effect on the menu selection. It still shows the same PICs as before the edit. Any tip on this?

Thanks,
Ioannis

mister_e
- 30th April 2009, 11:48
I just tried it myself here and, it seems the latest version of MCS don't care if you add device in the pic.ini list. So in theory, MCSP should scan the .INC file in your PBP folder and build a list automatically.

Ioannis
- 1st May 2009, 11:55
Hm, intersting. Yes, it searches the PBP file for the *.bas of the relevant PIC and not the .inc.

I made a copy of file, changed to *aa.bas and voila! It showed up in the drop down list.

This means that when you update the PBP Compiler, you have Microcode already updated!

Nice.

Ioannis

StoneColdFuzzy
- 22nd December 2009, 21:19
I'm using PICBASIC PRO™ version 2.45. Is there a way to add support for the PIC16F727? I don't see it in the drop down in MCS 3.0.0.5.

~ Dave

Melanie
- 23rd December 2009, 08:51
You could try creating your own INC and BAS files - you 'might' be lucky and that could be all that was needed... but more complex features may have required changes to the core compiler itself. Try it and see... but upgrading is so cheap anyway, treat yourself to a Christmas prezzy...

ardhuru
- 23rd December 2009, 17:25
Not quite relevant to this thread, but it does concern Microcode Studio Plus. I've been using the 16F88X chips quite a bit, and would love to see MCSP ICD support for these. I wrote to Mecanique a couple of times but got no response.

There was a thread pertaining to this issue http://www.letbasic.com/forum/showthread.php?t=4945 where David gave a link for an updated set of ICD files, but although the 16F88Xs are listed, they do not exist in the actual download.

Is there a way to add this support oneself?

Anand

Ioannis
- 23rd December 2009, 21:58
Which compiler do you refer too??

Ioannis

ardhuru
- 24th December 2009, 01:29
PBP 2.47, MCSP 3.0.0.5.

Anand.

Ioannis
- 24th December 2009, 09:46
2.47 supports the F88x chips. This has nothing to do with MCS.

If the compiler supports the PIC then so does MCS.

Maybe your issue is something else. Are the *F88x.bas and *F88x.inc files present in your PBP directory??

Ioannis

ardhuru
- 24th December 2009, 12:08
This has nothing to do with MCS.

If the compiler supports the PIC then so does MCS.



No, I think you've misunderstood the issue; I am referring only to the MCSP ICD capability for these chips.

Anand

Ioannis
- 24th December 2009, 12:20
No I did not. MCS capability depends oin the compiler.

Ioannis

ardhuru
- 24th December 2009, 12:44
Including the MCS in-circuit debugging capability?

Anand

Archangel
- 24th December 2009, 14:35
Are you using the PRO version or the freebie? I have the pro version and while I do not use it, it seems to support that PIC.

ardhuru
- 24th December 2009, 14:56
MCS Pro.

Does the folder "ICDModels" in your install have a file for 16F88x? Mine doesnt. Alphabetically sorted, after 16F877A mine jumps to 16F913.

Regards,

Anand

Archangel
- 24th December 2009, 17:17
MCS Pro.

Does the folder "ICDModels" in your install have a file for 16F88x? Mine doesnt. Alphabetically sorted, after 16F877A mine jumps to 16F913.

Regards,

Anand

"ICDModels" ? I just have a bunch of buttons like ICD Compile, RUN . . . that work when 16F88 is selected. Try the Online Updates from the View Tab. Maybe your version is too old. They have never charged me for an update either, only the initial purchase of the Pro version.

ardhuru
- 24th December 2009, 17:49
"ICDModels" ? Try the Online Updates from the View Tab. Maybe your version is too old. They have never charged me for an update either, only the initial purchase of the Pro version.

I am referring to a folder called "ICDModels" within the main MCS Plus folder which contains .icd files for all the supported chips. I too have been able to update periodically after the initial purchase some years ago.

The 16F88 never was a problem; its only the 16F886, 16F887 etc. that I'm referring to.

Anand