Jump to content

skytoastar

Members
  • Content Count

    5
  • Joined

  • Last visited


Reputation Activity

  1. Like
    skytoastar got a reaction from spirilis in CCS for $9.99   
    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!
  2. Like
    skytoastar got a reaction from agaelema in CCS for $9.99   
    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!
  3. Like
    skytoastar got a reaction from tripwire in Linkers, GCC, and Code Size Limits   
    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?
×
×
  • Create New...