baseband-devel July 2012

baseband-devel@lists.osmocom.org

41 participants
57 discussions

Custom calypso board
by Harald Welte 18 Aug '12

18 Aug '12

Hi all! There are some signs that the supply of Motola C1xx phones is not endless, after all. As such, sysmocom has decided to manufacture some custom boards with the typical TI Calypso/Iota/Rita design. The RF PA will be RFMD RF3166, and the combined NOR + SRAM will be a Samsung K5A3281. All parts are still available from the surplus market. Schematics will be published in PDF form only, Gerber/PCB files will not be released (so basically the same like the OsmoSDR situation). All software used is already available as OsmocomBB under a *GPL license. Any help and input from the community will of course be appreciated. The design will be more or less a standard tri-band calypso phone design (900/1800/1900), with possibly a placement option for having 850/1800/1900. We'll be targetting a modem as opposed to a phone design, so no built-in keypad / display / battery, but external connections. At one edge there should be a PCB edge connector, possibly with mechanical form-factor of PCIe (sinc they're cheap). This connector should allow the module to be plugged into a back-plane with a number of other modems. I've crated an initial Wiki page about the possible / intended modifications from a classic phoned design at http://bb.osmocom.org/trac/wiki/Custom_Calypso_Board : * expose JTAG * board-edge connector for plugging many boards into one backplane * external clock input / buffered clock output * RF connector standard u.fl or SMA or optionally separate Rx/Tx? * I2C/SPI and both UARTs available on headers * on-board EEPROM for storing persistent data, even beyond NOR flashing * SIM card slot, SIM interface also present on header * additional / unused TPU ports * header for TSP / TPU and all data/control interfaces between iota/rita/calypso * RTC crystal and footprint for lithium backup battery * version of the board with uplink / downlink filters switched Feel free to discuss other extensions/modifications you may have in mind. Please note that fundamentally we are still heading for a calypso based design, so this will not be a board that just contains the Iota/Rita and some FPGA or general purpose DSP, as some people have proposed in the past. However, it may be possible to have connector footprints for the TSP / BSP interfaces and make some boarde that don't contain the calypso/ram/nor parts. Pricing will definitely not be anywhere near to the price of current phones. You cannot even source all the components for the price of those refurbished phones, let alone the fairly complex 6-layer PCB. Also, the quantities will be low, we may be manufacturing something like 100 units a batch only. This is a low-effort / side project, so I'm conservative with any estimates and would say that we're happy to have boards shipping by the end of this year. Regards, Harald (waiting for the e-mail flood) -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

9 24

[PATCH] change the keypad layout and the uart port number for the Pirelli DP-L10
by Marco Schwan 15 Aug '12

15 Aug '12

Hi, I have make a patch for the Pirelli DP-L10 created. You can enable and disable the patch in the makefile (src/target/firmware/Makefile). The Keypad layout is tested with rssi.bin app. Only the power button is not available. regards Marco

5 9

Working of ccch_scan and capturing the SDCCH.
by Altaf 08 Aug '12

08 Aug '12

Hello Sylvain I am using the burst_ind branch and have some doubts. I am using a test network, and it has no encryption. Usually the n/w has a low load and the channel structure followed during the assignment is SDCCH/4 + SACCH/C4 or CBCH(SDCCH/4). and timeslot 0 . SDCCH is assigned on timeslot 0.. The ccch_scan is able to capture the SMS sent on timeslot 0 and also only one of the subchannel as per the above assignment. Just for testing, When I use two phones and send an SMS from both of them simultaneously both are assigned timeslot 0 and different subchannels. CCCH_scan could capture only one SMS. meaning that it could only get one subchannel. Am I right about ccch_scan or does it have the capability to get a complete timeslot. ? Thank you Altaf -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Working-of-ccch-scan-and-capturi… Sent from the baseband-devel mailing list archive at Nabble.com.

5 10

cp2102 (betemcu, B75937)
by lonelysurfer 31 Jul '12

31 Jul '12

