Viewing 8 posts - 1 through 8 (of 15 total)
  • Author
  • #8836

    Goodmorning everyone, I have recently joined and it is my first post.
    I am recently working with Proton Basic and I have a problem with the configuration bit for a 16F88.
    I cannot define the use of the internal oscillator with the two pins RA6 and RA7 used as I / O.
    After much research, I found a plugin for Proton, PIC fuse configurator, but it doesn't work anyway.
    I create the following two lines at the beginning of the program:

    Config2 FCMEN_ON, IESO_ON

    Unfortunately, compiling gives me an error: Invalid fuse setting FOSC_INTOSCIO.
    I do not know what to do.
    Seggerimenti build…..


    even if I run the risk of being unpleasant and nuisance… you said you recently used Proton Basic, so you can still save yourself… 🙂
    Forget the Jurassic stuff and use MPLAB X IDE (programming in C or assembler). E’ all free and also multi-platform.
    I know, it is another environment and another language, but it is a small effort that I think is worth doing.
    You will have a professional and well-supported IDE in front of you, and used by half the world…
    A greeting.


    Hello and thanks for the reply. I've been using MBPro for years (I only know the basic) but now given its characteristics, I dusted off and updated Proton which I haven't used in a long time.
    Proton is very nice because you can combine it with Proteus for a very interesting debugging. Unfortunately I don't know the “C”, let alone the assembler (even though I started with Nuova Elettronica and the ST6) and I honestly don't feel like learning another language. I tried but I always gave up. Now I just have to figure out how to solve the problem described, I hope for some suggestions.


    While agreeing with the use of C as a programming language, with a simple search I found this
    to page 161 you have the instructions to configure the fuses.
    I can not help you more I do not know such programming language, I also started with the basic then migrated to C for its simplicity and ease of finding libraries and solutions to every problem on the net. Once analyzed, I adapt to my project without many problems.


    Ciao, yes the manual is the first thing I looked at, but it doesn't solve my problems.
    OSC_HS is fine, but that's not what I need. What is strange, is that I have used the proton PIC fuse configurator for another pic and everything is fine.
    That's a problem with the 16F88?????
    I have to configure the pic with the internal oscillator and use the two pins of the oscillator as normal I / O ports, otherwise the project will fail.
    You see, I am of a certain age and I don't want to start studying the “C”…..I understand, I interpret it, I modify it, but creating from scratch remains difficult for me. I have known the basic since the days of the ZX80 sinclair


    Forget the Jurassic stuff and use MPLAB X IDE (programming in C or assembler). It's all free and it's also multi-platform.

    How much free one notices from the volume created by’ The resulting HEX.
    For those who have not done so many studies for a language, just writing as an amateur with the first computers, the basic has been learned, Between different compilers, I see that the proton compiles commands very well with high levels of optimization also a flexibility to enter their own routines and hybrids.


    Yup, the free version has inactive optimizations, but for normal use it doesn't make much difference.
    With the latest generation PICs you have enough Flash, and using the assembler the problem does not arise (if you use PICs with few resources, the assembler is still to be kept in mind as a possible choice).
    For example the PIC17F47Q10 that I am starting to use has 128KB of flash and costs 1.7 € (excluded taxes) for the DIP-40 version (the SMD version also costs less).

    Then no one forbids using Atmegas with the ATMEL STUDIO IDE, also free and without optimization problems “castrate” (if I remember correctly) or STM32 with CubeIDE.
    Obviously all with the C / C ++ or Assembler language.

    Then I understand that if you are used to the Basic and it is also quite optimized and you do not want to change it might as well stay.

    • This reply was modified 3 years, 7 months ago by Just4Fun.
    • This reply was modified 3 years, 7 months ago by Just4Fun.

    I agree that as amateurs you rely on your own experience, maybe gained with the first computers that had the basic, Even an approach with PICs have pushed to the basic, come PICAXE.
    At the event with easy information, instead, they are found to be obsolete MCU-based experiences. For this the amateurs, including me, have opted to take those MCUs and / or have stock to dispose of.
    obviously, proton basic offers a free version for a good portion of MCUs that may be on the obsolescence list.
    Instead one should also think that there are MCUs with better performance and less cost. Also because the market policy invites you to take the latest productions.
    I admit that I would be inclined not to use MCUs with the bank memory structure anymore, one tortures even if the language does not show it, but that you pay for with a higher volume of code. Unfortunately, I still have stocks and that's why it doesn't make me want to spend more money, for small home projects.

Viewing 8 posts - 1 through 8 (of 15 total)
  • You must be logged in to reply to this topic.