Searching \ for '[SX] Out of Space!!!' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/ubicom/devices.htm?key=sx
Search entire site for: 'Out of Space!!!'.

Exact match. Not showing close matches.
PICList Thread
'[SX] Out of Space!!!'
2005\12\27@045144 by inakin/a

flavicon
face
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, inaki wrote:

I went out of space on a SX48. My program is writen in SX/B so I think I could save some space coding in assembler but I see two  problems: first,the code is rather complex to code in assembler (and I am not an expert in SX asm coding) and second, I have realized that the code generated by the SX/B compiler is already very good! So I don't think I could improve it much.

The question now is: what to do next ? Recoding everything in assembler ? Perhaps adding a second SX48 and share de tasks between them ? What to do when running out of space ?


By the way, the SX52 has the same space that the SX48, isnt'it ?

---------- End of Message ----------

You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=102335
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)

2005\12\27@065849 by g_daubachn/a

flavicon
face
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, g_daubach wrote:

Second answer first: The only differences between the SX48 and 52 are the number of I/O pins, and the package, i.e. same size of RAM and program memory.

First answer next: As you know, program memory is segmented into pages. Hard to believe that all your program memory pages are filled up with code. After compiling the latest version of your program that did not run out of space, have a look at the list file ("Run - View List"). The list file shows you the generated machine code together with the addresses where it is stored in program memory. Hopefully, you'll find some empty space remaining in some pages. For a quick overview, after a compile, you can also do a "Run - Device" which will pop-up the Device window, showing you part of the program memory in hex in the E˛Flash section. Scroll through the hex code, and see if there are any areas containing a number of subsequent FFFs. These areas are empty and can be filled with more code.

Im must admit - I'm not very experienced with SX/B to tel you how to move parts of SX/B-generated code into other pages - maybe, you will have to do this by cut-copy-paste in the generatd assembly code output file but I'm sure someone else with more experience will bail in here - Bean?

---------- End of Message ----------

You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=102335#m102346
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)

2005\12\27@103459 by Chris Savagen/a

flavicon
face
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Chris Savage wrote:

Bear in mind that SX/B is a non-optimizing compiler, so if you have commands repeated throughout your code, they will take up a lot more code space.  For example, if you have a bunch of SEROUT commands, they will each take up a chunk of code necessary to handle the serial output.  However, if you put that into a subroutine and call it repeatedly, it only gets created once, so it will use a lot less space.  Perhaps you post your code.

---------- End of Message ----------

You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=102335#m102360
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)

2005\12\27@104457 by beann/a

flavicon
face
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, bean wrote:

Yes please post your code. And Chris is right, in SX/B it's best to put a subroutine "wrapper" around any high-level commands like PAUSE, SEROUT, SERIN, etc.
If you post your code I'm sure we can figure a way to squeeze it in without resorting to assembler (not that there is anything wrong with assembler).
Bean.

---------- End of Message ----------

You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=102335#m102364
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...