simtrace

simtrace@lists.osmocom.org

350 discussions

SIMtrace v0.9+
by Kevin Redon 22 May '11

22 May '11

Hi, The BOM (bill of material) is ready. I finished the netlist, footprint drawing, and footprint selection. all available at : https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ next task : place the components on the board (i'll try smart card size) and route the lines. Kevin

3 13

softSIM
by Kevin Redon 13 May '11

13 May '11

Hi, softSIM is out : http://bb.osmocom.org/trac/wiki/softSIM It's not fully implemented but already working (I hope). The osmocomBB use/cooperation will come out soon. Other tools are coming next week (I need to clean them). Have fun, tsaitgaist

2 1

Osmocom project vs. sysmocom GmbH
by Harald Welte 13 May '11

13 May '11

Hi all! As some of you already know, Holger and I have recently started a new company called "sysmocom - systems for mobile communications GmbH". The process of establishing the new company has now formally concluded. Before some rumours start to spread, we would like to clarify some points and make sure there is mutual understanding between the Osmocom community and the sysmocom company. sysmocom is intended to provide commercial offerings related to the Osmocom projects. This is not entirely new. Especially on the network side, people like Holger and I have been doing quite a lot of paid development to bring those projects forward. We would not have many of the features we have today, if it wasn't for customers who actually pay us for development of OpenBSC, OsmoBSC, OsmoSGSN and the various side projects more targetted at a real network operator like cellmgr-ng, bsc-nat, gb_proxy - just to name a few. However, this has always only been freelancing development of Software. With sysmocom, we want to go one step further and work on hardware products related to the various Free Software projects. Right now I don't want to talk too much about unfinished products, but we are working towards an inexpensive BTS product, we are funding the prototypes for Osmocom SIMtrace, and we will likely also see stuff like OpenBSC appliances. Given our past involvement and exposure into other projects that share a split Free Software / business set-up, we think we understand very well where potential issues of conflict between the two sides may be. Let me make some more clarification what this is not about: * sysmocom is not about creating proprietary derivates of Osmocom software. We work on Free Software which is publicly available under OSI approved and FSF endorsed licenses. We may offer proprietary hardware and sometimes software - but those are independent projects from existing Osmocom software. * we specifically will not have a public and a non-public version of the same program with differences in features. * sysmocom is not a VC-funded startup. It's a very small company run out of personal funds with no intention to take external funding or grow rapidly. Nobody but Holger and I determine where it goes and what it does. * sysmocom does not hold any copyright on the Free Software projects. The copyrights stay distributed with the major authors such as Holger, Onwaves, Sylvain, Dieter, Andreas and myself. None of the others have any affiliation with sysmocom. I have (personally, unrelated to sysmocom) asked some of the smaller contributors for a copyright transfer to make sure we could do the AGPLv3 transition, or future re-licensing decisions without having to ask dozens and dozens of people. sysmocom does not seek to control the Free Software projects. * we will maintain a strict separation between the community side of things and the business side. Unlike some other popular projects, we will not end up in a situation where the osmocom.org websites will be full of advertisements and hidden links that lure you on the company website. * we will keep a strict separation of naming. Osmocom is for the FOSS projects, sysmocom for the business. The company will use the term "Osmocom" only in descriptive context, not as a product name, brand or for advertisement. If you do have any concerns, please feel free to share them. However, I'd like to avoid cross-posting them throguh different mailing lists. Please follow-up-to openbsc(a)lists.osmocom.org Regards, Harald -- - Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

1 0

simtrace hardware kicad project now part of simtrace.git
by Harald Welte 13 May '11

13 May '11

Hi all! The kicad project for the simtrace hardware that Kevin has been working on is now available as part of the simtrace.git repository on git.osmocom.org. This will allow us to document the revision history of any modifications to the hardware in the commit messages, and it allows us to see differences between individual versions. 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)

1 0

SIMtrace v0.8
by Kevin Redon 12 May '11

12 May '11

hi, here v0.8 : https://gsm.tsaitgaist.info/SIMtrace/v0.8/ Compared to v0.7+, I added 2 1n4148 after the parallel voltage regulator outputs. I wanted to avoid the regulators to fuzz each other, but I don't know if it's right. Maybe an additional zener diode is also required. Now I'm looking for the parts and footprints. Kevin

