51 (edited by CoolArts 2017-02-27 02:34:21)

Re: NFC tag emulator

I'm doing that way to simplify routes, I don't have avrdude installed on the system so I'm using the avrdude from Arduino.app.

If i use tinyisp everything seems to go well even verifications until eeprom verification:

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0x01 != 0x00
avrdude: verification error; content mismatch

But both files you post are readed and writed to emu:

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e920d (probably t4313)
avrdude: erasing chip
avrdude: reading input file "emutag/ntag213-sniff.bin"
avrdude: writing flash (3992 bytes):

Writing | ################################################## | 100% 6.33s

avrdude: 3992 bytes of flash written
avrdude: verifying flash memory against emutag/ntag213-sniff.bin:
avrdude: load data flash data from input file emutag/ntag213-sniff.bin:
avrdude: input file emutag/ntag213-sniff.bin contains 3992 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 7.11s

avrdude: verifying ...
avrdude: 3992 bytes of flash verified
avrdude: reading input file "emutag/common.eep"
avrdude: writing eeprom (256 bytes):

Writing | ################################################## | 100% 51.56s

avrdude: 256 bytes of eeprom written
avrdude: verifying eeprom memory against emutag/common.eep:
avrdude: load data eeprom data from input file emutag/common.eep:
avrdude: input file emutag/common.eep contains 256 bytes
avrdude: reading on-chip eeprom data:

Reading | ################################################## | 100% 7.21s

Do you know why eeprom verification step can be miserably failing?

avrdude: input file emutag/common.eep contains 256 bytes
avrdude: reading on-chip eeprom data:

Reading | ################################################## | 100% 7.21s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0x01 != 0x00
avrdude: verification error; content mismatch
XYZ Junior/Mini Passwords Thread
If you are in a hurry and need your password NOW, or if it takes me too long for you, you can read the posts from 1851. I'm not going to be as effective as Bozo or Cgrillo, but you can give a try with me. If PASSWORDS thread follow it's current flow: asking for repeated passwords, not returning or false PACKS... I will end up with it as others before me.

52

Re: NFC tag emulator

Yea, I got that error when I had the wrong device defined, but if you had tried the UNO then the device was correct. I just went back and checked my notes and when I fixed my device is when it worked. I am not sure what the device name is for your tiny. I will see if I can find something on that.

53

Re: NFC tag emulator

Check the avrdude.conf file for the different device types and see if one of those will work. I see a lot of tiny devices.

54

Re: NFC tag emulator

My avrdude.conf only allow me this programmers. I think that only USBTINY is for my USBtinyISP

Valid programmers are:
  2232HIO          = FT2232H based generic programmer [etc/avrdude.conf:412]
  4232h            = FT4232H based generic programmer [etc/avrdude.conf:440]
  arduino          = Arduino                        [etc/avrdude.conf:360]
  arduino-ft232r   = Arduino: FT232R connected to ISP [etc/avrdude.conf:764]
  arduinoisp       =                                [etc/avrdude.conf:878]
  atmelice         = Atmel-ICE (ARM/AVR) in JTAG mode [etc/avrdude.conf:1123]
  atmelice_dw      = Atmel-ICE (ARM/AVR) in debugWIRE mode [etc/avrdude.conf:1139]
  atmelice_isp     = Atmel-ICE (ARM/AVR) in ISP mode [etc/avrdude.conf:1147]
  atmelice_pdi     = Atmel-ICE (ARM/AVR) in PDI mode [etc/avrdude.conf:1131]
  avr109           = Atmel AppNote AVR109 Boot Loader [etc/avrdude.conf:894]
  avr910           = Atmel Low Cost Serial Programmer [etc/avrdude.conf:721]
  avr911           = Atmel AppNote AVR911 AVROSP    [etc/avrdude.conf:901]
  avrftdi          = FT2232D based generic programmer [etc/avrdude.conf:386]
  avrisp           = Atmel AVR ISP                  [etc/avrdude.conf:608]
  avrisp2          = Atmel AVR ISP mkII             [etc/avrdude.conf:628]
  avrispmkII       = Atmel AVR ISP mkII             [etc/avrdude.conf:622]
  avrispv2         = Atmel AVR ISP V2               [etc/avrdude.conf:615]
  buspirate        = The Bus Pirate                 [etc/avrdude.conf:633]
  buspirate_bb     = The Bus Pirate (bitbang interface, supports TPI) [etc/avrdude.conf:640]
  butterfly        = Atmel Butterfly Development Board [etc/avrdude.conf:887]
  butterfly_mk     = Mikrokopter.de Butterfly       [etc/avrdude.conf:915]
  bwmega           = BitWizard ftdi_atmega builtin programmer [etc/avrdude.conf:751]
  C232HM           = FT232H based module from FTDI and Glyn.com.au [etc/avrdude.conf:509]
  c2n232i          = serial port banging, reset=dtr sck=!rts mosi=!txd miso=!cts [etc/avrdude.conf:1278]
  dasa             = serial port banging, reset=rts sck=dtr mosi=txd miso=cts [etc/avrdude.conf:1250]
  dasa3            = serial port banging, reset=!dtr sck=rts mosi=txd miso=cts [etc/avrdude.conf:1264]
  diecimila        = alias for arduino-ft232r       [etc/avrdude.conf:775]
  dragon_dw        = Atmel AVR Dragon in debugWire mode [etc/avrdude.conf:1050]
  dragon_hvsp      = Atmel AVR Dragon in HVSP mode  [etc/avrdude.conf:1041]
  dragon_isp       = Atmel AVR Dragon in ISP mode   [etc/avrdude.conf:1023]
  dragon_jtag      = Atmel AVR Dragon in JTAG mode  [etc/avrdude.conf:1014]
  dragon_pdi       = Atmel AVR Dragon in PDI mode   [etc/avrdude.conf:1059]
  dragon_pp        = Atmel AVR Dragon in PP mode    [etc/avrdude.conf:1032]
  flip1            = FLIP USB DFU protocol version 1 (doc7618) [etc/avrdude.conf:1170]
  flip2            = FLIP USB DFU protocol version 2 (AVR4023) [etc/avrdude.conf:1177]
  ft232r           = FT232R Synchronous BitBang     [etc/avrdude.conf:739]
  ft245r           = FT245R Synchronous BitBang     [etc/avrdude.conf:728]
  jtag1            = Atmel JTAG ICE (mkI)           [etc/avrdude.conf:928]
  jtag1slow        = Atmel JTAG ICE (mkI)           [etc/avrdude.conf:933]
  jtag2            = Atmel JTAG ICE mkII            [etc/avrdude.conf:963]
  jtag2avr32       = Atmel JTAG ICE mkII im AVR32 mode [etc/avrdude.conf:996]
  jtag2dw          = Atmel JTAG ICE mkII in debugWire mode [etc/avrdude.conf:978]
  jtag2fast        = Atmel JTAG ICE mkII            [etc/avrdude.conf:957]
  jtag2isp         = Atmel JTAG ICE mkII in ISP mode [etc/avrdude.conf:969]
  jtag2pdi         = Atmel JTAG ICE mkII PDI mode   [etc/avrdude.conf:1005]
  jtag2slow        = Atmel JTAG ICE mkII            [etc/avrdude.conf:952]
  jtag3            = Atmel AVR JTAGICE3 in JTAG mode [etc/avrdude.conf:1067]
  jtag3dw          = Atmel AVR JTAGICE3 in debugWIRE mode [etc/avrdude.conf:1083]
  jtag3isp         = Atmel AVR JTAGICE3 in ISP mode [etc/avrdude.conf:1091]
  jtag3pdi         = Atmel AVR JTAGICE3 in PDI mode [etc/avrdude.conf:1075]
  jtagkey          = Amontec JTAGKey, JTAGKey-Tiny and JTAGKey2 [etc/avrdude.conf:447]
  jtagmkI          = Atmel JTAG ICE (mkI)           [etc/avrdude.conf:920]
  jtagmkII         = Atmel JTAG ICE mkII            [etc/avrdude.conf:944]
  jtagmkII_avr32   = Atmel JTAG ICE mkII im AVR32 mode [etc/avrdude.conf:987]
  lm3s811          = Luminary Micro LM3S811 Eval Board (Rev. A) [etc/avrdude.conf:570]
  mib510           = Crossbow MIB510 programming board [etc/avrdude.conf:672]
  mkbutterfly      = Mikrokopter.de Butterfly       [etc/avrdude.conf:909]
  nibobee          = NIBObee                        [etc/avrdude.conf:847]
  o-link           = O-Link, OpenJTAG from www.100ask.net [etc/avrdude.conf:541]
  openmoko         = Openmoko debug board (v3)      [etc/avrdude.conf:552]
  pavr             = Jason Kyle's pAVR Serial Programmer [etc/avrdude.conf:1156]
  pickit2          = MicroChip's PICkit2 Programmer [etc/avrdude.conf:1163]
  ponyser          = design ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts [etc/avrdude.conf:1228]
  siprog           = Lancos SI-Prog <http://www.lancos.com/siprogsch.html> [etc/avrdude.conf:1241]
  stk500           = Atmel STK500                   [etc/avrdude.conf:658]
  stk500hvsp       = Atmel STK500 V2 in high-voltage serial programming mode [etc/avrdude.conf:693]
  stk500pp         = Atmel STK500 V2 in parallel programming mode [etc/avrdude.conf:686]
  stk500v1         = Atmel STK500 Version 1.x firmware [etc/avrdude.conf:665]
  stk500v2         = Atmel STK500 Version 2.x firmware [etc/avrdude.conf:679]
  stk600           = Atmel STK600                   [etc/avrdude.conf:700]
  stk600hvsp       = Atmel STK600 in high-voltage serial programming mode [etc/avrdude.conf:714]
  stk600pp         = Atmel STK600 in parallel programming mode [etc/avrdude.conf:707]
  ttl232r          = FTDI TTL232R-5V with ICSP adapter [etc/avrdude.conf:811]
  tumpa            = TIAO USB Multi-Protocol Adapter [etc/avrdude.conf:591]
  UM232H           = FT232H based module from FTDI and Glyn.com.au [etc/avrdude.conf:482]
  uncompatino      = uncompatino with all pairs of pins shorted [etc/avrdude.conf:787]
  usbasp           = USBasp, http://www.fischl.de/usbasp/ [etc/avrdude.conf:822]
  usbasp-clone     = Any usbasp clone with correct VID/PID [etc/avrdude.conf:858]
  usbtiny          = USBtiny simple USB programmer, http://www.ladyada.net/make/usbtinyisp/ [etc/avrdude.conf:869]
  wiring           = Wiring                         [etc/avrdude.conf:353]
  xplainedmini     = Atmel AVR XplainedMini in ISP mode [etc/avrdude.conf:1107]
  xplainedmini_dw  = Atmel AVR XplainedMini in debugWIRE mode [etc/avrdude.conf:1115]
  xplainedpro      = Atmel AVR XplainedPro in JTAG mode [etc/avrdude.conf:1099]

http://soliforum.com/i/?u5AwxEm.jpg


I tried it with 4 or 5, but they don't give response (following [code.]), only USBtiny does.

avrdude: ser_open(): can't open device "unknown": No such file or directory

I have to work now, but this night I will try to do it again with the arduino UNO, I was wiring it as in the photo, reviewed a hundred times that was ok, i think yes (only 4+2 cables), but I could be blind as many times i was before.


http://soliforum.com/i/?wMXsqNl.jpg

Thank you very much!
Regards!.

XYZ Junior/Mini Passwords Thread
If you are in a hurry and need your password NOW, or if it takes me too long for you, you can read the posts from 1851. I'm not going to be as effective as Bozo or Cgrillo, but you can give a try with me. If PASSWORDS thread follow it's current flow: asking for repeated passwords, not returning or false PACKS... I will end up with it as others before me.

55 (edited by CoolArts 2017-03-12 15:59:22)

Re: NFC tag emulator

First of all sorry for this super looooong delay, I was in a high work period plus some personal things kept me out of the printer and the arduinos.

Today I retrieved the tests to try to restore the emu and everything went right. EMUTAG is working perfect again.

I want to thank a lot to Bozotclown him patience, instructions and files. Thank you very much Bozo!. I want to thank your efforts and patience as well Kaltt_Kaffe!!!

Finally the thing was exactly what you've told me, I had to choose another programmer, (in my case) arduino must be changed to stk500v1 (I readed that here: arduino.cc)

The final command that worked for me was:

bin/avrdude -c stk500v1 -p t4313 -P /dev/cu.usbmodem1411 -C etc/avrdude.conf -b 19200 -e -U flash:w:emutag/ntag213-sniff.bin:r -U eeprom:w:emutag/common.eep:r

Mac users must take into consideration that I run that command from this folder:

/Applications/Arduino.app/Contents/Java/Hardware/tools/avr/

Also I've created a folder named "emutag" inside that folder

/Applications/Arduino.app/Contents/Java/Hardware/tools/avr/emutag/

And copied there the files posted by Bozo "common.eep" & "ntag213-sniff.bin"


The command has been run with an Arduino UNO "Made in Italy" as ISP in macOS Sierra 10.12.3.

Thank you very much again Bozo & Kaltt!.

XYZ Junior/Mini Passwords Thread
If you are in a hurry and need your password NOW, or if it takes me too long for you, you can read the posts from 1851. I'm not going to be as effective as Bozo or Cgrillo, but you can give a try with me. If PASSWORDS thread follow it's current flow: asking for repeated passwords, not returning or false PACKS... I will end up with it as others before me.

56

Re: NFC tag emulator

CoolArts wrote:

Thank you very much again Bozo!.

You are more than welcome. I am glad I was able to head you in the right direction. Again, I am no brainiac, but I have spent a lot of time reading this stuff.

Glad you got it working again.

57

Re: NFC tag emulator

I'm not writing in forums, and less in a language I do not dominate, I've gotten into the world of davincy Jr because of my father-in-law, I have a prick I3 with which I am delighted.
I have problems with the emutag. After returning to flasear the card is not read by my two readers PN532 and an RC522 only by an android phone, but after a few hours the emutag is only recognized, do not overturn the information.
I already sent a duplicate. But my eagerness to repair things will not let me give it away.

sorry for my English
I tested with external power and the results are worse, a cell battery of 3.7v 1200mHa

58 (edited by CoolArts 2017-03-16 16:00:17)

Re: NFC tag emulator

If you are already waiting for a replacing unit, i would wait until it reaches to your home. As far as i know you have already flashed the unit 3 times, and it never worked more than 2 consecutive hours before it reset itself. I don't know enough electronics to help you to detect what component is wrong in you emutag maybe someone arround can help you with that more than i can.

Si ya estás esperando la unidad de reemplazo yo me esperaría a que te llegue. Si ya has reseteado la unidad 3 veces y nunca te ha funcionado más de 2 horas seguidas, no creo que esa unidad te valla a funcionar más lejos de ese punto. No sé si será una cosa de electrónica o no, lamentablemente yo no tengo los conocimientos suficientes como para ayudarte a detectar qué componente del emu te está fallando. Quizás alguien del foro te pueda ayudar mejor que yo.

Siento no poder ayudarte más. I'm sorry i can't help you further.
Un saludo!, Regards!

XYZ Junior/Mini Passwords Thread
If you are in a hurry and need your password NOW, or if it takes me too long for you, you can read the posts from 1851. I'm not going to be as effective as Bozo or Cgrillo, but you can give a try with me. If PASSWORDS thread follow it's current flow: asking for repeated passwords, not returning or false PACKS... I will end up with it as others before me.

59 (edited by Bozotclown1970 2017-03-16 17:23:15)

Re: NFC tag emulator

chetosvsgeez wrote:

I'm not writing in forums, and less in a language I do not dominate, I've gotten into the world of davincy Jr because of my father-in-law, I have a prick I3 with which I am delighted.
I have problems with the emutag. After returning to flasear the card is not read by my two readers PN532 and an RC522 only by an android phone, but after a few hours the emutag is only recognized, do not overturn the information.
I already sent a duplicate. But my eagerness to repair things will not let me give it away.

