1111-------What was done is followed the instruction of this website:
http://sourceforge.net/apps/mediawiki/i … 00_Multim\
edia_Sensorboard

2222-------The main steps is:
# I2C
cd /lib/modules/2.6.29.1.rc1_1/kernel/drivers/i2c/algos
insmod i2c-algo-bit.ko
cd ../busses
insmod i2c-gpio.ko

# CAMERA
cd /lib/modules/2.6.29.1_r1.1/kernel/drivers/media/video
insmod videobuf-core.ko
insmod videodev.ko
insmod v4l2-common.ko
insmod v4l2-int-device.ko
insmod videobuf-dma-sg.ko
insmod soc_camera.ko
insmod pxa_camera.ko
insmod ov7670_soc.ko

mknod /dev/video0 c 81 0

3333-------and i can get the /dev/video0 appeared, however ,when i tried:
capture -d/dev/video0

the message comes out like this:
[root@SG2-3 webcam]#./capture -d /dev/video0
Can't open device /dev/video0

4444-------The same result comes out again when i wrote a c program to test the drivers by
myself :
[root@SG2-3 /root]#./cameraTest
v4l_open:: No such device or address

5555-------If anyone has any experience ,suggestions or knows how to solve it ,please give
me a hand . Thanks million in advance!!!

Starry

will be happy to answer any questions or even upload photos on request.

   As far as I can see, at the moment the proxmark would not be able to snoop on 125kHz communications between tags & readers: am I missing something there? I'd like to be able to do this to better understand some weird 125kHz tags I have... Do you think it would be possible to implement this type of feature without touching the FPGA code ?

Ed

I've just checked in a new version of the proxmark3 client into the google code repo (http://code.google.com/p/proxmark3/)

New functions:

em410xread [clock (optional, should always be 64 anyway)] -- Reads the ID from an EM410x tag (the plot should contain the raw tag).
Example:
> loread
> losamples 2000
> em410xread
Auto-detected clock rate: 64
EM410x Tag ID: 1a0041375d

em410xsim [tag id] -- Simulates an EM410x tag with the specified ID.
Example:
> em410xsim 1a0041375d
(The orange light will turn on. Press the button on the PM3 to stop emulating the tag.)

em410xwatch -- Watches for an EM410x tag until it detects one. Essentially "loread + losamples 2000 + em410xread" until a tag is detected.
Example:
> em410xwatch
Auto-detected clock rate: 64
EM410x Tag ID: 1a0041375d

manmod [clock (optional)] -- This will Manchester modulate the graphed bitstream. It's a helper function for em410xsim but can be re-used.

detectclock -- This function will auto-detect the clock rate.
Example:
> detectclock
Auto-detected clock rate: 64

bitstream [clock (optional)] -- Converts a waveform into a bitstream. The number of "samples" is still the same but it's easier to read a stream. I've only tested this using EM4102 tags.

Other Features:

Auto-detection of clock rate -- You'll notice in most functions, clock rate is auto-detected now.

prox.exe offline -- An offline mode is now available in the Windows client. You can use this to examine or work with older traces.

mandemod update -- Mandemod no longer requires specifying a clock rate and no longer requires askdemod being run first.

askdemod update -- Askdemod no longer requires specifying a clock rate.

traces/ directory -- I've included a traces/ directory in the repository containing some traces of my EM4102 tags. Might be useful to others to see or use them.

Let me know if you have any issues/questions!

When I go to the dir I get this:
bt4:~/proxmark3/linux/proxmark3-read-only# make
make -C bootrom all
make[1]: Entering directory `/root/proxmark3/linux/proxmark3-read-only/bootrom'
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I. -mthumb -mthumb-interwork -o obj/version.o version.c
make[1]: arm-eabi-gcc: Command not found
make[1]: *** [obj/version.o] Error 127
make[1]: Leaving directory `/root/proxmark3/linux/proxmark3-read-only/bootrom'
make: *** [bootrom/all] Error 2

I just uploaded a binary beta release
http://proxmark3.googlecode.com/files/p … s_beta.zip

if you guys (well, people with some knowledge, because there are no documentation yet) could give it a try, if possible from a pristine windows (so I know whether or not I forgot some DLLs), that'd be great.

to flash the proxmark with it, just use:
flasher.exe ..\arm\fullimage.elf
from the bin directory.

Let me know how it goes...

