+ Reply to Thread
Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Some Bugs...

  1. #1

    Default Some Bugs...

    Recently i bought Proton complier
    I updated it to the last version
    It's look great but i found some serious bugs :

    1.When i write the command
    "CWrite 8000,[1,0,4,0,7,0,"*",0,2,0,5,0,8,0,0,0,3,0,6,0,9,0,"#",0] "
    in the memory it's write the initials numbers with "3F" thus when write 1 the value is 3F01, 2 = 3F02 etc...
    if i write just 1 number it's ok, but if it's many numbers (like in the line up,the bug is occured

    2. I must using addresses from memoy, so i have using with poke command
    'Poke COUNTERT,ClickedTimer"
    (COUNTERT and ClickedTimer are words variables)
    if i write the address directly like "poke 7,ClickedTimer" so it's ok.
    but if i write the address by variable "poke var1,var2 " it's done nothing
    With the 2nd data, has no problem if it's variable

    Thanks
    Erez

    Hi, its great to see you visiting our forum. Why not try Proton Compiler for FREE?

    Download the FREE version of Proton Compiler, Its called Amicus18 and its available from HERE

    Already using proton Compiler??? Get rid of these pesky messages... get LICENSED USER STATUS




  2. If you're a Licensed user of PROTON DEVELOPMENT SUITE, apply for Licensed User Status to remove these pesky messages
     and get access to additional forum areas, Beta test downloads and more!

  3. #2
    Licensed User Tim's Avatar
    Join Date
    Jan 2003
    Location
    london
    Posts
    6,950


    Default Re: Some Bugs...

    1 Pic type
    2 Some code we can test
    3 Can you point me to where in the manual Poke is a command?
    Tim

  4. #3
    Licensed User cgriffin's Avatar
    Join Date
    Oct 2003
    Location
    CA
    Posts
    1,249


    Default Re: Some Bugs...

    Tim must be busy; he's being brief!

    On the cwrite, you do know that you must erase it prior to writing, right? The PIC type will determine how much must be erased.
    In addition, because you are complaining of the preceding 3f, then I'm going to guess you are using a 16f, because if you read the manual (pg 160) it clearly states that $3fff is the max number available... I'm going to guess that if you tell it to write a byte that it is ONLY going to write the byte, and the top 6 bits are going to stay at $3f. Because 16f PIC's do not have 16 bit code space (they have 14 bit commands), you cannot write two bytes consecutively into memory, because it doesn't hold 2 bytes.

    Peek and Poke are unsupported keywords...kind of an unnecessary hangover from the old days. Describe your goal, and somebody here will likely be able to help you with a better method.

  5. #4
    Unregistered
    Guest Unregistered's Avatar


    Default Re: Some Bugs...

    Quote Originally Posted by Tim View Post
    1 Pic type
    2 Some code we can test
    3 Can you point me to where in the manual Poke is a command?
    1. I operate it on 16f877.
    2. poke 8,var of byte type - this is works
    poke var1,var2 - this is not work at all
    3. sorry, i don't understand your question

  6. #5
    Licensed User Tim's Avatar
    Join Date
    Jan 2003
    Location
    london
    Posts
    6,950


    Default Re: Some Bugs...

    Were in the manual is the Poke command that you are talking about?

    Post the section from the manual so I can see the syntax
    Tim

  7. #6


    Default Re: Some Bugs...

    Actualy Tim Peek and Poke are valid commands. They are just not documented.
    Regards
    Charlie M.

  8. #7
    Super Moderator wastrix's Avatar
    Join Date
    May 2008
    Location
    Sydney, Australia
    Posts
    2,555


    Default Re: Some Bugs...

    The reason why a command may not be documented is usually because it is deprecated, is "advanced" or "dangerous" or in beta stage - possibly they do not work in all cases or they are only kept to maintain semi-compatibility with old programs and other languages like for the Basic Stamp, etc.

    In general, if a command/directive/etc. is not documented, presumably it would have been removed or neglected to be put in by Les for a reason and so it is not good practice to use it in new programs.
    Last edited by wastrix; 28th October 2010 at 10:56.
    "If you have an important point to make, don't try to be subtle or clever. Use a pile driver."
    - Winston Churchill
    If you want to contact me, please email me, don't PM me.

  9. #8


    Default Re: Some Bugs...

    point being it is still a valid command. If it is not recommended for use then it should be removed.
    Regards
    Charlie M.

  10. #9
    Licensed User Tim's Avatar
    Join Date
    Jan 2003
    Location
    london
    Posts
    6,950


    Default Re: Some Bugs...

    The point is it is a non supported command. I was left in for backward compatibility, there are loads of commands not used but the name is reserved. As I said in my post.

    "Post the section from the manual so I can see the syntax"
    Tim

  11. #10


    Default Re: Some Bugs...

    __________________________________________________ __________________
    Why take off these important commands (peek & poke) insteed just fix the bugs ?
    This commads exist properly all the other pic's languages, so no reson it's not in Proton....
    i used by them to choose the right outputs or inputs by a smart multi-data table from memory, so the program determine by the data which port and what is the data.
    In this way the program is so small, smart fast and effective

    Thank

    Erez
    __________________________________________________ __________________

    Quote Originally Posted by Tim View Post
    The point is it is a non supported command. I was left in for backward compatibility, there are loads of commands not used but the name is reserved. As I said in my post.

    "Post the section from the manual so I can see the syntax"

+ Reply to Thread
Page 1 of 3 123 LastLast

Similar Threads

  1. Fuse configurator bugs ?
    By boezio in forum Fuse Configurator
    Replies: 3
    Last Post: 20th September 2009, 22:11
  2. I find any bugs!
    By atomix in forum Proton Plus Compiler v3
    Replies: 5
    Last Post: 2nd November 2007, 13:50
  3. Proton bugs in Toshiba commands?
    By J. Mark Wolf in forum Proton Plus Compiler v3
    Replies: 2
    Last Post: 3rd March 2007, 21:26
  4. optimizer and endless loop bugs?
    By boezio in forum Proton Plus Compiler v3
    Replies: 8
    Last Post: 3rd June 2006, 16:01

Members who have read this thread since 2nd May 2012, 20:57 : 0

Actions :  (Set Date)  (Clear Date)

You do not have permission to view the list of names.

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts