Menu

SOS

Help
2022-04-24
2022-04-24
  • Bertrand BAROTH

    Bertrand BAROTH - 2022-04-24

    Help ...
    1) Are the expressions in lines 8, 85 and 95 OK (using HSerReceive as a function and addressing directly an element in a string) ?
    2) I didn't use the blocking option for USART1 because in the loop lines 61 to 64 I will finally add another condition to leave the routine : data received on USART1 or key pressed, connected to parallel port.
    3) What THE HELL do the cryptic error messages mean when I try to compile ?
    :(

     
  • Anobium

    Anobium - 2022-04-24

    These posts are public and this may set the wrong impression.

    1) #8. Not an approach I would use. 85. Yes, 95, Yes. But, 95 is a comment.
    2) Your #8 may work. But, use Wait While UDRE0 = Off would be better as you are testing the interrupt bit.
    3) Your code as strange variables. Do exactly what the error messages states.
    a. Examine Parole.lst
    b. Search for the error 'LDS SYSVALUECOPY,$FF', what is the source ASM ?
    c. So, search the ASM for $FF as shown the error is an SFR called $FF. I found this is in theASM
    ..

    ;PortB = $FF
    lds SysValueCopy,$FF
    out PORTB,SysValueCopy
    

    Not sure what $FF is doing here.... there are other variables the same.
    d, Change the errant variables to hex values and it compiles.

    Compiling c:\Users\admin\Downloads\Parole.gcb ...
    Done (Compile time: 0.812 seconds)
    
    Summary:
         Read by GCBASIC:
              Input lines: 79
              Subroutines: 426
         Chip resource usage:
              Program Memory: 385/8192 words (4.7%)
              RAM: 22/1024 bytes (2.15%)
              OSC: 4Mhz
    
    Assembling program ...
    
    Program assembled successfully
    
    Done
    
     

    Last edit: Anobium 2022-04-24
  • Bertrand BAROTH

    Bertrand BAROTH - 2022-04-24

    I modified lines 7 and 8 and so my "philosophy" to detect the beginning of input stream on USART1 (BTW my old algorithm was false, I read USART1 twice) ; and I removed all $ signs (an old habit from Pascal instead of 0x for hex litterals) ; and now it gets compiled OK ; but to test I am waiting for some hardware ... from China !

     
    • Anobium

      Anobium - 2022-04-24

      Excellent, if you have some simple words I could use to change the 'cryptic error messages' then that would help the project.

      Good news on progress.

       

      Last edit: Anobium 2022-04-24

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.