simtrace

simtrace@lists.osmocom.org

350 discussions

[PATCH] eabi: Remove EABI functions to fix building with EABI toolchains
by Holger Hans Peter Freyther 08 Apr '12

08 Apr '12

These symbols are not referenced on an arm-elf gcc 4.7, they are used when building with an arm-eabi gcc 4.7 and then cause linking issues. The linking to libgcc can not be omitted as the irq code is using ffs. Remove the EABI symbols. The alternative would be to declare the EABI as weak inside the lib1funcs. Link error: multiple definition of `__udivsi3' multiple definition of `__aeabi_uidiv' Exported symbols: nm lib/lib1funcs.o 00000000 t Ldiv0 00000010 T __div0 --- firmware/lib/lib1funcs.S | 99 ---------------------------------------------- 1 file changed, 99 deletions(-) diff --git a/firmware/lib/lib1funcs.S b/firmware/lib/lib1funcs.S index 92a6c56..87890db 100644 --- a/firmware/lib/lib1funcs.S +++ b/firmware/lib/lib1funcs.S @@ -205,105 +205,6 @@ Boston, MA 02111-1307, USA. */ .endm -ENTRY(__udivsi3) -ENTRY(__aeabi_uidiv) - - subs r2, r1, #1 - moveq pc, lr - bcc Ldiv0 - cmp r0, r1 - bls 11f - tst r1, r2 - beq 12f - - ARM_DIV_BODY r0, r1, r2, r3 - - mov r0, r2 - mov pc, lr - -11: moveq r0, #1 - movne r0, #0 - mov pc, lr - -12: ARM_DIV2_ORDER r1, r2 - - mov r0, r0, lsr r2 - mov pc, lr - - -ENTRY(__umodsi3) - - subs r2, r1, #1 @ compare divisor with 1 - bcc Ldiv0 - cmpne r0, r1 @ compare dividend with divisor - moveq r0, #0 - tsthi r1, r2 @ see if divisor is power of 2 - andeq r0, r0, r2 - movls pc, lr - - ARM_MOD_BODY r0, r1, r2, r3 - - mov pc, lr - - -ENTRY(__divsi3) -ENTRY(__aeabi_idiv) - - cmp r1, #0 - eor ip, r0, r1 @ save the sign of the result. - beq Ldiv0 - rsbmi r1, r1, #0 @ loops below use unsigned. - subs r2, r1, #1 @ division by 1 or -1 ? - beq 10f - movs r3, r0 - rsbmi r3, r0, #0 @ positive dividend value - cmp r3, r1 - bls 11f - tst r1, r2 @ divisor is power of 2 ? - beq 12f - - ARM_DIV_BODY r3, r1, r0, r2 - - cmp ip, #0 - rsbmi r0, r0, #0 - mov pc, lr - -10: teq ip, r0 @ same sign ? - rsbmi r0, r0, #0 - mov pc, lr - -11: movlo r0, #0 - moveq r0, ip, asr #31 - orreq r0, r0, #1 - mov pc, lr - -12: ARM_DIV2_ORDER r1, r2 - - cmp ip, #0 - mov r0, r3, lsr r2 - rsbmi r0, r0, #0 - mov pc, lr - - -ENTRY(__modsi3) - - cmp r1, #0 - beq Ldiv0 - rsbmi r1, r1, #0 @ loops below use unsigned. - movs ip, r0 @ preserve sign of dividend - rsbmi r0, r0, #0 @ if negative make positive - subs r2, r1, #1 @ compare divisor with 1 - cmpne r0, r1 @ compare dividend with divisor - moveq r0, #0 - tsthi r1, r2 @ see if divisor is power of 2 - andeq r0, r0, r2 - bls 10f - - ARM_MOD_BODY r0, r1, r2, r3 - -10: cmp ip, #0 - rsbmi r0, r0, #0 - mov pc, lr #ifdef CONFIG_AEABI -- 1.7.9.5

3 2

Unable to compile firmware
by Marnix Janse 07 Apr '12

07 Apr '12