sorry for my English
I tested with external power and the results are worse, a cell battery of 3.7v 1200mHa



I had a similar issue and found that the batteries were very low. I had to order new ones from the internet because they are not common here in the US. I have not had any issues since replacing them.


Tuve un problema similar y encontré que las baterías eran muy bajas. yo Tuvimos que pedir nuevos de Internet porque no son comunes aquí en los Estados Unidos. No he tenido ningún problema desde su reemplazo.

60

Re: NFC tag emulator

thanks bozot...
The batteries are new, change them in the first problem which has now give enough mAh 43 mAh to make the emutag work without problems. I have to say that the ncipher support has been wonderful. It is not the fault of any component fails.

regads
Gerardo
http://soliforum.com/i/?IjDC5yF.jpg

61

Re: NFC tag emulator

chetosvsgeez wrote:

thanks bozot...
The batteries are new, change them in the first problem which has now give enough mAh 43 mAh to make the emutag work without problems. I have to say that the ncipher support has been wonderful. It is not the fault of any component fails.

regads
Gerardo
http://soliforum.com/i/?IjDC5yF.jpg

Glad I was able to head you in the right direction.

I have to agree with you, ncipher has to be the best vendor I have ever worked with.


Me alegro de poder dirigirte en la dirección correcta.

Tengo que estar de acuerdo con usted, Ncipher tiene que ser el mejor vendedor con el que he trabajado.

Bozo

62

Re: NFC tag emulator

Bozotclown1970
You could show me your RFID reader, to look for an equal one for my Emutag. They could all put the ones that use CoolArts Cgrillo ......

Thanks

63

Re: NFC tag emulator

chetosvsgeez wrote:

Bozotclown1970
You could show me your RFID reader, to look for an equal one for my Emutag. They could all put the ones that use CoolArts Cgrillo ......

Thanks


No problem, I use a Arduino UNO and an Adafruit PN532 Shield. Now I have to say, if you are using the software from eBay to update your EMU then you will need to make some modifications to the PN532. It comes IC2 enabled and the software from eBay is SPI. They both work equally well. I had modded my board but put it back. I bought another board for SPI.

http://soliforum.com/i/?xRKi0Wm.jpg

http://soliforum.com/i/?cNBgOfn.jpg

64

Re: NFC tag emulator

Hi all,
I bought an emutag and it worked like a charm until one day one of the batteries fell out. Since putting it back in, the device has not been readable anymore.
I replaced the batteries with brand new ones but to no avail.
As a last resort I flashed it via an Arduino Uno as described in this thread. It seems to have worked because all steps finished without any error message, but still it is not recognized.

Any idea, how to check what is going on here or how to revive this neat little thing?!

rt

65

Re: NFC tag emulator

real_terk wrote:

Hi all,
I bought an emutag and it worked like a charm until one day one of the batteries fell out. Since putting it back in, the device has not been readable anymore.
I replaced the batteries with brand new ones but to no avail.
As a last resort I flashed it via an Arduino Uno as described in this thread. It seems to have worked because all steps finished without any error message, but still it is not recognized.

Any idea, how to check what is going on here or how to revive this neat little thing?!

rt



What exactly did you do after you flashed it?

66

Re: NFC tag emulator

Bozotclown1970 wrote:

What exactly did you do after you flashed it?

I installed the batteries again and tried to read it with an android phone -> no reaction.

What should I've done?!

rt

67

Re: NFC tag emulator

real_terk wrote:
Bozotclown1970 wrote:

What exactly did you do after you flashed it?

I installed the batteries again and tried to read it with an android phone -> no reaction.

What should I've done?!

rt


Ok, since you re flashed the tag. It has no information in it. No password or pack code, nothing. Is a phone the only device you have for updating this? If yes, then you will now have some typing ahead of you before you can use it.

68

Re: NFC tag emulator

Bozotclown1970 wrote:
real_terk wrote:
Bozotclown1970 wrote:

