In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Tony Leyland wrote:

Hi PeterM,

I know what you mean, it does sound like I'm being a bit too 'picky' with my coding and trying to save unnecessary bytes. 

The program that I have developed runs on an SX48 as the SX/B code is too large for the smaller devices.  I'm now faced with
the problem of running out of program space on the SX48 (not enough debug space of approx 136 bytes at the end of ROM).

I've been going through the whole program (both my SX/B and my ASM code) to reduce byte count.  There is hardly any data
stored in the ROM, it is all much needed code routines.  I've already shaved over 300 bytes from my current optimisation procedures and
so I'm looking deeper in to my ASM code to futher reduce the byte count.

The project that I'm working on for my company involves the following:-

1)  A very accurate GPS unit is connected to my SX board using Bluetooth.
2)  The GPS time/speed string that arrives via BlueTooth is sent via a serial connection to a video overlay device that puts a display
     on live video, which is then recorded on a small Hardisk PVR device.
3)  I use a blue Matrix Orbital 20x4 LCD to display menu screens, where the operator chooses various options using 4 keys and displays current operation status.
4)  External I2C 256 byte EEPROM for storing user settings (like MAC address of detected BlueTooth GPS device).

As you can see, I'm pushing it somewhat in cramming all of that in a single SX device.  The SX/B source is over 30 pages long and the ASM files over 20 pages long.

I will probably need to split it up into modules based around 2 or more SX devices.

Hope that explains a few things !

Cheers
Tony

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


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=126329#m126666

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2006 (http://www.dotNetBB.com)