FreeCalypso > hg > freecalypso-sw
comparison gsm-fw/L1/stand/README @ 613:9e605ec89ed0
gsm-fw/L1/stand: starting work on our version of standalone L1
| author | Michael Spacefalcon <msokolov@ivan.Harhan.ORG> |
|---|---|
| date | Fri, 29 Aug 2014 17:25:46 +0000 |
| parents | |
| children | 4d40f9a99445 |
comparison
equal
deleted
inserted
replaced
| 612:700d450bb8da | 613:9e605ec89ed0 |
|---|---|
| 1 In their internal development environment, TI had a way to build L1 standalone, | |
| 2 i.e., omitting the G23 protocol stack and other large and complex pieces of the | |
| 3 full firmware. Such an ability is essential for sane development, and the | |
| 4 abundant references to OP_L1_STANDALONE throughout the codebase confirm that TI | |
| 5 had it indeed. | |
| 6 | |
| 7 However, we (FreeCalypso) don't have a way to build an OP_L1_STANDALONE image | |
| 8 exactly the way TI did it - we don't have all of the necessary source - the | |
| 9 glue pieces specific to this configuration are missing. Nor do we necessarily | |
| 10 need to imitate what TI did in this department: it appears that TI's standalone | |
| 11 L1 build omitted GPF (with the exception of OS and OSX) and everything that | |
| 12 lives in Riviera land, but for us the situation is different: we already have | |
| 13 a successful build with Riviera and GPF, but no L1, thus we simply need to add | |
| 14 L1 to what we have. Our idea of standalone L1 simply means building without | |
| 15 the G23 stack, which we have yet to begin integrating. | |
| 16 | |
| 17 In the standard firmware build, there is a component called L1 PEI. It is part | |
| 18 of the G23 stack, and has header and library dependencies of the latter - thus | |
| 19 it is *not* part of the L1 code proper. However, it performs some essential | |
| 20 initialization steps, and runs the L1A task. We don't know how TI handled | |
| 21 these functions in their standalone L1 build - we don't have that part of their | |
| 22 source, not even in the otherwise complete LoCosto version, not even if we were | |
| 23 targeting LoCosto hardware. | |
| 24 | |
| 25 Our solution: we are going to lift l1_pei out of LoCosto's g23m-gsm, and hack | |
| 26 up a special version of it that won't have the standard complement of G23 | |
| 27 header and library dependencies. It is virtually certain that TI did something | |
| 28 different, but our hack-solution should work for our needs. | |
| 29 | |
| 30 Because our standalone L1 build is a specially stripped-down version of the | |
| 31 regular fw build, and not at all like TI's standalone L1, we do NOT define | |
| 32 OP_L1_STANDALONE. Instead we have a different preprocessor symbol: | |
| 33 CONFIG_L1_STANDALONE. |