What exactly did you do after you flashed it?

I installed the batteries again and tried to read it with an android phone -> no reaction.

What should I've done?!

rt


Ok, since you re flashed the tag. It has no information in it. No password or pack code, nothing. Is a phone the only device you have for updating this? If yes, then you will now have some typing ahead of you before you can use it.

To be honest, I don't even have a phone with NFC, so I have to borrow my colleague's one ;-)
When I got the emutag in the first place, I wrote the standard text file onto it which I found in one of these threads here.
Is something more required after flashing it? I am a bit annoyed that the phone does not detect the tag at all....

rt

69

Re: NFC tag emulator

real_terk wrote:
Bozotclown1970 wrote:
real_terk wrote:

I installed the batteries again and tried to read it with an android phone -> no reaction.

What should I've done?!

rt


Ok, since you re flashed the tag. It has no information in it. No password or pack code, nothing. Is a phone the only device you have for updating this? If yes, then you will now have some typing ahead of you before you can use it.

To be honest, I don't even have a phone with NFC, so I have to borrow my colleague's one ;-)
When I got the emutag in the first place, I wrote the standard text file onto it which I found in one of these threads here.
Is something more required after flashing it? I am a bit annoyed that the phone does not detect the tag at all....

rt


Let's switch over to PM. I think I may be able to help you.

70

Re: NFC tag emulator

Today, after about 5 days of printing bliss with my EMUtag, I now get "Spool Not Recognized"  error.  I was printing fine, and then on the next job, fail. 
So I thought it might be batteries, since I have been printing about 14 hours on this set, so I changed them.  Using my phone, I reprogrammed the tag fine, but still get the Spool Error.

Ummmmm.  Ok maybe the DaVinci is smart enough to throw this error if the count ( i.e. remaining length on the spool ) does not match the internal data.  It would be mismatched because I did not have the latest count saved after the last print.  So I used a new UID, Password and Pack.  Programmed the data on the EMUtag and,......  still no joy.

So I took a working file and programmed with that and again, Spool Error.

Ok, Whats going on here.  I can read and write the data on the EMUtag, It looks valid, but DaVinci complains.

I can write the file, read it back and compare ok.   
It looks like the EMUtag can no longer emulate.   

Does anyone have any thoughts on this?  And how to fix.

I will be starting printing withdrawal pains by the morning.  Please help.

71

Re: NFC tag emulator

mjf55 wrote:

Today, after about 5 days of printing bliss with my EMUtag, I now get "Spool Not Recognized"  error.  I was printing fine, and then on the next job, fail. 
So I thought it might be batteries, since I have been printing about 14 hours on this set, so I changed them.  Using my phone, I reprogrammed the tag fine, but still get the Spool Error.

Ummmmm.  Ok maybe the DaVinci is smart enough to throw this error if the count ( i.e. remaining length on the spool ) does not match the internal data.  It would be mismatched because I did not have the latest count saved after the last print.  So I used a new UID, Password and Pack.  Programmed the data on the EMUtag and,......  still no joy.

So I took a working file and programmed with that and again, Spool Error.

Ok, Whats going on here.  I can read and write the data on the EMUtag, It looks valid, but DaVinci complains.

I can write the file, read it back and compare ok.   
It looks like the EMUtag can no longer emulate.   

Does anyone have any thoughts on this?  And how to fix.

I will be starting printing withdrawal pains by the morning.  Please help.


PM me all of the data on your EMU Tag after you refreshed the data on it and I will take a look.

72

Re: NFC tag emulator

Mr Clown, PM sent with the data.  Thank you for your help

73

Re: NFC tag emulator

A couple of questions.

1. What is printer type?

2. What is firmware version?

3. Has the UID been used in printer before?

74

Re: NFC tag emulator

I have a da Vinci jr 1.0
Firmware is 2.2.7
yes, that one has , but i tried a brand new one and it is the same.

I can do a brand new on now and resend you the data if you like

75

Re: NFC tag emulator

Ok,

I sent you a PM with the same UID that worked in my printer. If you can easily try this then let me know if it works.