Menu

98_07 - Unable to compile program written in - resolved

wn
2021-06-05
2021-06-18
  • wn

    wn - 2021-06-05

    I get the following output when invoking Make Hex. The arrays are all less than 48 elements. I am programming a mega328PB chip. Some interrupts are invalid as well so not sure what is going on?

    Warning: The selected chip speed may be too high
    Error: The array RNDBALL1 is too large
    Error: The array RNDBALL10 is too large
    Error: The array RNDBALL2 is too large
    Error: The array RNDBALL3 is too large
    Error: The array RNDBALL4 is too large
    Error: The array RNDBALL5 is too large
    Error: The array RNDBALL6 is too large
    Error: The array RNDBALL7 is too large
    Error: The array RNDBALL8 is too large
    Error: The array RNDBALL9 is too large
    Error: The array SYSSTRINGPARAM1 is too large
    Error: The array SYSSTRINGPARAM2 is too large
    Error: The array SYSSTRINGPARAM3 is too large
    Error: The array SYSSTRINGPARAM4 is too large
    Error: The array SYSSTRINGPARAM5 is too large
    Error: The array SYSSTRINGPARAM6 is too large
    Error: The array BALLORDER is too large
    Error: The array BALLWAITTIME is too large
    Error: The array BTSTR is too large
    Error: The array BTTMP is too large
    Error: The array CMD is too large
    Error: The array LEFT is too large
    Error: The array MID is too large
    Error: The array RESULT is too large
    Error: The array SYSTEMPARRAY is too large
    Error: The array BALL1 is too large
    Error: The array BALL10 is too large
    Error: The array BALL2 is too large
    Error: The array BALL3 is too large
    Error: The array BALL4 is too large
    Error: The array BALL5 is too large
    Error: The array BALL6 is too large
    Error: The array BALL7 is too large
    Error: The array BALL8 is too large
    Error: The array BALL9 is too large
    Error: The array STR is too large
    Error: Excessive RAM usage! Delete some variables, reduce the size of
    arrays, or upgrade to a more powerful chip
    v701_DrillLock.gcb (253): Error: Invalid interrupt event: TIMER2OVERFLOW
    v701_DrillLock.gcb (275): Error: Invalid interrupt event: PINCHANGE3

     
  • William Roth

    William Roth - 2021-06-06

    Please provide your code.

     
  • wn

    wn - 2021-06-06

    Here are the DIM statements for the Arrays

    dim ball1(9)
    dim ball2(9)
    dim ball3(9)
    dim ball4(9)
    dim ball5(9)
    dim ball6(9)
    dim ball7(9)
    dim ball8(9)
    dim ball9(9)
    dim ball10(9)
    dim rndball1(30)
    dim rndball2(30)
    dim rndball3(30)
    dim rndball4(30)
    dim rndball5(30)
    dim rndball6(30)
    dim rndball7(30)
    dim rndball8(30)
    dim rndball9(30)
    dim rndball10(30)

     
    • Anobium

      Anobium - 2021-06-06

      Where is the rest of the code?
      Attach the complete program and this will determine total memory available/used.

       
  • Anobium

    Anobium - 2021-06-06

    And, very importantly, this is a user supplier DAT file by @wn
    So, is the memory correct? I do not know as we have not tested this DAT file.
    Does the code compile using a K42 PIC? or a LGT AVR chip?

     
  • William Roth

    William Roth - 2021-06-06

    It appears that the mega328pb datfile is a bust. It shows PROG = 0 and other issues.

    There was no datafile for mega328pb back in version 98.02 so I am guessing the code may have been written for mega328p (arduino uno) or something else.

    Post your complete code for the chip it originally worked on. Or try on chips other than mega328pb.

    As of now the mega328pb is not supported until a proper datfile is crafted.

     

    Last edit: William Roth 2021-06-06
  • wn

    wn - 2021-06-06

    Also, when I make the hex file sometimes the encoding of the GCB file changes to UTF-8 BOM and throws a syntax error. What would be causing this?

     
  • wn

    wn - 2021-06-06

    I have been compiling using the @wn file successfully in 98_02. In fact, it may be the file I originally modified that has been included. I did a diff between the supplied 328PB.dat and the one I use and there are significant differences. I am more that willing to work with you and the team to get it sorted out.

     
  • Anobium

    Anobium - 2021-06-06

    We will need Mega328pb Xplained Boards or something similar. Samples of the chip are available but we need clocks etc, and, some method to program. Hence, the Xplained board is best.

     

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.