Greetings to you all. This is my first message to this mailinglist. I received the SIMtrace hardware this week and I seem to get stuck at the point of making the firmware at this point: make BOARD=SIMTRACE DEBUG=1 TARGET=main_simtrace I am following the usernamual2.pdf,and I am trying to use my head, so far without too much success. The step before that is going fine: make -f Makefile.dfu BOARD=SIMTRACE Can anyone point me in the right direction on what toolchain to use and help me with the make-ussues below? Thank you, Marnix ------------------------------------------------------------------------------------------------------------------------------------------------ - I tried: - Linux-builds: CentOS 6.2 64-bitsVM, a CentOS 6.2 32-bitsVM and finally an Ubuntu 11.10 32-bits VM. - ARM-toolchain: GNU-arm (from the Wiki) and the CodeSourcery (advised at the openpcd website) - Result: With GNUarm: marnix@ubuntu:~/openpcd/firmware$ make BOARD=SIMTRACE DEBUG=1 TARGET=main_simtrace -------- begin (mode: RUN_FROM_ROM) -------- arm-elf-gcc (GCC) 3.4.3 Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Assembling (ARM-only): src/start/Cstartup_app.S arm-elf-gcc -c -mcpu=arm7tdmi -I. -x assembler-with-cpp -DRUN_FROM_ROM -D__AT91SAM7S128__ -Wa,-adhlns=src/start/Cstartup_app.lst,--gdwarf-2 -Iinclude/ -D__ASSEMBLY__ src/start/Cstartup_app.S -o src/start/Cstartup_app.o /home/marnix/gnuarm/bin/../lib/gcc/arm-elf/3.4.3/../../../../arm-elf/bin/as: unrecognized option '--gdwarf-2' make: *** [src/start/Cstartup_app.o] Error 1 When I change DEBUG-format from dwarf-2 to stabs I get this error: DEBUGF = stabs #DEBUGF = dwarf-2 Linking: main_simtrace.elf arm-elf-gcc -mcpu=arm7tdmi -I. -gstabs -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DDEBUG -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -O2 -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow - Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/start/Cstartup_app.lst -I../../librfid//include/ -ffunction-sections -fdata-sections -MD -MP -MF .dep/main_simtrace.elf.d src/start/Cstartup_app.o lib/changebit.o lib/clearbit.o lib/setbit.o lib/testchangebit.o lib/testclearbit.o lib/testsetbit.o lib/lib1funcs.o lib/div64.o lib/lib_AT91SAM7.o lib/vsprintf.o lib/ctype.o lib/string.o src/os/pcd_enumerate.o src/os/fifo.o src/os/dbgu.o src/os/led.o src/os/req_ctx.o src/os/trigger.o src/os/main.o src/os/syscalls.o src/os/usb_handler.o src/os/usb_benchmark.o src/os/tc_cdiv.o src/os/pit.o src/os/pwm.o src/os/pio_irq.o src/os/usbcmd_generic.o src/os/wdt.o src/os/blinkcode.o src/os/system_irq.o src/os/flash.o src/simtrace/iso7816_uart.o src/simtrace/tc_etu.o src/simtrace/sim_switch.o src/simtrace/spi_flash.o src/simtrace/main_simtrace.o --output main_simtrace.elf - nostartfiles -Wl,-Map=main_simtrace.map,--cref -lc -lgcc -L../../librfid//src/.libs/ -Wl,--gc-sections -Wl,--entry=_startup -Tlink/AT91SAM7S128-ROM-sam7dfu-app.ld src/simtrace/sim_switch.o(.bss.stats+0x0): In function `sim_switch_init': src/simtrace/sim_switch.c:69: multiple definition of `stats' src/simtrace/iso7816_uart.o(.bss.stats+0x0):src/simtrace/iso7816_uart.c:668: first defined here src/simtrace/spi_flash.o(.bss.stats+0x0): In function `spiflash_id': src/simtrace/spi_flash.c:137: multiple definition of `stats' src/simtrace/iso7816_uart.o(.bss.stats+0x0):src/simtrace/iso7816_uart.c:668: first defined here src/simtrace/main_simtrace.o(.bss.stats+0x0): In function `_main_func': src/simtrace/main_simtrace.c:220: multiple definition of `stats' src/simtrace/iso7816_uart.o(.bss.stats+0x0):src/simtrace/iso7816_uart.c:668: first defined here collect2: ld returned 1 exit status make: *** [main_simtrace.elf] Error 1 With CodeSourceryARM-toolchain: Linking: main_simtrace.elf arm-none-eabi-gcc -mcpu=arm7tdmi -I. -gdwarf-2 -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DDEBUG -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -O2 -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type - Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/start/Cstartup_app.lst -I../../librfid//include/ -ffunction-sections -fdata-sections -MD -MP -MF .dep/main_simtrace.elf.d src/start/Cstartup_app.o lib/changebit.o lib/clearbit.o lib/setbit.o lib/testchangebit.o lib/testclearbit.o lib/testsetbit.o lib/lib1funcs.o lib/div64.o lib/lib_AT91SAM7.o lib/vsprintf.o lib/ctype.o lib/string.o src/os/pcd_enumerate.o src/os/fifo.o src/os/dbgu.o src/os/led.o src/os/req_ctx.o src/os/trigger.o src/os/main.o src/os/syscalls.o src/os/usb_handler.o src/os/usb_benchmark.o src/os/tc_cdiv.o src/os/pit.o src/os/pwm.o src/os/pio_irq.o src/os/usbcmd_generic.o src/os/wdt.o src/os/blinkcode.o src/os/system_irq.o src/os/flash.o src/simtrace/iso7816_uart.o src/simtrace/tc_etu.o src/simtrace/sim_switch.o src/simtrace/spi_flash.o src/simtrace/main_simtrace.o --output main_simtrace.elf -nostartfiles -Wl,-Map=main_simtrace.map,--cref -lc -lgcc -L../../librfid//src/.libs/ -Wl,--gc-sections -Wl,--entry=_startup -Tlink/AT91SAM7S128-ROM-sam7dfu-app.ld /root/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_EABI/bin/../lib/gcc/arm-none-eabi/4.6.1/libgcc.a(_udivsi3.o): In function `__aeabi_uidiv': (.text+0x0): multiple definition of `__udivsi3' lib/lib1funcs.o:/root/openpcd/firmware/lib/lib1funcs.S:183: first defined here /root/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_EABI/bin/../lib/gcc/arm-none-eabi/4.6.1/libgcc.a(_udivsi3.o): In function `__aeabi_uidiv': (.text+0x0): multiple definition of `__aeabi_uidiv' lib/lib1funcs.o:/root/openpcd/firmware/lib/lib1funcs.S:183: first defined here collect2: ld returned 1 exit status make: *** [main_simtrace.elf] Error 1