(on a pristine windows computer, you'll *first* have to install the proxmark driver I included, since it will install the libusb0 DLL. The installation procedure *will* be documented of course...)

Edit: A bootrom is included. If someone (with JTAG ^^) can test it as well...

Edit2: I have updated the link to the beta version

Ed

However, I then decided to further explore the commands available in the Help system, to see what they all did.  At some point the traces STOPPED looking like the article...  So I did a device reset, and still, the same commands with the same card no longer produce any meaningful output!  I still get a significant tune voltage drop when the card is on the antenna, but the data plot output is not all nice like it used to be.  Sadly I didn't save the trace when it was nice, but it really looked exactly like this, from that tutorial:

Now here's what it looks like, it varies between these two patterns.  I've included trace files:

http://www.mediafire.com/file/yezng25tjzy/%20badtrace Trace file 1

http://www.mediafire.com/file/mit3j42ykjw/%20badtrace2 Trace file 2

Any suggestions on getting that nice mode back?
Thank you
CSM

I have an unknown HF tag. It is not ISO14443 nor ISO15693. What can I do with the Proxmark to determine the type of the tag ? Is it possible to sniff the communications between the tag and a legitimate reader ?

Am preparing my list of RFID accessories to complete the fun :-) ! I wanna get a Q5 tag kit, but their website (http://www.cyntag.com/Starter%20Kits.htm) doesn't state from where to purchase them!

So, any guidance on that?

Thank you.

It's easy to construct some ?
Could some one send-me the schematic or some help on that ?

I've got the budget to buy the equipment, but now the antennas are sale out...

Thanks,
RSilva.

I am running into problems, when issuing the command "data plot" in my proxmark3 binary compiled with the lates svn sources on linux kernel 2.6.31-20 with libqt4-dev present. Compilation runs without errors:

(....)
g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui   -Wall -O3 -c -o obj/proxgui.o proxgui.cpp
g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui   -Wall -O3 -c -o obj/proxguiqt.o proxguiqt.cpp
/usr/bin/moc-qt4 -oproxguiqt.moc.cpp proxguiqt.h
g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui   -Wall -O3 -c -o obj/proxguiqt.moc.o proxguiqt.moc.cpp
g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui   -Wall -O3 obj/proxmark3.o obj/crc16.o obj/iso14443crc.o obj/data.o obj/graph.o obj/ui.o obj/cmddata.o obj/cmdhf.o obj/cmdhf14a.o obj/cmdhf14b.o obj/cmdhf15.o obj/cmdhflegic.o obj/cmdhw.o obj/cmdlf.o obj/cmdlfem4x.o obj/cmdlfhid.o obj/cmdlfti.o obj/cmdparser.o obj/cmdmain.o obj/proxusb.o obj/proxgui.o obj/proxguiqt.o obj/proxguiqt.moc.o -L/opt/local/lib -L/usr/local/lib -lusb -lreadline -lpthread -lQtGui -lQtCore   -o proxmark3
(....)

The binary works perfectly well - until it comes to the point where I want to plot the data. Here I get a buffer overflow with the following Backtrace:

proxmark3> data plot
proxmark3> *** buffer overflow detected ***: ./proxmark3 terminated
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x75ced8]
/lib/tls/i686/cmov/libc.so.6[0x75bf10]
/lib/tls/i686/cmov/libc.so.6[0x75b648]
/lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0x6e559e]
/lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0xe1c)[0x6b995c]
/lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xad)[0x75b6fd]
/lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0x75b63d]
./proxmark3[0x805798c]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x524)[0xa65dd4]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xb4)[0xa10f54]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xda)[0xa185ca]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x7b)[0x5886cb]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x525)[0xa6de25]
/usr/lib/libQtGui.so.4[0xbfc2f8]
/usr/lib/libQtGui.so.4[0xbfc77a]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate16syncBackingStoreERK7QRegion+0x65)[0xa5f055]
/usr/lib/libQtGui.so.4[0xa77090]
/usr/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x1462)[0xa856f2]
/usr/lib/libQtGui.so.4[0xab2502]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f8)[0x7f9e88]
/lib/libglib-2.0.so.0[0x7fd730]
/lib/libglib-2.0.so.0(g_main_context_iteration+0x73)[0x7fd863]
/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c)[0x5b302c]
/usr/lib/libQtGui.so.4[0xab1be5]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x49)[0x586c79]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa)[0x5870ca]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xaf)[0x58953f]
/usr/lib/libQtGui.so.4(_ZN12QApplication4execEv+0x27)[0xa10dd7]
./proxmark3[0x8055c07]
./proxmark3[0x804b49f]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692b56]
./proxmark3[0x804b391]

Has anybody here an idea how to solve this problem?!

Any help is greatly appreciated!

Regards,
Tom

i was wondering, since the Hitag2 algorithm is practically the same as crypto1, is there anyone who has modified crapto1 to crack hitag2 keys? As far as I can tell, one would need to change some constants, but does hitag2 possess the same weaknesses as crypto1?

All the parts required to build it can be obtained from 3 suppliers, PCB from batchpcb.com (3 weeks lead), LCD from sparkfun.com (1 week) everything else from Digikey.com (1 week).

Read the readme file, any other questions, post them here on the forum and I'll answer them. As I've said before, I've built this already and field tested it without any real issues but I sent the assembled device to someone. I have more parts coming next week to make another one for myself.

I understand that most people don't want to make their own due to the difficulty of soldering small parts. I'm half thinking at looking into getting some assembled. If for argument's sake a complete board cost, say $350 USD (same as the original PM3) would you consider purchasing?