On Mon, May 30, 2011 at 1:22 AM, Sylvain Munaut <246tnt(a)gmail.com> wrote: Oh... I thought that firmware on ARM was communicating with DSP via AT messages... How does it control DSP then? I see that data is exchanged via shared memory in SRAM, but how does Calypso call DSP interface to do some processing ? I agree with you, but imagine someone who is looking around from the distance at one very interesting project. Fistly, I am not network stack engineer, but more attracted by the platform and system. But I'd like to get my feet wet, and not ready to throw 1k eur on the equipment I do not know at all. I'd rather try things around, get a feel and then, as I get involved, collect some material. You might disagree with me, but I think that for open source projects related to HW price is very important - keeping the price very low helps more people get involved in the project in the first place. Here, I ended up with telephone that can not do practicaly anything - can not receive nor transmit packets. Or am I wrong ? Can I use some data from public network, just to see some packets flow, so I can at least get some feel ? This does not surprise me much, world is full of morons. On the other side of the planet someone is litteraly dying for this $5. I can agree on this, it is not so expensive. But I explained position, so at this moment I am reconsidering solutions. When you say SW, I guess you mean some host applications ? What I was talking about is available HDL code that I can flash into my (eventually modified) FPGA board. I would more opt for idea of open source VHDL or Verilog code that can be flashed into non-expensive FPGA development boards (some Spartan or Altera or something) and open source schematics for additional hardware that can be soldered around to have signals coming. At this point I am not interested at full-blown BTS, but some minimal stuff that can send something via radio link that would be captured by the phone and transmitted via stack towards Wireshark on the host. Just the basic test. I do not need it for GSM protocol reserach, rather something that can give feel and usability to the OsmocomBB project, before someone has enough informations and idea to buy USRP. BR, Drasko

On Mon, May 30, 2011 at 2:02 AM, <246tnt(a)gmail.com> wrote: There is no need to take this personally, it was not my intention to sound too rude. It was more ironic social-awareness critic then an insult. Sorry if that offended you. In any case, I'd like to keep this interesting discussion strictly technical from now on, as I am sure that many people might benefit from it. Taken in a count that majority of engineers who are willing to contribute their time and knowledge to this project have probably mid-level expertise, with few real experts orbiting around and sharing the knowledge and support, paving the way for the newcomers. That's why I think that discussion I started makes sense and can be beneficial to all who have some general embedded engineering experience (in which I count myself) and are looking for a best way to contribute it to OsmocomBB and the community. I hope that you will share your valuable experience in this effort. I am aware of your work and I know that it is highly appreciated in the community. Thank you for your help and support. Best regards, Drasko

On Mon, May 30, 2011 at 8:56 AM, <weberbe(a)ee.ethz.ch> wrote: Yes, I think it would be a great start ! How this can be done ? Can somebody kindly explain the procedure to do this in a few words, and point out things to observe ? I think this kind of instructions/tutorial can be very useful for all the people who want to start quickly with OsmocomBB and have something useful that does communication and traverse packets through the stack. This employs all the tools from the project and gives perfect overview how they work together. Thanks and best regards, Drasko

On Mon, May 30, 2011 at 6:46 PM, Gianni Tedesco <gianni(a)scaramanga.co.uk> wrote: Hi Gianni, I did not saw it last night when I was srtawling through the wiki (or more possible did not understand that I was looking at it). Can you please post the link for the future reference ? BR, Drasko

On Tue, 2011-05-31 at 00:05 +0200, Drasko DRASKOVIC wrote: Pretty much, but also look at the page for your specific phone model and http://bb.osmocom.org/trac/wiki/osmocon Basically you just need to use osmocon to load the layer1 firmware, power the phone up and then if 'mobile' (or whatever app you want) is running, it should be "all systems go". You can run mobile/cell_log/whatever before or after booting the phone and it'll be fine. It's not a complicated scenario and is well explained on the wiki: We have a firmware for the phone that we compiled on the PC We have a data cable between phone and PC The firmware does low level things Other apps running on the PC do high level things (eg. mobile phone) We use a loader program (osmocon) to load the firmware from the PC on to the phone via the cable. After the firmware is running on the phone, we can run high level apps on the PC (mobile, cell_log, etc). The high level apps communicate to the phone via the communication channel setup by the loader. Most (all?) of the high level apps have a command line switch which tells them to transmit GSMTAP logs to a specific IP address. You can use tcpdump to capture the GSMTAP info and view it in wireshark. Gianni

On Tue, 2011-05-31 at 00:31 +0200, Drasko DRASKOVIC wrote: Sure. Although it is a goal of the project to bring awareness, knowledge, access to GSM to a wider audience, osmocom is still highly experimental software and that means that to do anything useful with it you are going to need to be very comfortable with figuring out these sorts of issues anyway. I mean, at this stage it's still very much for hackers who are ready to roll their sleeves up and get stuck in. I must say, I didn't even know of sylvains driver (non obvious branch name) or cell_log and had to write my own SIM access code to get going - it was a fun night :) Gianni

On Thu, 2011-06-02 at 01:22 +0200, Drasko DRASKOVIC wrote: It's all on the mailing list and recent. Although I think Nico Golde's SAP driver is the way this is going to go. So if you need SIM and don't want to use the phone SIM, try that. Gianni

On Mon, May 30, 2011 at 8:56 AM, <weberbe(a)ee.ethz.ch> wrote: Hi weberbe, can you explain in some more details how this can be done ? So far I did not succeed to attach to any cell, not to get some packets from it. At which moment can we observe the packets which are coming : 1) During the initial measurements or 2) Only after we attach to a cell What should be set up, what applications run and in which order to obtain some packet logging in Wireshark. I am running master branch - so, no SIM working. Best regards, Drasko