3 6

New v0.5 simtrace firmware release
by Harald Welte 26 Mar '12

26 Mar '12

Hi all! Just in time before OsmoDevCon, I managed to releaes a new version of the SIMtrace firmware. The list of changes is quite extensive and should address a number of the reliability problems that people have experienced. The changes include: * don't activate pass-through and LDO supply for the sim card at the same time, leading in power leaking from simtrace into phones * fix a watchdog timer misconfiguration leading to occasional watchdog resets * fix detection of sim insert/removal * better VCC_PHONE detection * reduce the amount of debug logging on the serial console and replace it by statistics (count of bytes, overruns, parity errors, etc) * statistics can be read from the UART by pressing 't'. * no longer crash the simtrace firmware if no simtrace host program is running Using this v0.5 firmware and a pretty aggressiv program causing lots of traffic (hunz' simdump) on a cm3121 reader at card Fi(9) Di(4) ratio 64 didn't cause any lost bytes or SIMtrace resets for me anymore. Any feedback is appreciated. 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)

3 7

question
by Krzysztof Zajac 26 Mar '12

26 Mar '12

Hello, I'm interesting of this device to sniff APDUs. Can we talk a bit more details? BR Krzysztof Z.

2 1

Loosing 1 byte on each chunk of URB transfer
by Myonium 21 Mar '12

21 Mar '12

Hi It seems to me that simtrace looses a byte between 2 URB transfers from the device. To trace the problem down, I wrote a little test-program, running the same APDU against the smart card. I’m using simtrace to trace the card on the HW level and at the very same time I trace on the PCSC layer of the OS. Of cause the 2 APDU traces should give exactly the same results. Surprisimgly I found that the simtrace is swallowing one byte between two URB chunks transferred. Please find below the 2 logs A.) PCSC trace, B.) simtrace output. In this example simtrace is missing 1 byte (“7F”) between the two URB chunks a.) and b.). This missing byte causes to scrow up the analyser (APDU number 5). The same problem occurs also between the next two URB chunks b.) and c.): This time a “00” gets lost ... etc etc. A.) The PCSC traces as reference: ======================================= 1.) transmitted: 80 C2 00 00 28 D8 00 01 6F 00 F5 EF BF B1 8C 76 16 00 0E 43 6F 6E 74 65 6E 74 4D 61 6E 61 67 65 72 00 C0 4B 4E 7F BD 00 04 4D 53 43 4D received: 61 05 2.) transmitted: 00 C0 00 00 05 received: 01 00 00 00 05 90 00 3.) transmitted: 80 C2 00 00 12 D8 00 05 6F 00 C0 4B 4E 7F BD DE EC 00 04 4D 53 43 4D received: 61 0F 4.) transmitted: 00 C0 00 00 0F received: 00 D2 5D 1C 11 27 00 07 37 2E 31 2E 30 2E 30 90 00 5.) transmitted: 80 C2 00 00 14 D8 00 05 6F 00 C0 4B 4E 7F BD 81 87 00 04 4D 53 43 4D 05 00 received: 61 1A 6.) transmitted: 00 C0 00 00 1A received: 00 D2 5D 1C 45 A3 00 00 00 10 2E 4E 45 54 57 01 13 51 21 9C 77 14 27 14 FF FF 90 00 7.) transmitted: 80 C2 00 00 12 D8 00 05 6F 00 C0 4B 4E 7F BD FA 3B 00 04 4D 53 43 4D received: 61 12 8.) transmitted: 00 C0 00 00 12 received: 00 D2 5D 1C 45 A3 00 00 00 08 83 17 65 55 19 7E A5 EB 90 00 9.) transmitted: 80 C2 00 00 1E D8 00 05 6F 00 C0 4B 4E 7F BD 24 FE 00 04 4D 53 43 4D 00 00 00 08 FC 66 34 93 BD 58 68 54 received: 90 00 10.) transmitted: 80 C2 00 00 13 D8 00 05 6F 00 C0 4B 4E 7F BD 6D 08 00 04 4D 53 43 4D 02 received: 61 0A 11.) transmitted: 00 C0 00 00 0A received: 00 D2 5D 1C 61 C0 00 00 00 05 90 00 B.) The simtrace output: ================================================ simtrace - GSM SIM and smartcard tracing (C) 2010 by Harald Welte <laforge(a)gnumonks.org> Entering main loop URB: 01 01 00 00 3b 16 96 41 73 74 72 69 64 ATR APDU: 3b 16 96 41 73 74 72 69 64 a.) URB: 01 00 00 00 80 c2 00 00 28 c2 d8 00 01 6f 00 f5 ef bf b1 8c 76 16 00 0e 43 6f 6e 74 65 6e 74 4d 61 6e 61 67 65 72 00 c0 4b 4e 7f bd 00 04 4d 53 43 4d 61 05 00 c0 00 00 05 c0 01 00 00 00 05 90 00 80 c2 00 00 12 c2 d8 00 05 6f 00 c0 4b 4e 7f bd de ec 00 04 4d 53 43 4d 61 0f 00 c0 00 00 0f c0 00 d2 5d 1c 11 27 00 07 37 2e 31 2e 30 2e 30 90 00 80 c2 00 00 14 c2 d8 00 05 6f 00 c0 4b 4e 1.) APDU: 80 c2 00 00 28 d8 00 01 6f 00 f5 ef bf b1 8c 76 16 00 0e 43 6f 6e 74 65 6e 74 4d 61 6e 61 67 65 72 00 c0 4b 4e 7f bd 00 04 4d 53 43 4d 61 05 2.) APDU: 00 c0 00 00 05 01 00 00 00 05 90 00 3.) APDU: 80 c2 00 00 12 d8 00 05 6f 00 c0 4b 4e 7f bd de ec 00 04 4d 53 43 4d 61 0f 4.) APDU: 00 c0 00 00 0f 00 d2 5d 1c 11 27 00 07 37 2e 31 2e 30 2e 30 90 00 b.) URB: 01 00 00 00 bd 81 00 04 4d 53 43 4d 05 00 61 1a 00 c0 00 00 1a c0 00 d2 5d 1c 45 a3 00 00 00 10 2e 4e 45 54 57 01 13 51 21 9c 77 14 27 14 ff ff 90 00 80 c2 00 00 12 c2 d8 00 05 6f 00 c0 4b 4e 7f bd fa 3b 00 04 4d 53 43 4d 61 12 00 c0 00 00 12 c0 00 d2 5d 1c 45 a3 00 00 00 08 83 17 65 55 19 7e a5 eb 90 00 80 c2 00 00 1e c2 d8 00 05 6f 00 c0 4b 4e 7f bd 24 fe 00 04 4d 53 43 4d 00 00 5.) APDU: 80 c2 00 00 14 d8 00 05 6f 00 c0 4b 4e bd 81 00 04 4d 53 43 4d 05 00 61 1a 00 c0 APDU: 00 00 1a c0 00 d2 5d APDU: 1c 45 a3 00 00 00 10 APDU: 2e 4e 45 54 57 01 13 APDU: 51 21 9c 77 14 27 14 APDU: ff ff 90 00 80 c2 00 APDU: 00 12 c2 d8 00 05 6f APDU: 00 c0 4b 4e 7f bd fa APDU: 3b 00 04 4d 53 43 4d APDU: 61 12 00 c0 00 00 12 APDU: c0 00 d2 5d 1c 45 a3 APDU: 00 00 00 08 83 17 65 APDU: 55 19 7e a5 eb 90 00 c.)URB: 01 04 00 00 08 fc 66 34 93 bd 58 68 54 d.)URB: 01 04 00 00 90 00 80 c2 00 00 13 c2 d8 00 05 6f 00 c0 4b 4e 7f bd 6d 08 00 04 4d 53 43 4d 02 61 0a 00 c0 00 00 0a c0 00 d2 5d 1c 61 c0 00 00 00 05 90 00 APDU: 80 c2 00 00 1e d8 00 05 6f 00 c0 4b 4e 7f bd 24 fe 00 04 4d 53 43 4d 00 00 08 fc 66 34 93 bd 58 68 54 90 00 80 APDU: c2 00 00 13 c2 d8 00 APDU: 05 6f 00 c0 4b 4e 7f APDU: bd 6d 08 00 04 4d 53 APDU: 43 4d 02 61 0a 00 c0 APDU: 00 00 0a c0 00 d2 5d APDU: 1c 61 c0 00 00 00 05 URB: 01 01 00 00 3b 16 96 41 73 74 72 69 64 ATR APDU: 3b 16 96 41 73 74 72 69 64 ========================================================== Is this a problem of simtrace or the firmware? Am I using a wrong firmware? Thanks, Ben

5 19

SIM Trace Appears to Stop Processing APDUs
by Jonathan Thomas 21 Mar '12

21 Mar '12

Environment: We have tested on three systems with both Ubuntu and OpenSUSE. Additionally, we have tested with both VMs and as a core system install. Software Installed: Installed the latest using the instructions from the user manual. Issue: With testing against all three of the SIMTrace modules we purchased we have found the trace appears to lock-up or freeze randomly through processing of the APDUs. Since the phone still functions properly I am assuming that the communication between the SIM and the phone are still intact, it is just an issue with the output to screen/file output. Has anyone else experienced this issue? We will try and flash the firmware, but since we saw this issue with all of the hardware we purchased we assumed there might be some other issue. Thank you. Jonathan

4 7

sysmosim - Greencard
by Arjen Smit 09 Mar '12

09 Mar '12

Dear all, Hopefully this is the right list for some questions on the SysmoSIM (aka Greencard). I have set the PIN1, PUK1, PIN1, PUK1, ADM1, AUK1, ADM2, AUK2 using the non-standard APDU (80 D4 ..) successfully using the cyberflex-shell. Verification of CHV1 and CHV2 are fine as well. (A0 20 00 01 08 ...) However verification of ADM2 (which I need because I want to change the Authentication algorithm) A0 20 00 0B 08 30 30 30 30 30 30 30 30 returns status : 98 02 (no chv initialized). It looks like I use the wrong APDU sequence for verifying ADM2 (I tried some other sequences as well (e.g A0 20 00 0A .. to A0 20 00 0D ..) but no luck. My main question is : What APDU sequence is needed to verify ADM2 ? Secondary less important questions: -When thinking about AUK1, AUK2, what are these used for ? -Do the cards support 03.48 OTA specs (if yes, can the Kic, Kid be set ?) -Are there actually any specs of these cards available ? (google gives www.elektroda.pl/rtvforum/download.php?id=351846 which matches the ATR of the card, however this spec is of little use though). Thanks in advance for your help. /Arjen

2 2

What can be logged?
by Florian Borggräfe 06 Mar '12

06 Mar '12

Hello, i have a question about the functionality of the Osmoscon SimTrace hardware system. Can I log everything, also packets like silent SMS (https://en.wikipedia.org/wiki/SMS#Silent_SMS)? Thank you for your request. Flo

3 3

1.1p board not recognized
by Martin Kaiser 19 Feb '12

19 Feb '12

Dear all, I'm struggling to get started with a 1.1p board. When I connect it via USB (with no simcard inserted and no connection to a phone), the red led is on. Sometimes, both leds remain off after connecting the board when I have a simcard inserted and a phone connected. On one box (debian lenny), the board is never recognized by lsusb or kernel messages. Do I need anything special (other than basic usb support) compiled into the kernel for libusb to do its work in user space? I tried dfu-util -l, the board wasn't listed. On a second box (debian squeeze) there's log messages when the usb is connected Feb 15 22:34:44 greta kernel: [186232.651806] usb 1-1.1: new full speed USB device using ehci_hcd and address 13 Feb 15 22:34:44 greta kernel: [186232.745566] usb 1-1.1: New USB device found, idVendor=16c0, idProduct=0762 Feb 15 22:34:44 greta kernel: [186232.745573] usb 1-1.1: New USB device strings: Mfr=4, Product=5, SerialNumber=0 Feb 15 22:34:44 greta kernel: [186232.745577] usb 1-1.1: Product: SimTrace SIM Sniffer - Runtime Mode Feb 15 22:34:44 greta kernel: [186232.745581] usb 1-1.1: Manufacturer: sysmocom - systems for mobile communications GmbH Feb 15 22:34:44 greta kernel: [186232.745694] usb 1-1.1: configuration #1 chosen from 1 choice lsusb doesn't show anything either the red led is on after connecting, simtrace (linked against libusb-1.0) says "can't open USB device" After some more tries, dfu-util recognizes the board root@greta:~# dfu-util -l dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Found DFU: [0x16c0:0x0762] devnum=17, cfg=0, intf=0, alt=0, name="SimTrace DFU Interface - Application Partition" Found DFU: [0x16c0:0x0762] devnum=17, cfg=0, intf=0, alt=1, name="SimTrace DFU Interface - Bootloader Partition" Found DFU: [0x16c0:0x0762] devnum=17, cfg=0, intf=0, alt=2, name="SimTrace DFU Interface - RAM" However, I'm not able to write a firmware. I tried the main_simtrace.bin that Harald posted to this list some days ago. root@greta:~# dfu-util -d 16c0:0762 -a0 -D /home/martin/tmp/main_simtrace.bin -R dfu-util - (C) 2007-2008 by 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... Found Runtime: [0x16c0:0x0762] devnum=17, cfg=0, intf=0, alt=0, name="SimTrace DFU Interface - Application Partition" Claiming USB DFU Interface... Setting Alternate Setting #0 ... Determining device status: state = dfuERROR, status = 8 dfuERROR, clearing status Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x0100 bytes_per_hash=417 Starting download: [#################################################dfu_download: usb_control_msg returned -32: error sending control message: Broken pipe Error during download Retrying multiple times, I always get the same error. I tried resetting the board with the bootloader button pressed, this didn't change anything. While trying to flash the firmware, there was no sim inserted and no phone connected. Does anyone have an idea what else I can try to track down the problems and get the board up and running? Thanks in advance, Martin

3 5

Corrupted git repository?
by Myonium 16 Feb '12

16 Feb '12

Hi I’m not very familiar with git, but there is something strange with the git repository “git://git.gnumonks.org/openpcd.git”: First of all the the identical revision number “4f7ca20bf40b911c035264d86ef0359d20e7ac88” appears several times: git rev-parse --all 4f7ca20bf40b911c035264d86ef0359d20e7ac88 4f7ca20bf40b911c035264d86ef0359d20e7ac88 4f7ca20bf40b911c035264d86ef0359d20e7ac88 f49cbc1f2503f737a96296993133aec065910935 4f7ca20bf40b911c035264d86ef0359d20e7ac88 3aa065ac48f21ce7c4d0879686fb07b04a60771f 45c13574ff89e3139567943e6a6cae82e754eab0 0febfc567d3f9441811a5490f0ea4d960798d313 Compiling “4f7ca20bf40b911c035264d86ef0359d20e7ac88” results in a not working firmware, even so the changes (PPS changes from Harald) are all correct. (I applied these changes to the v0.4 firmware (revision ebf16b4ddf0dcbadf96aebdec3304f703917fdc7) and it works all nicely.) Could somebody have a look ... Regards, Ben

1 0

← Newer
1
...
26
27
28
29
30
31
32
...
35
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace