skytoastar

There are two, 8-pin headers on the 5110 boards. How far apart are those headers?

I saw this a few days ago on TI's site and finally bit the bullet. I have a Chronos watch that I want the full license for. But I love all the new dev boards that are coming out, too. I get that Pokemon feeling when I look through all the neat boards you can get for <$20 and all the cool boosterpacks. Gotta catch 'em all!

I'd like to incorporate an LCD into a project. How far apart are the headers? Based on my best measuring of the pixels in that layout image, I'd guess 1600 or 1550 mil but I'm not sure. @@RobG do you mind saying?

I've been reading of people having huge code size results from compiling with GCC vs pre-TI GCC. That motivates me to use TI's compiler. And it's just one of those things where I want to know, "Can I? Is it possible?" I started experimenting myself this past weekend with the Chronos code (removing the COFF-only Bluerobin code) but ran into some issues. So I tried making the blink example code into a library and linking it, just the make the problem simpler, and I ran into problems cross-linking (TI compiles the .lib, GCC links it into another project) (no problems with TI's linker). It had to do with undefined symbols in the lib file but I ran out of weekend to keep working on it. Time for me to start learning about .a, .obj, and .lib files more.

I tried my best Google here and at e2e with no luck. Perhaps my Google skills are weak, though. So I know the code size limit of the free license for CCS is 16k. But I don't understand how it calculates this. For example, the ez430-Chronos watch has a project that compiles using the free, limited license. It does this by linking some precompiled binary .lib files rather than compiling those fresh. So, first question, does it know those lib files were compiled using a non-free license? And how does it calculate that 16k? Because after the linker is done, the final binary is just under 32k though I know some of it was previously compiled. I assume it's only counting the newly compiled parts but I can't find a simple way to know how much that is. But could I just divide a project into mini-projects and then link them in to get around the code size limit? Second question, slaa664 says that GCC and TI's compiler are ABI compatible. Doesn't that mean I get the benefit of TI's compiler with no code size restriction by compiling with TI and linking with GCC? I haven't had a chance to try this but I was wondering if anyone else had or what everyone's thoughts are on this. I could imagine problems with debugging. Obviously COFF files would need migration. Thoughts?