3 6

packet-gsm_sim wireshark
by K2 10 May '11

10 May '11

It is assumed in the dissector that the TERMINAL PROFILE has a len of 17, which is not the case with the SIM i'm currently using. I fixed it replacing with: case 0x10: /* TERMINAL PROFILE */ offset += DATA_OFFS; if(p3 >= 1) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b1, ett_tprof_b1, tprof_b1_fields, FALSE); if(p3 >= 2) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b2, ett_tprof_b2, tprof_b2_fields, FALSE); if(p3 >= 3) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b3, ett_tprof_b3, tprof_b3_fields, FALSE); if(p3 >= 4) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b4, ett_tprof_b4, tprof_b4_fields, FALSE); if(p3 >= 5) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b5, ett_tprof_b5, tprof_b5_fields, FALSE); if(p3 >= 6) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b6, ett_tprof_b6, tprof_b6_fields, FALSE); if(p3 >= 7) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b7, ett_tprof_b7, tprof_b7_fields, FALSE); if(p3 >= 8) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b8, ett_tprof_b8, tprof_b8_fields, FALSE); if(p3 >= 9) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b9, ett_tprof_b9, tprof_b9_fields, FALSE); if(p3 >= 10) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b10, ett_tprof_b10, tprof_b10_fields, FALSE); if(p3 >= 11) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b11, ett_tprof_b11, tprof_b11_fields, FALSE); if(p3 >= 12) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b12, ett_tprof_b12, tprof_b12_fields, FALSE); if(p3 >= 13) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b13, ett_tprof_b13, tprof_b13_fields, FALSE); if(p3 >= 14) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b14, ett_tprof_b14, tprof_b14_fields, FALSE); if(p3 >= 15) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b15, ett_tprof_b15, tprof_b15_fields, FALSE); if(p3 >= 16) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b16, ett_tprof_b16, tprof_b16_fields, FALSE); if(p3 >= 17) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b17, ett_tprof_b17, tprof_b17_fields, FALSE); /* FIXME */ break;

2 1

SIMtrace v0.7
by Kevin Redon 09 May '11

09 May '11

Hi The corrections have been applied. I hope I did not forget anything. The main changes : - reset is a jumper - bootloader switch added - 100k resistors used (instead of 4.7k, I hope it does not break anything) - jack connector added (for the debug) - WP from flash connected - USB voltage regulator TPS73633 used (lower capacitance) - USB buffer used instead of the openPCB solution (thus no pull-up and reset connection). saves space and complexity - pin renamed - QS3244 instead of QS3245 used, I/O and other pins are controlled separately - ... To make the changes I used the AT91SAM7X-EK Evaluation Board User Guide. The overall capacitance is reduced, but I think the 22uF for the battery should be kept. files : https://gsm.tsaitgaist.info/SIMtrace/v0.7/ good luck, Kevin

2 6

SIMtrace v0.6 schema
by Kevin Redon 08 May '11

08 May '11

Hi, here the schema. all the components are on it, but I don't know if the electrical part is right. Any comments/advices are welcome. schema : https://gsm.tsaitgaist.info/SIMtrace/v0.6/SIMtrace.ps source (KiCAD) : https://gsm.tsaitgaist.info/SIMtrace/v0.6/

3 4

Re: SPI flash
by Kevin Redon 06 May '11

06 May '11

Hi, I never tried WSON, but I think it's still possible to solder it. To do it (as most of the smd), I use a heating plate and a hot air gun (with soldering paste), and not a soldering iron. So it might also work with this package. But the SOIC package is easier for others. Even it's it two time the price, it's not too expensive. So you can choose any. Kevin On 06.05.2011 11:34, Harald Welte wrote: > Hi! > > I think one of the big concerns is to use components that can still be > soldered manually (like SOIC-8). All the larger-than-32MBit (4MByte) > SPI flashes that I could find were in smaller cases with no leads > extending from the case (like WSON). > > This one looks fine to me, and is available from digikey: > http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=SST25VF032… > datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/S71327_04.pdf > > Regards, > Harald >

1 0

None
by Luca Bongiorni 06 May '11

06 May '11

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace