simtrace

simtrace@lists.osmocom.org

347 discussions

Webshop for the SIMtrace hardware
by Holger Hans Peter Freyther 28 Aug '11

28 Aug '11

Hi all, I have toyed with spreecommerce[1] on and off and would like to have some friendly users to see if the whole checkout process is working. The shop can be found here[2] but I would like to share some technical details with you. My patched spreecommerce can be found on gitorious[3], for some of the changes I should have created an extension but right now I think I prefer git pull --rebase to see what changed. If you enter your EUVAT number you should not be charged VAT (unless you are in Germany). We are using a CA Cert signed certificate, your browser will tell you that it is dangerous, I think we prefer putting the money into future HW products than getting a signature from a 'trust worthy' org. Shipping cost calculation is a bit of a mess, does anyone know if DHL offers an API for it? The installation has four zones (Germany, EUVAT region, USA, World Wide)? Terms/Conditions and Privacy Policy are very basic and need to be refined, with best effort I tried to make short and clear. Technical feedback, specially on caching, rails (security), etc. is very welcome. holger [1] spreecommerce.com [2] https://shop.sysmocom.de [3] https://gitorious.org/sysmocom-spreecommerce

1 0

availability through web shop?
by Dirk Kirsten 19 Aug '11

19 Aug '11

Hi, I just wanted to ask for a short heads up of the release schedule. I know you have been selling the boards at the CCC camp, but I haven't been there. It was mentioned on the list that you are planning to sell it through a web shop in the "2nd half of august". I am sorry for being in such a hurry, but I'd really like to have the boards on my desk in august, due to my holidays afterwards. Cheers, Dirk

4 4

samba precondition
by Kevin Redon 19 Aug '11

19 Aug '11

Hi, I think I found a small hardware bug while fixing the v1.0p boards (adding a 100nF capacitor near the LDO pin 4). When I want to put the SAM7S in SAM-BA mode (shorting TEST and 3.3V pins), it does not work, even after waiting a lot of time. The 2 LEDs are on, and when I touch PA0 (pin 48 on the right upper corner of the SAM7S, near the "A") with a piece of metal, the LEDs switch off and putting into SAM-BA mode works. maybe PA0 needs to be low/up but it is not connected and probably floating. The solution is easy, but should we correct that for the next version (if it is a real bug)? Also, simtrace seems to load sam_ba module, which I have to remove so I can use sam7util multiple times: sudo rmmod cdc_acm && sudo rmmod sam_ba && sudo ./sam7 --exec set_clock --exec unlock_regions --exec "flash ../openpcd/firmware/main_simtrace.samba" thanks, kevin

5 5

'no simcard' bug / SIMtrace firmware update
by Harald Welte 16 Aug '11

16 Aug '11

Hi all, I have meanwhile solved the first half of the bug that was causing a lot of problems during the CCC Camp 2011. In git commit fa7297b93f4187bce9439bb676874815f66d8f21 to openpcd.git, I have made the following changes: * make sure SIMtrace remains completely passive even in case of (alleged) parity errors * prevent an IRQ storm by properly clearing error flags in the USART, which have lead to a watchdog triggered reset which in turn caused a USB disconnect So right now, you should not see the "No SIM card" or "SIM card error" in the display of your phone, no matter what phone / simcard is used. However, the data logged by SIMtrace still is incorrect in those cases. I hope to release a fix for that soon. The updated 'main_simtrace.bin' firmware is attached to this mail. You can install it by using "dfu-util -d 16c0:0762 -a0 -D ./main_simtrace.bin -R" which should produce something like: ======= dfu-util - (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Opening USB Device 0x16c0:0x0762... Claiming USB DFU Runtime Interface... Determining device status: state = appIDLE, status = 0 Device really in Runtime Mode, send DFU detach request... Resetting USB... Opening USB Device... Found Runtime: [0x16c0:0x0762] devnum=41, cfg=0, intf=0, alt=0, name="SimTrace DFU Interface - Application Partition" Claiming USB DFU Interface... Setting Alternate Setting #0 ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Device returned transfer size 256 bytes_per_hash=415 Copying data from PC to DFU device Starting download: [##################################################] finished! state(7) = dfuMANIFEST, status(0) = No error condition is present state(2) = dfuIDLE, status(0) = No error condition is present Done! can't detach: error sending control message: Broken pipe Resetting USB to switch back to runtime mode ======== After that, the new firmware has been programmed into your SIMtrace and you can immediately use it again (no reset/re-plug/... needed) 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)

2 2

TST PIN and SIMtrace Schematic question
by Holger Hans Peter Freyther 15 Aug '11

15 Aug '11

Hi all, I have a stupid schematic question. I read section 6.2 of the SAM7 datasheet (as in the git tree) and it mentions that besides TST high also PA0, PA1 and PA2 needs to be high, and PA0, PA1 should not be low as this leads to unpredictable results. So I wonder about the following: - PA0 is not connected, default state should be high - PA1 is connected with a trace that leads to PA6 - PA2 is connected with a trace that leads to PA4 will PA4, PA6 work like a pull down (I am not sure of Table 10-3)? cheers holger

2 2

Connecting the FTDI cable
by Stefan Petersen 15 Aug '11

15 Aug '11

Hello! I skimmed over the schematic and noticed that the power output from the FTDI cable is connected directly to the 3.3V line. In my experience the output from the FTDI cable is 5V even though it is the 3.3V version. I have actually fried some designs due to this. I'm not 100% sure about this, but my tips is to check it before you connect it. Best regards, /Stefan

4 3

SIMtrace usermanual
by Holger Hans Peter Freyther 15 Aug '11

15 Aug '11

Hi all, there is a doc/ directory in the simtrace source and the documentation is done with docbook. The result of the document can be seen here[1]. It is still missing proof reading, sections on building the patched wireshark, building the firmware and more content. comments welcome holger [1] http://bb.osmocom.org/trac/attachment/wiki/SIMtrace/usermanual.pdf

1 1

[PATCH 1/3] Include <stdlib.h> for malloc() and free()
by Peter Stuge 15 Aug '11

15 Aug '11

--- host/main.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/host/main.c b/host/main.c index a1e5600..1823857 100644 --- a/host/main.c +++ b/host/main.c @@ -19,6 +19,7 @@ #include <errno.h> #include <unistd.h> #include <stdio.h> +#include <stdlib.h> #include <string.h> #include <stdint.h> #include <time.h> -- 1.7.4.1.343.ga91df.dirty

2 3

tags for the hardware
by Holger Hans Peter Freyther 15 Aug '11

15 Aug '11

Hi all, are there tags for the v1.0p hardware and other prototypes? I don't see them with git tag -l. holger

2 1

[PATCH] fix simtrace crash when unpluging usb
by Luka Perkov 12 Aug '11

12 Aug '11

This patch should fix the crash from simtrace app when SIMtrace hardware is unpluged from usb or when it is reseted. This feature was proposed on simtrace workshop on ccc camp. Signed-off-by: Luka Perkov < lists ->-to->- lukaperkov.net > --- diff --git a/host/main.c b/host/main.c index a1e5600..61656be 100644 --- a/host/main.c +++ b/host/main.c @@ -187,7 +187,14 @@ int main(int argc, char **argv) rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000); if (rc < 0 && rc != -EAGAIN) { fprintf(stderr, "Error submitting BULK IN urb: %s\n", usb_strerror()); - exit(1); + while (1) { + udev = usb_find_reopen(SIMTRACE_USB_VENDOR, SIMTRACE_USB_PRODUCT); + if (!udev) { + usleep(1000000); + } else { + break; + } + } } if (rc > 0) { //printf("URB: %s\n", osmo_hexdump(buf, rc)); diff --git a/host/usb_helper.c b/host/usb_helper.c index 231363a..97ea7b6 100644 --- a/host/usb_helper.c +++ b/host/usb_helper.c @@ -28,6 +28,8 @@ #include <usb.h> +static struct usb_dev_handle *hdl; + static struct usb_device *find_usb_device (uint16_t vendor_id, uint16_t product_id) { struct usb_bus *bus; @@ -46,8 +48,6 @@ static struct usb_device *find_usb_device (uint16_t vendor_id, uint16_t product_ struct usb_dev_handle *usb_find_open(uint16_t vendor_id, uint16_t product_id) { struct usb_device *dev; - struct usb_dev_handle *hdl; - usb_init(); usb_find_busses(); usb_find_devices(); @@ -56,7 +56,7 @@ struct usb_dev_handle *usb_find_open(uint16_t vendor_id, uint16_t product_id) if (!dev) { fprintf(stderr, "Cannot find matching USB Device. " "Are you sure it is connected?\n"); - exit(1); + return NULL; } hdl = usb_open(dev); @@ -74,3 +74,12 @@ struct usb_dev_handle *usb_find_open(uint16_t vendor_id, uint16_t product_id) return hdl; } + +struct usb_dev_handle *usb_find_reopen(uint16_t vendor_id, uint16_t product_id) +{ + if (hdl) { + usb_detach_kernel_driver_np(hdl, 0); + } + + return usb_find_open(vendor_id, product_id); +} diff --git a/host/usb_helper.h b/host/usb_helper.h index 13f96f8..0a9714c 100644 --- a/host/usb_helper.h +++ b/host/usb_helper.h @@ -22,5 +22,6 @@ #include <stdint.h> struct usb_dev_handle *usb_find_open(uint16_t vendor_id, uint16_t product_id); +struct usb_dev_handle *usb_find_reopen(uint16_t vendor_id, uint16_t product_id); #endif

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace