From laforge at gnumonks.org Thu Oct 13 07:09:21 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 13 Oct 2016 09:09:21 +0200 Subject: nuttx-bb layout? inside or outside nuttx? In-Reply-To: <2117200564.394691.1474810375659@mail.yahoo.com> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160924123159.sdqpnz5yksr6njcr@nataraja> <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> <2117200564.394691.1474810375659@mail.yahoo.com> Message-ID: <20161013070921.p76bbpfw5jwjzv6l@nataraja> Hi Craig, this is just a small note that I just met Marcin Mielczarczyk (who did the existing but still incomplete MTK support work a few years back) at Embedded Linux Conf Europe, and informed him about your work. It is really exciting for both of us to see somebody picking this up and trying to bring things together. If I'm not mistaken, you basically have the following agenda: * Structure OsmocomBB in a way that it can be built 'side-by-side into Nuttx * Build /integrate it from the fernvale nuttx port that is available * Implement the bulk of the MTK L1 integration, i.e. the interface to the DSP. And afterwards hope that you have something that supports either the Fernvale, SIM800H, Linkit One, or other MTK 2G baseband chips out there. Please let me know this was an accurate understanding. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From craig_comstock at yahoo.com Thu Oct 13 10:56:35 2016 From: craig_comstock at yahoo.com (Craig Comstock) Date: Thu, 13 Oct 2016 10:56:35 +0000 (UTC) Subject: nuttx-bb layout? inside or outside nuttx? References: <1792646760.58493.1476356195912.ref@mail.yahoo.com> Message-ID: <1792646760.58493.1476356195912@mail.yahoo.com> Yes, my plan was: - get osmocom-bb (layer1/rssi) firmware working (without graphics probably) - use that work side-by-side to integrate into fernvale nuttx - create a layer1 "app" in nuttx - port "mobile" app to nuttx With the goal being that you can call/text from the nuttx shell. I have the following hardware with which to experiment: - c139 motorola phones - pirelli phone - a few other calypso phones - seeedstudio rephone (mtk6261) - sim800 of various types - several watch phones (dz09 gt08 v9, both 6260 and 6261) - raw 6260 chips which I hope to design a custom pcb for My end goal which is far too ambitious is to make a rock-like device which has no ports/holes: - bluetooth serial to nuttx shell - qi wireless charging - accelerometer gestures for basic controls - bone conducting speaker - speech synth (sam/espeak) and voice recognition (pocketsphinx) - all source is included on-device, even to the point that I would like to port all this work to a forth-like language of my own invention so you can debug, learn and experiment on the device I have so far fixed up the existing mtk-firmware target and was debating whether to submit that small patch or wait until I get some 626x work done. On that front I have the basic registers and an initial BSI power on routine written (but not tested). Thanks to all the giants upon whose shoulders I stand to do this work, Craig -------------------------------------------- On Thu, 10/13/16, Harald Welte wrote: Subject: Re: nuttx-bb layout? inside or outside nuttx? To: "Craig Comstock" Cc: "Marcin Mielczarczyk" , "baseband-devel" Date: Thursday, October 13, 2016, 2:09 AM Hi Craig, this is just a small note that I just met Marcin Mielczarczyk (who did the existing but still incomplete MTK support work a few years back) at Embedded Linux Conf Europe, and informed him about your work. It is really exciting for both of us to see somebody picking this up and trying to bring things together. If I'm not mistaken, you basically have the following agenda: * Structure OsmocomBB in a way that it can be built 'side-by-side into Nuttx * Build /integrate it from the fernvale nuttx port that is available * Implement the bulk of the MTK L1 integration, i.e. the interface to ? the DSP. And afterwards hope that you have something that supports either the Fernvale, SIM800H, Linkit One, or other MTK 2G baseband chips out there. Please let me know this was an accurate understanding. Regards, ??? Harald -- - Harald Welte ? ? ? ? ???http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? (ETSI EN 300 175-7 Ch. A6) From craig at unreasonablefarm.org Sat Oct 15 04:26:56 2016 From: craig at unreasonablefarm.org (Craig Comstock) Date: Fri, 14 Oct 2016 23:26:56 -0500 Subject: [PATCH] adjust Makefile.mtk so that mtk-firmware works again Message-ID: <1476505616-21599-1-git-send-email-craig@unreasonablefarm.org> --- src/target/firmware/Makefile.mtk | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/target/firmware/Makefile.mtk b/src/target/firmware/Makefile.mtk index 30fa2fc..927e31a 100644 --- a/src/target/firmware/Makefile.mtk +++ b/src/target/firmware/Makefile.mtk @@ -4,14 +4,16 @@ BOARDS?=mt62xx # List of all applications (meant to be overridden on command line) APPLICATIONS?=loader_mtk -mtkram_LDS=board/mediatek/ram.lds -mtkram_OBJS=board/mediatek/start.ram.o +APP_loader_mtk_ENVIRONMENTS=mtkram + +ENV_mtkram_LDS=board/mediatek/ram.lds +ENV_mtkram_OBJS=board/mediatek/start.ram.o mtk_COMMON_OBJS=board/mediatek/uart.o # Mediatek MT62xx -mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o -mt62xx_ENVIRONMENTS=mtkram +BOARD_mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o +BOARD_mt62xx_ENVIRONMENTS=mtkram # Global include path INCLUDES=-Iinclude/ -I../../../include -I../../shared/libosmocore/include -- 2.1.4 From mychaela.falconia at gmail.com Mon Oct 17 19:07:26 2016 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Mon, 17 Oct 2016 11:07:26 -0800 Subject: Solution to the shortage of Calypso devices Message-ID: Hello baseband hacking folks, I have heard several people complain that they are no longer able to find/obtain a Motorola C1xx phone or any other Calypso device for playing with OsmocomBB. I assume these complaints probably come from people in the EU and other 900/1800 MHz regions, as US band C139 phones are still readily available on ebay (63 listings as of right now, all dirt cheap), but either way, I have what I believe to be the proper solution to the shortage and the crippled nature of all pre-existing Calypso devices: a new Calypso board. Back in 2012 Harald Welte posted here saying that his company was going to be making a new Calypso board for the very same purpose of addressing the shortage and the deficiencies of pre-existing devices, but as far as I know, no such product has ever been produced - nor do I know if whoever was behind that project even got as far as creating the design for it. Fast-forwarding to the present, we now have a ready-to-build design for a Calypso development board called FCDEV3B, which stands for FreeCalypso development board, triband. It is based on a reuse of the known-working Calypso modem design from Openmoko, reuse at the level of physical PCB layout, based on the GTA02 design files which Openmoko founder Mr. Sean Moss-Pultz released in April of 2015 at my urging. Back in 2012 Harald was saying that he was only going to release PDF schematics but not the full design files for his board; I feel differently about such matters, hence the complete design files for *my* board are free to the world: ftp://ftp.freecalypso.org/pub/GSM/FreeCalypso/fcdev3b/ Now we need to get these boards physically made, and toward that end I have started a crowdfunding campaign: https://www.gofundme.com/fcdev3b-board-production-2umevjw In the interest of transparency, I have to disclose (most people know it already, but I have to state it anyway) that I do not use OsmocomBB and will never contribute to Osmocom software because I am working on my own personally preferred alternative GSM MS firmware implementation, but when it comes to the hardware I seek to build and offer to the community, there is no reason why it won't work with OsmocomBB - it should work just fine. Because my board is a derivative of Openmoko's modem design and the part that is different between Openmoko's board and mine (the flash chip - I will populate a higher-capacity chip on the same footprint) is not used by OsmocomBB software, the images currently built in board/gta0x/*.highram.bin should work as-is on my FCDEV3B without needing any code changes. Hasta la Victoria, Siempre, M~ From laforge at gnumonks.org Wed Oct 19 20:19:31 2016 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 19 Oct 2016 22:19:31 +0200 Subject: Solution to the shortage of Calypso devices In-Reply-To: References: Message-ID: <20161019201931.4fwsxeme7nnx2c4e@nataraja> Hi Mychaela, On Mon, Oct 17, 2016 at 11:07:26AM -0800, Mychaela Falconia wrote: > I believe to be the proper solution to the shortage and the crippled > nature of all pre-existing Calypso devices: a new Calypso board. To be fair: It is *a* solution, unfortunately not one accessible to all people. The price of the C1xx phones at the height of their availability some 5 years ago was in the range of 10-20 USD, which is something never achievable with any new board if not only due to the economics of scale. > Back in 2012 Harald Welte posted here saying that his company was > going to be making a new Calypso board for the very same purpose of > addressing the shortage and the deficiencies of pre-existing devices, I will re-read the mails, but as far as I remember it, there was some intention and some plans, but I do not recall having made a firm committment that we definitely will do it. As usual, life happens and there are many other interesting projects to work on. I personally and "my" company have been working ever since to create more and more FOSS for cellular communications - with a focus on the network / infrastructure side. > but as far as I know, no such product has ever been produced - nor do > I know if whoever was behind that project even got as far as creating > the design for it. I know of one company who has created a proprietary calypso-based design (not for public sale), but neither I nor sysmocom were involved in that. > Fast-forwarding to the present, we now have a ready-to-build design > for a Calypso development board called FCDEV3B, which stands for > FreeCalypso development board, triband. This is great news. I have been occasionally following your efforts, and it is great to see those efforts culminating at this point. > Back in 2012 Harald was saying that he was only going to release PDF > schematics but not the full design files for his board; I feel > differently about such matters, This is a misrepresentation. I do not "feel" differently. The point was simply that at that time, Openmoko Inc still existed, and there was confidentiality on the GSM modem part of the GTA01/GTA02 phone designs. So I simply didn't have any authority to decide on that, no matter wat my feelings were. It's great that you got permission to disclose that layout - three years later. > Now we need to get these boards physically made, and toward that end I > have started a crowdfunding campaign: > > https://www.gofundme.com/fcdev3b-board-production-2umevjw Great! I have pitched USD 450 in to see how this bord turns out in reality. I think it should be relatively easy to get 9 more people chip in to turn this into realaity. We also still have 100 units of calypso, iota and rita chips in stock at sysmocom, which we'd happily donate to your project if you were interested. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From mychaela.falconia at gmail.com Wed Oct 19 22:10:11 2016 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Wed, 19 Oct 2016 14:10:11 -0800 Subject: Solution to the shortage of Calypso devices In-Reply-To: <20161019201931.4fwsxeme7nnx2c4e@nataraja> References: <20161019201931.4fwsxeme7nnx2c4e@nataraja> Message-ID: Hi Harald, > To be fair: It is *a* solution, unfortunately not one accessible to all > people. The price of the C1xx phones at the height of their > availability some 5 years ago was in the range of 10-20 USD, Actually the US band C139s are *still* available at these prices on ebay today; dunno about EU band ones though. My personal reasons for seeking to build my own FreeCalypso board have more to do with these phones' extremely crippled nature, rather than their shortage. My FreeCalypso software puts more demands on its underlying hw target than OsmocomBB, and a C1xx phone can never be a fully satisfactory replacement for Openmoko's modem for FreeCalypso purposes. I want a hardware platform on which my FreeCalypso work can shine at its full brightness, hence FreeCalypso hardware. But I also heard many complaints from people who said they could NOT get a Mot C1xx phone for the purpose of playing with OsmocomBB, thus I thought that perhaps my board project could benefit not only the FC community, but OsmocomBB as well. > which is > something never achievable with any new board if not only due to the > economics of scale. Absolutely true. > I will re-read the mails, but as far as I remember it, there was some > intention and some plans, but I do not recall having made a firm > committment that we definitely will do it. I don't think I said that you made a firm commitment, but the announcement of those plans on this list did generate a lot of excitement and interest. > As usual, life happens and > there are many other interesting projects to work on. I have Asperger Syndrome, which causes me to remain focused on one single project for years on end. But I do realize that most "normal" people don't have the same kind of single-minded focus. > I personally and > "my" company have been working ever since to create more and more FOSS > for cellular communications - with a focus on the network / > infrastructure side. I very much appreciate your work on the network / infrastructure side, as I suspect that it may become vital when the greedy uncaring major network operators shut down their GSM/2G services. When that happens, those of us who absolutely require GSM/2G in order to live happy and meaningful lives will have to set up our own networks, and that is where your work on that side will come in very handy. > I know of one company who has created a proprietary calypso-based > design (not for public sale), but neither I nor sysmocom were involved > in that. I know (or I should say suspect) at least two, one of which is likely the same one you know of. They contacted me asking if I could make AMR work for them in OsmocomBB, with the uplink TCH/AFS (or TCH/AHS perhaps) bits coming from their external host instead of the microphone-fed internal vocoder, and I told them that (1) I only work on FreeCalypso sw and not OsmocomBB, and (2) I don't know if what they wanted is even possible without *Massive* DSP reverse eng work to produce a special DSP patch, so that was the end of the story. But they did mention to me that they had their own Calypso board, although I have no idea how it differs from mine or from a C1xx phone. The other company which I suspect is also building their own Calypso- based hardware for use inside their closed world and not for the general public is the anonymous company who did the FCDEV3B PCB design in Altium - they did this work for me on a barter basis in exchange for some consulting work I did for them, which consisted of extensive hand-holding help with FreeCalypso sw on GTA02 devices - apparently they are building something GTA02-based, but I can only guess, and your guess would be as good as mine. They are anonymous in that I myself don't know who they are - they never told me. > This is a misrepresentation. I do not "feel" differently. The point > was simply that at that time, Openmoko Inc still existed, and there > was confidentiality on the GSM modem part of the GTA01/GTA02 phone > designs. So I simply didn't have any authority to decide on that, no > matter wat my feelings were. Well, Prometheus did not have any authority from Zeus to give Fire to Humankind either, but he did it anyway. Every time you cook something on a fire or warm your house with one, say thanks to the greatest NDA breaker of all times! > Great! I have pitched USD 450 in to see how this bord turns out in > reality. I've already sent you an off-list thank-you note, but here I reiterate my thanks for your donation publicly! > I think it should be relatively easy to get 9 more people > chip in to turn this into realaity. I hope so... > We also still have 100 units of calypso, iota and rita chips in stock at > sysmocom, The exact same number I have in my own stash - what a coincidence. :) > which we'd happily donate to your project if you were > interested. Thanks, I'll keep you in mind if my own stash ever proves insufficient and I have difficulty getting more from the Chinese market. M~ From robert.steve07 at gmail.com Tue Oct 25 07:51:18 2016 From: robert.steve07 at gmail.com (robert) Date: Tue, 25 Oct 2016 10:51:18 +0300 Subject: omsocombb not receiving calls In-Reply-To: <20160321095208.GH10371@nataraja> References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> Message-ID: <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> Hi, Is it possible to have two or more timeslots receiving at the same time. It is necessary to have timeslot 0 at all time and another timeslot for paging. Best regards, On Mar 21, 2016, at 11:52 AM, Harald Welte wrote: > Hi robert, > > On Mon, Mar 21, 2016 at 11:43:20AM +0200, robert wrote: >> I can?t figure out a way to dynamically set the time slot, I?m always >> getting errors during compilation. When I solve these errors I will >> give you some feedback about any progress. > > Feel free to post your patches + error messages here. > > The below patch doens't work for you? > > diff --git a/src/target/firmware/layer1/prim_rx_nb.c b/src/target/firmware/layer1/prim_rx_nb.c > index 38c7b53..d186bff 100644 > --- a/src/target/firmware/layer1/prim_rx_nb.c > +++ b/src/target/firmware/layer1/prim_rx_nb.c > @@ -204,7 +204,7 @@ static int l1s_nb_cmd(__unused uint8_t p1, uint8_t burst_id, > burst_id, tsc > ); > > - l1s_rx_win_ctrl(arfcn, L1_RXWIN_NB, 0); > + l1s_rx_win_ctrl(arfcn, L1_RXWIN_NB, tn); > > return 0; > } > -- > - Harald Welte http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) From 246tnt at gmail.com Tue Oct 25 08:35:57 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 25 Oct 2016 10:35:57 +0200 Subject: omsocombb not receiving calls In-Reply-To: <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> Message-ID: Hi, > Is it possible to have two or more timeslots receiving at the same time. It is necessary to have timeslot 0 at all time and another timeslot for paging. Can the hw do it : yes Can the software do it : no. Is it really necessary: no it's not. For each frame you'll need either ts0 or tsX but not both at once in the same frame. Cheers, Sylvain From robert.steve07 at gmail.com Tue Oct 25 08:42:56 2016 From: robert.steve07 at gmail.com (robert) Date: Tue, 25 Oct 2016 11:42:56 +0300 Subject: omsocombb not receiving calls In-Reply-To: References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> Message-ID: <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> Hi Sylvain, Thanks for explaining. I couldn?t find a way to decide which ts to choose so I thought about having multiple ts at the same time. So I understand that I should stick with only one ts. Best regards, On Oct 25, 2016, at 11:35 AM, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > >> Is it possible to have two or more timeslots receiving at the same time. It is necessary to have timeslot 0 at all time and another timeslot for paging. > > Can the hw do it : yes > > Can the software do it : no. > Is it really necessary: no it's not. For each frame you'll need either > ts0 or tsX but not both at once in the same frame. > > Cheers, > > Sylvain From 246tnt at gmail.com Wed Oct 26 05:10:58 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 26 Oct 2016 07:10:58 +0200 Subject: omsocombb not receiving calls In-Reply-To: <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> Message-ID: > Thanks for explaining. I couldn?t find a way to decide which ts to choose so I thought about having multiple ts at the same time. > So I understand that I should stick with only one ts. Which TS to listen on for paging message will be dependent on the paging group your sim card is in. It's a formula that's based on your IMSI and the cell configuration. It's described somewhere in the spec, GSM 04.08 should have at least reference to it if you search for "paging group". Curently we don't support configs that have a CCCH on any other ts than 0. Cheers, Sylvain From robert.steve07 at gmail.com Wed Oct 26 06:39:14 2016 From: robert.steve07 at gmail.com (robert) Date: Wed, 26 Oct 2016 09:39:14 +0300 Subject: omsocombb not receiving calls In-Reply-To: References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> Message-ID: <8B091653-55DF-49EF-8FC7-394CD6C7EB7F@gmail.com> Hi, On Oct 26, 2016, at 8:10 AM, Sylvain Munaut <246tnt at gmail.com> wrote: >> Thanks for explaining. I couldn?t find a way to decide which ts to choose so I thought about having multiple ts at the same time. >> So I understand that I should stick with only one ts. > > Which TS to listen on for paging message will be dependent on the > paging group your sim card is in. It's a formula that's based on your > IMSI and the cell configuration. It's described somewhere in the spec, > GSM 04.08 should have at least reference to it if you search for > "paging group?. > Yes I understand, my problem is in modifying the osmocombb code so that it listens to other TS. I have tried to change the code to make it work but with no success. I only need some instructions on where to start and what should be done. Best regards, From domi at tomcsanyi.net Wed Oct 26 07:07:24 2016 From: domi at tomcsanyi.net (=?utf-8?B?VG9tY3PDoW55aSwgRG9tb25rb3M=?=) Date: Wed, 26 Oct 2016 09:07:24 +0200 (CEST) Subject: omsocombb not receiving calls In-Reply-To: <8B091653-55DF-49EF-8FC7-394CD6C7EB7F@gmail.com> References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> <8B091653-55DF-49EF-8FC7-394CD6C7EB7F@gmail.com> Message-ID: As far as I remember the calypso-trx code was capable of receiving multiple timeslots, maybe check out that code (jolly/trx if I'm right) and watch Sylvain's talk about it. https://youtu.be/B1od4x9L3t4 Cheers, Domi 2016. okt. 26. d?tummal, 8:40 id?pontban robert ?rta: > Hi, > > On Oct 26, 2016, at 8:10 AM, Sylvain Munaut <246tnt at gmail.com> wrote: > >>> Thanks for explaining. I couldn?t find a way to decide which ts to choose so I thought about having multiple ts at the same time. >>> So I understand that I should stick with only one ts. >> >> Which TS to listen on for paging message will be dependent on the >> paging group your sim card is in. It's a formula that's based on your >> IMSI and the cell configuration. It's described somewhere in the spec, >> GSM 04.08 should have at least reference to it if you search for >> "paging group?. >> > Yes I understand, my problem is in modifying the osmocombb code so that it listens to other TS. I have tried to change the code to make it work but with no success. I only need some instructions on where to start and what should be done. > > Best regards, > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Wed Oct 26 07:32:38 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 26 Oct 2016 09:32:38 +0200 Subject: omsocombb not receiving calls In-Reply-To: References: <56D9C251.8050908@googlemail.com> <5AF0C357-BCC3-4DD0-BE74-6E6E61F29EDE@gmail.com> <9B8058DF-95F4-4B76-AB29-FA8CB86DD3C7@gmail.com> <20160316140643.GA8342@nataraja> <4AD5A12F-4A49-4386-AED4-D52383C48B76@gmail.com> <20160316145002.GC8342@nataraja> <35A2C529-22EE-483E-94CF-D9DB961F7F18@gmail.com> <20160321095208.GH10371@nataraja> <388DD99E-AB05-4174-A457-BEEBB616934C@gmail.com> <06448C87-6E13-438A-85C9-D5ADD69A3E31@gmail.com> <8B091653-55DF-49EF-8FC7-394CD6C7EB7F@gmail.com> Message-ID: On Wed, Oct 26, 2016 at 9:07 AM, Tomcs?nyi, Domonkos wrote: > As far as I remember the calypso-trx code was capable of receiving multiple > timeslots, maybe check out that code (jolly/trx if I'm right) and watch > Sylvain's talk about it. > https://youtu.be/B1od4x9L3t4 That's only to act as a BTS. This screws with the DSP code and breaks all normal phone code function. You loose all the channel coding/decoding with this and have to do all that on the host. Cheers, Sylvain