FreeCalypso > hg > freecalypso-sw
comparison doc/Freerunner-Howto @ 864:4fa939eada22
documentation update: how to compile and flash experimental gsm-fw for gtamodem
| author | Space Falcon <falcon@ivan.Harhan.ORG> |
|---|---|
| date | Sun, 10 May 2015 19:35:29 +0000 |
| parents | |
| children | 7d3f0910aeb2 |
comparison
equal
deleted
inserted
replaced
| 863:78c894c7c471 | 864:4fa939eada22 |
|---|---|
| 1 How to play with FreeCalypso GSM firmware on a Neo Freerunner | |
| 2 ============================================================= | |
| 3 | |
| 4 Aside from the half-source leo2moko fw we produced back in 2013-10 (you can | |
| 5 read all about that one at www.freecalypso.org/leo2moko/), we don't have a | |
| 6 working free GSM firmware version for the Freerunner yet. What we do have | |
| 7 currently is experimental code that can be built into an image that can be | |
| 8 flashed into a GTA02 modem - but it doesn't really work yet. | |
| 9 | |
| 10 If you would like to play with our experimental code on your Neo FR and maybe | |
| 11 help us make it work, here are the instructions: | |
| 12 | |
| 13 1. Build the firmware in the gtamodem-gsm configuration - see the Compiling | |
| 14 document for more details; | |
| 15 | |
| 16 2. You should get a flashImage.bin image built; now you need to flash it into | |
| 17 your FR's modem. The serial cable method is highly recommended: the only | |
| 18 thing you'll be able to do with our current non-working firmware is help us | |
| 19 debug it, and the serial cable will be needed for the latter part anyway. | |
| 20 | |
| 21 3. Run fc-loadtool the same way you would if you were flashing leo2moko; | |
| 22 | |
| 23 4. The actual flash programming commands are a little different because the | |
| 24 image is smaller and in a different format: | |
| 25 | |
| 26 flash erase 0 0x160000 | |
| 27 flash program-bin 0 finlink/flashImage.bin | |
| 28 | |
| 29 The second number in the flash erase command needs to be the size of | |
| 30 flashImage.bin rounded up to a multiple of 64 KiB (the flash sector size in the | |
| 31 GTA02 modem); 0x160000 is correct for the fw image size as of this writing, but | |
| 32 please double-check it yourself before flashing. The 0 argument in the | |
| 33 flash program-bin command is the flash offset at which the image should be | |
| 34 programmed: it will always be 0 for FreeCalypso flashable fw images for gtamodem | |
| 35 and other targets that have the Calypso boot ROM enabled in the hardware. | |
| 36 | |
| 37 Once you have flashed our experimental fw into your modem, you can power-cycle | |
| 38 the modem and see the new fw boot. You should have the serial cable connected, | |
| 39 the serial channel enabled from the Freerunner's AP side and either rvtdump or | |
| 40 rvinterf running on your PC or other development machine when you first power | |
| 41 your modem up with the experimental fw in it: this way you will see whether the | |
| 42 fw boots successfully or crashes. If it does boot without crashing (whether or | |
| 43 not it does seems to depend on some factors which we have yet to understand), | |
| 44 you will get an AT command interface on the other UART going to the Freerunner's | |
| 45 AP - now go ahead and play from there. :) | |
| 46 | |
| 47 To reflash your modem back to stable and working leo2moko aka moko12, execute | |
| 48 the following fc-loadtool commands: | |
| 49 | |
| 50 flash erase 0 0x230000 | |
| 51 flash program-m0 leo2moko.m0 | |
| 52 | |
| 53 (Whichever firmware image you are flashing, the flash erase command needs to | |
| 54 cover the range of flash sectors this image will occupy. You can erase more | |
| 55 sectors up to 0x300000, the "natural" boundary of the flash area where fw | |
| 56 images live, but I prefer to erase only the needed number of sectors: it is | |
| 57 both faster and imposes less wear on the flash.) |