Re: Re. Building a totally new smart phone
Adam Bogacki wrote: > Now that I have dir 'freecalypso-sw-SE52Fru5' I am not quite sure what > to do. > Is there some documentation available, or a man page ? No documentation has been written yet, because there is nothing to document yet: all that's there is a FreeNucleus RTOS skeleton and some host tools for pushing code images to the Calypso. See my earlier posts in this thread for my planned roadmap of adding "meat" to this skeleton. The FreeCalypso project is still in a very early stage - most projects aren't even announced at all when they are this early in the development process. The only reason why I'm releasing this code at all is to satisfy the moral requirement: on my planet it is a crime to have some ware and not share it, no matter what the ware is. If you want to play with the current code just for fun (there isn't anything more that you would be able to do with it), you should be able to at least compile it, and if you have one of the two supported phone models (DP-L10 or GTA02), even run it and see the serial output from the FreeNucleus demo app. The steps are: 1. Build and install the arm-elf cross-compile toolchain. Look in the toolchain directory and it should be obvious. 2. Using that toolchain, compile the target-utils part. (Just run make in the target-utils subdir with the toolchain in your PATH.) You'll get the loadagent.srec image. 3. Compile loadtools - again, just run make in the corresponding directory. These are host tools, so they need to run on whatever Unix/Linux machine you'll be using to push code to the Calypso. If you are doing this with a Pirelli phone, FreeCalypso loadtools need to run on your PC/desktop/laptop. If you are playing with a GTA02 instead, you will need to either make a special cable to get to the Calypso via the headphone jack, or build loadtools to run on the GTA02 AP. 4. Once you've got loadtools, loadagent.srec and a compatible Calypso phone, you can actually try running this stuff. If you have successfully passed steps 1 through 3, but are having difficulties with this step, ask and I'll help you. If you are still struggling with one of the previous steps, work on that first. A command like this (from a laptop with a Pirelli DP-L10 phone connected and showing up as /dev/ttyUSB0): fc-loadtool -h pirelli /dev/ttyUSB0 or like this (from the GTA02 AP, talking to the Calypso part of the same phone): fc-loadtool -h gta02 /dev/ttySAC0 should produce output that looks like this: Sending beacons to /dev/ttyUSB0 Got beacon response, attempting download The 3 lines beginning with "FreeCalypso loadagent running" will be printed by code running on the Calypso chip itself, which you would have built in step 2. Once you are at the loadtool prompt, you are interacting with the host utility you would have built in step 3, which is in turn communicating over a serial channel with loadagent.srec running on the Calypso. Loadtool has commands for things like peeking and poking registers, dumping and programming flash, etc. But right now the only documentation is the source code. Type exit, quit or ^D when you are done - it'll reboot the Pirelli phone or power off the GTA02 GSM modem. 5. The Nucleus-based skeleton for what is meant to become the main GSM firmware lives in the nuc-fw directory. You can build it as soon as you've got the arm-elf toolchain from step 1. Unlike loadagent, which is meant to remain "universal" for all Calypso phones (just like TI's FLUID), the main firmware obviously has to be configured for a specific target. The snapshot you are looking at has the beginnings of the configuration mechanism, but the latter doesn't do anything yet. For now all that's there is the Nucleus demo, and it happens to be the same for all phones, so just type make in the nuc-fw directory with the toolchain from step 1 in your PATH. You'll get ramImage.srec, which you can run on your Calypso phone with the fc-xram utility: fc-xram -h pirelli /dev/ttyUSB0 ramImage.srec If you are doing this with a Pirelli DP-L10, you should see the output from the demo app pouring on your terminal when you run the above command. Type ^\ to kill the fc-xram process on your host, but to stop the demo app running on the phone and make the phone usable again, you'll have to pull the battery and put it back in. (And then reset the clock, as this phone doesn't have a separate RTC backup battery.) If you are playing with a GTA02 instead, you can run the same ramImage.srec image, and you can push it with the same fc-xram command either from inside the phone (from the AP) or from an external host via that special headphone jack cable, but the demo app's output will always go to the IrDA UART (unless you change the code in demo.c), so you won't see anything unless you have that special serial cable. That's all that one can do with freecalypso-sw for now. My planned next step is to at
Re: Re. Building a totally new smart phone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 .. the ftp*bz2 link works and I have unpacked it. Now that I have dir 'freecalypso-sw-SE52Fru5' I am not quite sure what to do. Is there some documentation available, or a man page ? Searching by 'calypso' or 'freecalypso' did not show anything relevant when using 'www.deeperweb.com' Regards, Adam. On 24/08/13 13:28, Michael Spacefalcon wrote: > Adam Bogacki wrote: > >> I have not been able to find working links to freecalypso-sw anywhere. > > Not able to find *working* links? So the link I had posted earlier in > this thread: > > ftp://ftp.ifctf.org/pub/GSM/FreeCalypso/snapshots/freecalypso-sw-SE52Fru5.tar.bz2 > > is not working for you? > > There is also a Mercurial source repository where the development > takes place: > > https://bitbucket.org/falconian/freecalypso-sw > > But if it gets taken down because some suppressive person reports it, > don't blame me. Of course Mercurial is a distributed SCM just like > git, hence even if bitbucket.org takes it down, no source or history > will be lost - but it will make the project inaccessible to others > (except via the occasional snapshots which I post on my FTP site) > until we (the FreeCalypso community, currently consisting of one > developer and a few supporters watching from the sidelines) find a new > Hg webhost. > > VLR, > SF > > - -- Adam Bogacki adam.boga...@clear.net.nz http://www.independent.academia.edu/AdamBogacki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJSGBzLAAoJELXBCnrK+Nj6J8IH/2jz92N6LSLRGk/UNv9fxO/F BdSVqjfssAwGkRyP47B0lsgFjBBLS+1hDbR1egeBHhbjNkB2mz2JqC7Z7ysnzCTJ 7uZbt3ey0FFEAM5o/gr2KJRkBknqawdUC/yLgweX5mUTpbbjvwj3tBYYFK0eWV9h lOFtI3Lo1pAfuHIyzhe8ctTC8QCrKsHb5SRcKzOZ8x/qqf7Y+o8TBYcBIQRbcVqL oPUmTNxQzN3ZgJVA6zfhUdC3FGbiip6Ktv+2vLLjwEJ/hJabHK5oCwy5yKDtj5kI ERM2Hj2tWZPCIsNaukBMac5FIdDNcwtFBITsWletKLA3jo4/a0/mmdJgrXreE6Q= =6s6W -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re. Building a totally new smart phone
Adam Bogacki wrote: > I have not been able to find working links to freecalypso-sw anywhere. Not able to find *working* links? So the link I had posted earlier in this thread: ftp://ftp.ifctf.org/pub/GSM/FreeCalypso/snapshots/freecalypso-sw-SE52Fru5.tar.bz2 is not working for you? There is also a Mercurial source repository where the development takes place: https://bitbucket.org/falconian/freecalypso-sw But if it gets taken down because some suppressive person reports it, don't blame me. Of course Mercurial is a distributed SCM just like git, hence even if bitbucket.org takes it down, no source or history will be lost - but it will make the project inaccessible to others (except via the occasional snapshots which I post on my FTP site) until we (the FreeCalypso community, currently consisting of one developer and a few supporters watching from the sidelines) find a new Hg webhost. VLR, SF ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re. Building a totally new smart phone
On Sat 24 August 2013 02:04:45 Adam Bogacki wrote: > I would like to add my vote to the proposal of a totally new non-smart > phone. [...] > I think there is increasing demand for a secure non-smart phone. There IS NO secure phone! See any of the dozen other mails in this very thread about that topic. Or rather, there's not even any insecure phone - means you can't make it more secure by reviewing the firmware of the modem, since there IS NOTHING insecure in the firmware. It's not like you could kick out any rogue hidden backdoors since there aren't any, I won't elaborate again why that's evident. There are also no flaws in any security related encryptions or whatever that you could fix in the phone firmware, since those flaws (if any relevant) exist in the protocol spec and you need to fix both ends, mobile and BTS. And this still leaves all the other vulnerabilities of all public networks which always allow eavesdropping on a multitude of levels not under the control of the phone's firmware. Increasing demand for secure phone? I offer the only solution: adjust your habits, improve your knowledge. The phone is as secure as the user who operates it. /j -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments (alas the above page got scrapped due to resignation(!!), so here some supplementary links:) http://www.georgedillon.com/web/html_email_is_evil.shtml http://www.nonhtmlmail.org/campaign.html http://www.georgedillon.com/web/html_email_is_evil_still.shtml http://www.gerstbach.at/2004/ascii/ (German) signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re. Building a totally new smart phone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would like to add my vote to the proposal of a totally new non-smart phone. A recent article in 'The Futurist' has flagged the demise of the current model of the 'smartphone' in favour of less intrusive devices such as glasses and watches. http://www.wfs.org/futurist/2013-issues-futurist/september-october-2013-vol-47-no-5/top-10-disappearing-futures/disap-7 I have not been able to find working links to freecalypso-sw anywhere. http://en.wikipedia.org/wiki/Calypso_Technology I think there is increasing demand for a secure non-smart phone. Good luck, Adam. - -- Adam Bogacki adam.boga...@clear.net.nz http://www.independent.academia.edu/AdamBogacki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJSF/iOAAoJELXBCnrK+Nj6ViAH/3Cu4kB1DBunLIL82JCwhRoi KGXPrK6+ycIl6ime6wFkZdm5A3kSJgV1ZRkYKcbhcWbEFYb913tcgDFCqJlUUWd7 tmjXffh1K6ueXV70blSUHhakHp/LMy9vx27Pn/wmNOr79UauqAvKTrCJqY2v88QR nVNpwIlSDk5lIVe0PUgeMFi8e4JhTicsxSrAI7/2h18MwQmEKmk4qbs7wERcCVCa GeSMoDQgxgiS8D3lTJVuHBKJr2H3v8BbLL+jhB+V4BzVeQ80actmua/O2KAUEOjz R0RIcgo+DQvRZbcGlnT1VtxAjMjqt/jEv9FdmBnhRDPmINbJCsgQdj6CtMGYQEs= =QVKc -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