...a never ending story: i have a working ftdi-ttl, but the cp2102-adapters (http://www.ebay.de/itm/USB-2-0-to-UART-TTL-6PIN-Module-Serial-Converter-CP2…) with the same cable dont work under ubuntu or windows. if i rub the top of the 2.55mm with my finger random data appears. but the loader doesnt upload the firmware. i used the txd, rxd and gnd pins and checked the connections with a multimeter. i tested -m c123xor, -m c123 and the default firmware. flashing custom baudrates was no problem. rivers are installed correctly (stady ttyusb0 under ubuntu/ com1 under win). is there any hint? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/cp2102-betemcu-B75937-tp3489336p… Sent from the baseband-devel mailing list archive at Nabble.com.

3 4

OSMOCOM RECEIVING BUT NOT SENDING DATA THROUGHT TXD - HARDWARE&SOFTWARE TESTED - GNUARM&OSMOCOM BUILT FROM OSMOCOM PAGE INSTRUCTIONS
by Filipe RC - 27 Jul '12

27 Jul '12

Hi, im having some problems in software only, that i describe bellow in my log: -FTDI based interface sold by tronix (vendor link on your site), usb2 to serial adaptor ( model TRX1227, CHIPSET FT232R ) -gnuarm&osmocom compiled from source on debian stable as per osmocom without a single problem. -ran osmocom from su (tried user as well), as instructed and as follows: $ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin output: whenever power button was pressed, all i got was some aparently random hex…(no expert on phone flashing here) with no getting to PROMPT1: "root@box:/home/box/osmocomm/osmocom-bb/src/host/osmocon# sudo ./osmocon -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 00 .. got 3 bytes from modem, data looks like: 72 82 bf r.. got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: a6 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: d2 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: b2 . got 1 bytes from modem, data looks like: a4 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 4d M got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . 2nd press: got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . third press: got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . fourth press: got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 82 . got 1 bytes from modem, data looks like: bf . got 1 bytes from modem, data looks like: 7d } got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: a6 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . " Same output, (maybe with a few more presses) in hex, using gtkterm@115200baud,8bit,nopar,1stop: " 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 B2 A4 12 00 4D A3 A3 68 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 A4 A4 12 00 4D A3 A3 68 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 B2 A4 12 00 4D A3 A3 64 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 A4 A4 12 00 4D A3 A3 64 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 B2 A4 12 00 4D A3 A3 48 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 B2 A4 12 00 4D A3 A3 64 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 B4 A4 12 00 4D A3 A3 48 23 00 00 00 F1 00 72 82 BF 7D FD 7F 00 A6 51 D2 51 A4 A4 12 00 4D A3 A3 48 23 00 00 " -/dev/USB0 permission check - good, even chmoded 777&chown on rc.local. -cable check: thought txd was broken, but wasnt. checked from linux with a led stuck to the txd end of the jack, echo "whatever" > /dev/ttyUSB0, led did flash. -chances i put are: osmocom dependent on some specific C123 firmware? some kind of hidden compilation complication? some kind of ftdi eeprom config/bitrate/parity config missing for osmocom? I hope i have managed to be concise enough. Great work guys. Greatings from portugal, Filipe RC

1 1

For sale some phones that are no longer required.
by George Carpenter 24 Jul '12

24 Jul '12

Hello. I have some motorola phones that they are no longer required by my friends. These phones are with the filter rework done. The phones are complete with serial and antenna cables but can be sent without them. If anyone is interested, please send me a msg at irc (OsmoCarpenteR), do not reply to this msg. Thanks.

1 0

The AMR decode segmentation fault
by bob 24 Jul '12

24 Jul '12

Hi,List I use a TCH/AFS decoder written by Sylvain Munaut and mad to decode the TCH AMR, but it seems there are some bug, but I am not familiar with the convolution codes， the code is following, who are familiar can help me? very thanks! /* * conv_amr.c * * Convolutional code tables for TCH/AFS channels * * Copyright (C) 2011 Sylvain Munaut <tnt(a)246tNt.com> */ #include <stdint.h> #include <osmocom/core/conv.h> /* TCH/AFS12.2 */ /* ----------- */ //# AFS12.2 1/2, K=5, RSC static const uint8_t conv_afs12_2_next_output[][2] = {{0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2}, {0, 3}, {1, 2},}; static const uint8_t conv_afs12_2_next_state[][2] = {{0, 1}, {2, 3}, {4, 5}, {6, 7}, {9, 8}, {11, 10}, {13, 12}, {15, 14}, {1, 0}, {3, 2}, {5, 4}, {7, 6}, {8, 9}, {10, 11}, {12, 13}, {14, 15},}; static const uint8_t conv_afs12_2_next_term_output[] = {0, 1, 0, 1, 3, 2, 3, 2, 3, 2, 3, 2, 0, 1, 0, 1,}; static const uint8_t conv_afs12_2_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30,}; static const uint16_t conv_afs12_2_punct[] = {321, 325, 329, 333, 337, 341, 345, 349, 353, 357, 361, 363, 365, 369, 373, 377, 379, 381, 385, 389, 393, 395, 397, 401, 405, 409, 411, 413, 417, 421, 425, 427, 429, 433, 437, 441, 443, 445, 449, 453, 457, 459, 461, 465, 469, 473, 475, 477, 481, 485, 489, 491, 493, 495, 497, 499, 501, 503, 505, 507, -1,}; const struct osmo_conv_code conv_tch_afs_12_2 = { .N = 2, .K = 5, .len = 250, .next_output = conv_afs12_2_next_output, .next_state = conv_afs12_2_next_state, .next_term_output = conv_afs12_2_next_term_output, .next_term_state = conv_afs12_2_next_term_state, .puncture = conv_afs12_2_punct, }; //# AFS10.2 1/3, K=5, RSC static const uint8_t conv_afs10_2_next_output[][2] = {{0, 7}, {2, 5}, {4, 3}, {6, 1}, {2, 5}, {0, 7}, {6, 1}, {4, 3}, {0, 7}, {2, 5}, {4, 3}, {6, 1}, {2, 5}, {0, 7}, {6, 1}, {4, 3},}; static const uint8_t conv_afs10_2_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15},}; static const uint8_t conv_afs10_2_next_term_output[] = {0, 5, 3, 6, 5, 0, 6, 3, 7, 2, 4, 1, 2, 7, 1, 4,}; static const uint8_t conv_afs10_2_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 0, 2, 4, 6, 8, 10, 12, 14,}; const uint16_t conv_afs10_2_punct[] = {1, 4, 7, 10, 16, 19, 22, 28, 31, 34, 40, 43, 46, 52, 55, 58, 64, 67, 70, 76, 79, 82, 88, 91, 94, 100, 103, 106, 112, 115, 118, 124, 127, 130, 136, 139, 142, 148, 151, 154, 160, 163, 166, 172, 175, 178, 184, 187, 190, 196, 199, 202, 208, 211, 214, 220, 223, 226, 232, 235, 238, 244, 247, 250, 256, 259, 262, 268, 271, 274, 280, 283, 286, 292, 295, 298, 304, 307, 310, 316, 319, 322, 325, 328, 331, 334, 337, 340, 343, 346, 349, 352, 355, 358, 361, 364, 367, 370, 373, 376, 379, 382, 385, 388, 391, 394, 397, 400, 403, 406, 409, 412, 415, 418, 421, 424, 427, 430, 433, 436, 439, 442, 445, 448, 451, 454, 457, 460, 463, 466, 469, 472, 475, 478, 481, 484, 487, 490, 493, 496, 499, 502, 505, 508, 511, 514, 517, 520, 523, 526, 529, 532, 535, 538, 541, 544, 547, 550, 553, 556, 559, 562, 565, 568, 571, 574, 577, 580, 583, 586, 589, 592, 595, 598, 601, 604, 607, 609, 610, 613, 616, 619, 621, 622, 625, 627, 628, 631, 633, 634, 636, 637, 639, 640, -1,}; const struct osmo_conv_code conv_tch_afs_10_2 = { .N = 3, .K = 5, .len = 210, .next_output = conv_afs10_2_next_output, .next_state = conv_afs10_2_next_state, .next_term_output = conv_afs10_2_next_term_output, .next_term_state = conv_afs10_2_next_term_state, .puncture = conv_afs10_2_punct, }; //# AFS7.95 1/3, K=7, RSC static const uint8_t conv_afs7_95_next_output[][2] = {{0, 7}, {3, 4}, {2, 5}, {1, 6}, {2, 5}, {1, 6}, {0, 7}, {3, 4}, {3, 4}, {0, 7}, {1, 6}, {2, 5}, {1, 6}, {2, 5}, {3, 4}, {0, 7}, {3, 4}, {0, 7}, {1, 6}, {2, 5}, {1, 6}, {2, 5}, {3, 4}, {0, 7}, {0, 7}, {3, 4}, {2, 5}, {1, 6}, {2, 5}, {1, 6}, {0, 7}, {3, 4}, {0, 7}, {3, 4}, {2, 5}, {1, 6}, {2, 5}, {1, 6}, {0, 7}, {3, 4}, {3, 4}, {0, 7}, {1, 6}, {2, 5}, {1, 6}, {2, 5}, {3, 4}, {0, 7}, {3, 4}, {0, 7}, {1, 6}, {2, 5}, {1, 6}, {2, 5}, {3, 4}, {0, 7}, {0, 7}, {3, 4}, {2, 5}, {1, 6}, {2, 5}, {1, 6}, {0, 7}, {3, 4},}; static const uint8_t conv_afs7_95_next_state[][2] = {{0, 1}, {2, 3}, {5, 4}, {7, 6}, {9, 8}, {11, 10}, {12, 13}, {14, 15}, {16, 17}, {18, 19}, {21, 20}, {23, 22}, {25, 24}, {27, 26}, {28, 29}, {30, 31}, {33, 32}, {35, 34}, {36, 37}, {38, 39}, {40, 41}, {42, 43}, {45, 44}, {47, 46}, {49, 48}, {51, 50}, {52, 53}, {54, 55}, {56, 57}, {58, 59}, {61, 60}, {63, 62}, {1, 0}, {3, 2}, {4, 5}, {6, 7}, {8, 9}, {10, 11}, {13, 12}, {15, 14}, {17, 16}, {19, 18}, {20, 21}, {22, 23}, {24, 25}, {26, 27}, {29, 28}, {31, 30}, {32, 33}, {34, 35}, {37, 36}, {39, 38}, {41, 40}, {43, 42}, {44, 45}, {46, 47}, {48, 49}, {50, 51}, {53, 52}, {55, 54}, {57, 56}, {59, 58}, {60, 61}, {62, 63},}; static const uint8_t conv_afs7_95_next_term_output[] = {0, 3, 5, 6, 5, 6, 0, 3, 3, 0, 6, 5, 6, 5, 3, 0, 4, 7, 1, 2, 1, 2, 4, 7, 7, 4, 2, 1, 2, 1, 7, 4, 7, 4, 2, 1, 2, 1, 7, 4, 4, 7, 1, 2, 1, 2, 4, 7, 3, 0, 6, 5, 6, 5, 3, 0, 0, 3, 5, 6, 5, 6, 0, 3,}; static const uint8_t conv_afs7_95_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62,}; const uint16_t conv_afs7_95_punct[] = {1, 2, 4, 5, 8, 22, 70, 118, 166, 214, 262, 310, 317, 319, 325, 332, 334, 341, 343, 349, 356, 358, 365, 367, 373, 380, 382, 385, 389, 391, 397, 404, 406, 409, 413, 415, 421, 428, 430, 433, 437, 439, 445, 452, 454, 457, 461, 463, 469, 476, 478, 481, 485, 487, 490, 493, 500, 502, 503, 505, 506, 508, 509, 511, 512, -1,}; const struct osmo_conv_code conv_tch_afs_7_95 = { .N = 3, .K = 7, .len = 165, .next_output = conv_afs7_95_next_output, .next_state = conv_afs7_95_next_state, .next_term_output = conv_afs7_95_next_term_output, .next_term_state = conv_afs7_95_next_term_state, .puncture = conv_afs7_95_punct, }; //# AFS 7.4 1/3, K=5, RSC (2) static const uint8_t conv_afs7_4_next_output[][2] = {{0, 7}, {2, 5}, {4, 3}, {6, 1}, {2, 5}, {0, 7}, {6, 1}, {4, 3}, {0, 7}, {2, 5}, {4, 3}, {6, 1}, {2, 5}, {0, 7}, {6, 1}, {4, 3},}; static const uint8_t conv_afs7_4_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15},}; static const uint8_t conv_afs7_4_next_term_output[] = {0, 5, 3, 6, 5, 0, 6, 3, 7, 2, 4, 1, 2, 7, 1, 4,}; static const uint8_t conv_afs7_4_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 0, 2, 4, 6, 8, 10, 12, 14,}; const uint16_t conv_afs7_4_punct[] = {0, 355, 361, 367, 373, 379, 385, 391, 397, 403, 409, 415, 421, 427, 433, 439, 445, 451, 457, 460, 463, 466, 468, 469, 471, 472, -1,}; const struct osmo_conv_code conv_tch_afs_7_4 = { .N = 3, .K = 5, .len = 154, .next_output = conv_afs7_4_next_output, .next_state = conv_afs7_4_next_state, .next_term_output = conv_afs7_4_next_term_output, .next_term_state = conv_afs7_4_next_term_state, .puncture = conv_afs7_4_punct, }; //# AFS6.7 1/4, K=5, RSC static const uint8_t conv_afs6_7_next_output[][2] = {{0, 15}, {4, 11}, {8, 7}, {12, 3}, {4, 11}, {0, 15}, {12, 3}, {8, 7}, {0, 15}, {4, 11}, {8, 7}, {12, 3}, {4, 11}, {0, 15}, {12, 3}, {8, 7},}; static const uint8_t conv_afs6_7_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15},}; static const uint8_t conv_afs6_7_next_term_output[] = {0, 11, 7, 12, 11, 0, 12, 7, 15, 4, 8, 3, 4, 15, 3, 8,}; static const uint8_t conv_afs6_7_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 0, 2, 4, 6, 8, 10, 12, 14,}; const uint16_t conv_afs6_7_punct[] = {1, 3, 7, 11, 15, 27, 39, 55, 67, 79, 95, 107, 119, 135, 147, 159, 175, 187, 199, 215, 227, 239, 255, 267, 279, 287, 291, 295, 299, 303, 307, 311, 315, 319, 323, 327, 331, 335, 339, 343, 347, 351, 355, 359, 363, 367, 369, 371, 375, 377, 379, 383, 385, 387, 391, 393, 395, 399, 401, 403, 407, 409, 411, 415, 417, 419, 423, 425, 427, 431, 433, 435, 439, 441, 443, 447, 449, 451, 455, 457, 459, 463, 465, 467, 471, 473, 475, 479, 481, 483, 487, 489, 491, 495, 497, 499, 503, 505, 507, 511, 513, 515, 519, 521, 523, 527, 529, 531, 535, 537, 539, 543, 545, 547, 549, 551, 553, 555, 557, 559, 561, 563, 565, 567, 569, 571, 573, 575, -1,}; const struct osmo_conv_code conv_tch_afs_6_7 = { .N = 4, .K = 5, .len = 140, .next_output = conv_afs6_7_next_output, .next_state = conv_afs6_7_next_state, .next_term_output = conv_afs6_7_next_term_output, .next_term_state = conv_afs6_7_next_term_state, .puncture = conv_afs6_7_punct, }; //# AFS5.9 1/4, K=7, RSC static const uint8_t conv_afs5_9_next_output[][2] = {{0, 15}, {8, 7}, {4, 11}, {12, 3}, {4, 11}, {12, 3}, {0, 15}, {8, 7}, {8, 7}, {0, 15}, {12, 3}, {4, 11}, {12, 3}, {4, 11}, {8, 7}, {0, 15}, {8, 7}, {0, 15}, {12, 3}, {4, 11}, {12, 3}, {4, 11}, {8, 7}, {0, 15}, {0, 15}, {8, 7}, {4, 11}, {12, 3}, {4, 11}, {12, 3}, {0, 15}, {8, 7}, {0, 15}, {8, 7}, {4, 11}, {12, 3}, {4, 11}, {12, 3}, {0, 15}, {8, 7}, {8, 7}, {0, 15}, {12, 3}, {4, 11}, {12, 3}, {4, 11}, {8, 7}, {0, 15}, {8, 7}, {0, 15}, {12, 3}, {4, 11}, {12, 3}, {4, 11}, {8, 7}, {0, 15}, {0, 15}, {8, 7}, {4, 11}, {12, 3}, {4, 11}, {12, 3}, {0, 15}, {8, 7},}; static const uint8_t conv_afs5_9_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {17, 16}, {18, 19}, {20, 21}, {23, 22}, {24, 25}, {27, 26}, {29, 28}, {30, 31}, {32, 33}, {35, 34}, {37, 36}, {38, 39}, {41, 40}, {42, 43}, {44, 45}, {47, 46}, {49, 48}, {50, 51}, {52, 53}, {55, 54}, {56, 57}, {59, 58}, {61, 60}, {62, 63}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15}, {16, 17}, {19, 18}, {21, 20}, {22, 23}, {25, 24}, {26, 27}, {28, 29}, {31, 30}, {33, 32}, {34, 35}, {36, 37}, {39, 38}, {40, 41}, {43, 42}, {45, 44}, {46, 47}, {48, 49}, {51, 50}, {53, 52}, {54, 55}, {57, 56}, {58, 59}, {60, 61}, {63, 62},}; static const uint8_t conv_afs5_9_next_term_output[] = {0, 7, 11, 12, 11, 12, 0, 7, 7, 0, 12, 11, 12, 11, 7, 0, 8, 15, 3, 4, 3, 4, 8, 15, 15, 8, 4, 3, 4, 3, 15, 8, 15, 8, 4, 3, 4, 3, 15, 8, 8, 15, 3, 4, 3, 4, 8, 15, 7, 0, 12, 11, 12, 11, 7, 0, 0, 7, 11, 12, 11, 12, 0, 7,}; static const uint8_t conv_afs5_9_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62,}; const uint16_t conv_afs5_9_punct[] = {0, 1, 3, 5, 7, 11, 15, 31, 47, 63, 79, 95, 111, 127, 143, 159, 175, 191, 207, 223, 239, 255, 271, 287, 303, 319, 327, 331, 335, 343, 347, 351, 359, 363, 367, 375, 379, 383, 391, 395, 399, 407, 411, 415, 423, 427, 431, 439, 443, 447, 455, 459, 463, 467, 471, 475, 479, 483, 487, 491, 495, 499, 503, 507, 509, 511, 512, 513, 515, 516, 517, 519, -1,}; const struct osmo_conv_code conv_tch_afs_5_9 = { .N = 4, .K = 7, .len = 124, .next_output = conv_afs5_9_next_output, .next_state = conv_afs5_9_next_state, .next_term_output = conv_afs5_9_next_term_output, .next_term_state = conv_afs5_9_next_term_state, .puncture = conv_afs5_9_punct, }; //# AFS5.15 1/5, K=5, RSC static const uint8_t conv_afs5_15_next_output[][2] = {{0, 31}, {4, 27}, {24, 7}, {28, 3}, {4, 27}, {0, 31}, {28, 3}, {24, 7}, {0, 31}, {4, 27}, {24, 7}, {28, 3}, {4, 27}, {0, 31}, {28, 3}, {24, 7},}; static const uint8_t conv_afs5_15_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15},}; static const uint8_t conv_afs5_15_next_term_output[] = {0, 27, 7, 28, 27, 0, 28, 7, 31, 4, 24, 3, 4, 31, 3, 24,}; static const uint8_t conv_afs5_15_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 0, 2, 4, 6, 8, 10, 12, 14,}; const uint16_t conv_afs5_15_punct[] = {0, 4, 5, 9, 10, 14, 15, 20, 25, 30, 35, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 150, 160, 170, 180,190, 200, 210, 220, 230, 240, 250, 260, 270, 280,290, 300, 310, 315, 320, 325, 330, 334, 335, 340, 344, 345, 350, 354, 355, 360, 364, 365, 370, 374, 375, 380, 384, 385, 390, 394, 395, 400, 404, 405, 410, 414, 415, 420, 424, 425, 430, 434, 435, 440, 444, 445, 450, 454, 455, 460, 464, 465, 470, 474, 475, 480, 484, 485, 490, 494, 495, 500, 504, 505, 510, 514, 515, 520, 524, 525, 529, 530, 534, 535, 539, 540, 544, 545, 549, 550, 554, 555, 559, 560, 564, -1,}; const struct osmo_conv_code conv_tch_afs_5_15 = { .N = 5, .K = 5, .len = 109, .next_output = conv_afs5_15_next_output, .next_state = conv_afs5_15_next_state, .next_term_output = conv_afs5_15_next_term_output, .next_term_state = conv_afs5_15_next_term_state, .puncture = conv_afs5_15_punct, }; //# AFS4.75 1/5, K=7, RSC static const uint8_t conv_afs4_75_next_output[][2] = {{0, 31}, {24, 7}, {4, 27}, {28, 3}, {4, 27}, {28, 3}, {0, 31}, {24, 7}, {24, 7}, {0, 31}, {28, 3}, {4, 27}, {28, 3}, {4, 27}, {24, 7}, {0, 31}, {24, 7}, {0, 31}, {28, 3}, {4, 27}, {28, 3}, {4, 27}, {24, 7}, {0, 31}, {0, 31}, {24, 7}, {4, 27}, {28, 3}, {4, 27}, {28, 3}, {0, 31}, {24, 7}, {0, 31}, {24, 7}, {4, 27}, {28, 3}, {4, 27}, {28, 3}, {0, 31}, {24, 7}, {24, 7}, {0, 31}, {28, 3}, {4, 27}, {28, 3}, {4, 27}, {24, 7}, {0, 31}, {24, 7}, {0, 31}, {28, 3}, {4, 27}, {28, 3}, {4, 27}, {24, 7}, {0, 31}, {0, 31}, {24, 7}, {4, 27}, {28, 3}, {4, 27}, {28, 3}, {0, 31}, {24, 7},}; static const uint8_t conv_afs4_75_next_state[][2] = {{0, 1}, {3, 2}, {5, 4}, {6, 7}, {9, 8}, {10, 11}, {12, 13}, {15, 14}, {17, 16}, {18, 19}, {20, 21}, {23, 22}, {24, 25}, {27, 26}, {29, 28}, {30, 31}, {32, 33}, {35, 34}, {37, 36}, {38, 39}, {41, 40}, {42, 43}, {44, 45}, {47, 46}, {49, 48}, {50, 51}, {52, 53}, {55, 54}, {56, 57}, {59, 58}, {61, 60}, {62, 63}, {1, 0}, {2, 3}, {4, 5}, {7, 6}, {8, 9}, {11, 10}, {13, 12}, {14, 15}, {16, 17}, {19, 18}, {21, 20}, {22, 23}, {25, 24}, {26, 27}, {28, 29}, {31, 30}, {33, 32}, {34, 35}, {36, 37}, {39, 38}, {40, 41}, {43, 42}, {45, 44}, {46, 47}, {48, 49}, {51, 50}, {53, 52}, {54, 55}, {57, 56}, {58, 59}, {60, 61}, {63, 62},}; static const uint8_t conv_afs4_75_next_term_output[] = {0, 7, 27, 28, 27, 28, 0, 7, 7, 0, 28, 27, 28, 27, 7, 0, 24, 31, 3, 4, 3, 4, 24, 31, 31, 24, 4, 3, 4, 3, 31, 24, 31, 24, 4, 3, 4, 3, 31, 24, 24, 31, 3, 4, 3, 4, 24, 31, 7, 0, 28, 27, 28, 27, 7, 0, 0, 7, 27, 28, 27, 28, 0, 7,}; static const uint8_t conv_afs4_75_next_term_state[] = {0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62,}; const uint16_t conv_afs4_75_punct[] = {0, 1, 2, 4, 5, 7, 9, 15, 25, 35, 45, 55, 65, 75, 85, 95, 105, 115, 125, 135, 145, 155, 165, 175, 185, 195, 205, 215, 225, 235, 245, 255, 265, 275, 285, 295, 305, 315, 325, 335, 345, 355, 365, 375, 385, 395, 400, 405, 410, 415, 420, 425, 430, 435, 440, 445, 450, 455, 459, 460, 465, 470, 475, 479, 480, 485, 490, 495, 499, 500, 505, 509, 510, 515, 517, 519, 520, 522, 524, 525, 526, 527, 529, 530, 531, 532, 534, -1,}; const struct osmo_conv_code conv_tch_afs_4_75 = { .N = 5, .K = 7, .len = 101, .next_output = conv_afs4_75_next_output, .next_state = conv_afs4_75_next_state, .next_term_output = conv_afs4_75_next_term_output, .next_term_state = conv_afs4_75_next_term_state, .puncture = conv_afs4_75_punct, }; -- View this message in context: http://baseband-devel.722152.n3.nabble.com/The-AMR-decode-segmentation-faul… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Poll: Osmocom meeting 25th of July?
by Harald Welte 23 Jul '12

23 Jul '12

Hi all! On Wednesday, 25th of July we would have the next Osmocom meeting berlin. However, neither Holger nor I will be in Berlin on that day to host the event. I also know that Tobias will not be in Berlin. Nonetheless, if there are other people that want to meet up, there is no reason to not hold it! So I would like to get some feedback on who would want to attend next wednesday. If there are a couple of people, I'll try to find somebody who can open the CCCB for you. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

7 9

Re: Sagem OT-290 trace phone / GSMTAP integration
by Thomas Bertani 22 Jul '12

22 Jul '12

On 22 July 2012 14:26, Tyson Key <tyson.key(a)gmail.com> wrote: > Hi Thomas, > > Although myself and a few others (Denis?) have tentatively volunteered to > work on it, no-one has actually requested (or received) the hardware itself > yet, as far as I know. If I remember correctly, two phones were available - > so it might be possible to share the workload, if arrangements can be made > regarding logistics. > Hi, well I can start to work on it immediately, however I'm not sure whether one or two phones were actually available, so if it's only one, it won't be possible to share the workload. > If you're interested, then I'd suggest asking Harald for a copy of the > protocol specification to read through, to determine its feasibility in > order to figure out how long you think it would take. I've already received it, it doesn't seem an excessively long work but at the moment it would be difficult to do a precise estimation. > I hope that helps, > > Tyson. Thank you for the update, Thomas

1 0

Tooling up for osmocom, gnuradio, and android ... suggestions ?
by John Case 21 Jul '12

21 Jul '12

I am a mac and NetBSD user and have not run any linux systems for many years. I have never used Debian/Ubuntu/etc. Now I would like to begin doing work with osmocom, GNU radio, SDRs and some android development. I knw it's a religious question, but since I am starting with a completely blank slate, what would be the simplest, most painless distro to set up a development and build environment (cross compiling for arm, building osmocom, gnu radio, and running android development tools and SDKs) ? I assume the answer must be either Debian or Ubuntu, but really have no idea ... comments ? I think the nicest thing would be a distro that *already* had a full complement of the GNU devel/conf/build tools that all the examples in the wiki rely on ... so I wouldn;t have to worry about getting that environment up from scratch ... Thanks.

5 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel July 2012