Author Topic: DIY "GREEN DOT" Data Logger  (Read 68466 times)

0 Members and 1 Guest are viewing this topic.

Offline iBangkok24

  • Member
  • *
  • Posts: 25
DIY "GREEN DOT" Data Logger
« on: January 30, 2013, 10:11:00 AM »
I have every thing I need, so I try to program the security registry. The problem is, it seem like I can't program it. Please have a look at my terminal capture below

Quote
SPI>[0x9f r:4]   <<< Check If I have a good SPI communication
/CS ENABLED
WRITE: 0x9F
READ: 0x1F 0x22 0x00 0x00
/CS DISABLED
SPI>[0x77 0 0 0 r:128]   <<< Read in the security register
/CS ENABLED
WRITE: 0x77
WRITE: 0x00
WRITE: 0x00
WRITE: 0x00
READ: 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0x0B 0x02 0x0E 0x05 0x3A 0x30 0x1F 0x22 0x00 0x00 0x5E 0x00 0xFF 0xFF 0xBC
 0xFF 0x30 0x30 0x4D 0x32 0x36 0x36 0x39 0x38 0x07 0x5E 0x2D 0xFF 0xFF 0xFF 0xFF
 0xFF 0x43 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF
/CS DISABLED
SPI>[0x9b 0x00 0x00 0x00 0x80 0x2D 0x22 0x6F 0x52 0x6F 0x98 0xA9 0x21 0x25 0x5E
0x2D 0x2D 0x31 0xD2 0x39   <<< Security register write start here
/CS ENABLED
WRITE: 0x9B
WRITE: 0x00
WRITE: 0x00
WRITE: 0x00
WRITE: 0x80
WRITE: 0x2D
WRITE: 0x22
WRITE: 0x6F
WRITE: 0x52
WRITE: 0x6F
WRITE: 0x98
WRITE: 0xA9
WRITE: 0x21
WRITE: 0x25
WRITE: 0x5E
WRITE: 0x2D
WRITE: 0x2D
WRITE: 0x31
WRITE: 0xD2
WRITE: 0x39
SPI>0x18 0x1C 0x63 0x0C 0x31 0x21 0x2D 0x39 0x90 0xDE 0x94 0x6F 0x6B 0x77 0x73 0
x7F 0x63 0x8C 0x88 0x84 <<< I have to break it in to many line because I can't copy/paste the whole data in
WRITE: 0x18
WRITE: 0x1C
WRITE: 0x63
WRITE: 0x0C
WRITE: 0x31
WRITE: 0x21
WRITE: 0x2D
WRITE: 0x39
WRITE: 0x90
WRITE: 0xDE
WRITE: 0x94
WRITE: 0x6F
WRITE: 0x6B
WRITE: 0x77
WRITE: 0x73
WRITE: 0x7F
WRITE: 0x63
WRITE: 0x8C
WRITE: 0x88
WRITE: 0x84
SPI>0x80 0x9C 0x98 0x94 0x90 0xAD 0xA9 0xA5 0xA1 0xBD 0xB9 0xB5 0xB1 0xCA 0xCE 0
xC2 0xC6 0xDA 0xDE 0xD2
WRITE: 0x80
WRITE: 0x9C
WRITE: 0x98
WRITE: 0x94
WRITE: 0x90
WRITE: 0xAD
WRITE: 0xA9
WRITE: 0xA5
WRITE: 0xA1
WRITE: 0xBD
WRITE: 0xB9
WRITE: 0xB5
WRITE: 0xB1
WRITE: 0xCA
WRITE: 0xCE
WRITE: 0xC2
WRITE: 0xC6
WRITE: 0xDA
WRITE: 0xDE
WRITE: 0xD2
SPI>0xD6 0xEB 0xEF 0xE3 0xE7 0xFB 0xFF 0xF3] <<< finish write the security register
WRITE: 0xD6
WRITE: 0xEB
WRITE: 0xEF
WRITE: 0xE3
WRITE: 0xE7
WRITE: 0xFB
WRITE: 0xFF
WRITE: 0xF3
/CS DISABLED
SPI>[0xd7 r]
/CS ENABLED
WRITE: 0xD7
READ: 0x8C
/CS DISABLED
SPI>[0x77 0 0 0 r:128] <<< read it back in.... nothing change!!!
/CS ENABLED
WRITE: 0x77
WRITE: 0x00
WRITE: 0x00
WRITE: 0x00
READ: 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0x0B 0x02 0x0E 0x05 0x3A 0x30 0x1F 0x22 0x00 0x00 0x5E 0x00 0xFF 0xFF 0xBC
 0xFF 0x30 0x30 0x4D 0x32 0x36 0x36 0x39 0x38 0x07 0x5E 0x2D 0xFF 0xFF 0xFF 0xFF
 0xFF 0x43 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
 0xFF
/CS DISABLED
SPI>

Am I doing something wrong?

Offline DeKay

  • Forecaster
  • *****
  • Posts: 397
    • Mad Scientist Labs
Re: DIY "GREEN DOT" Data Logger
« Reply #1 on: January 30, 2013, 07:51:26 PM »
Am I doing something wrong?


If it isn't working, then you are certainly doing something wrong.  Don't know what though.

Have you tried more than once to program the security register?  You only get one chance to get it right.  If you screw up by not getting it just right the first time, you've got to throw the chip away and try again on a new one. 

I would suggest trying something simpler like a page write and get that working first before trying again on a new chip.

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #2 on: January 30, 2013, 08:16:47 PM »
Am I doing something wrong?


If it isn't working, then you are certainly doing something wrong.  Don't know what though.

Have you tried more than once to program the security register?  You only get one chance to get it right.  If you screw up by not getting it just right the first time, you've got to throw the chip away and try again on a new one. 

I would suggest trying something simpler like a page write and get that working first before trying again on a new chip.

I think you right DeKay. I try several thing before programming the security register, but the first time I try to write it I got so many problem, forgot to add 0x before all digit of data, copy/paste without luck. Maybe I just accidentally write nothing in that register in the first attempt. Will try it with a new one.

Thanks,

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #3 on: January 30, 2013, 08:24:51 PM »
The Logger sit and working nicely in my "NON Green Dot" VUE console. I will make a new one as soon as I got more PCB in hand.






Offline Bushman

  • Forecaster
  • *****
  • Posts: 6879
    • Eagle Bay Weather
Re: DIY "GREEN DOT" Data Logger
« Reply #4 on: January 30, 2013, 09:05:25 PM »
So you built your own logger with Xbee communication?  Sweet.

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #5 on: January 30, 2013, 09:37:04 PM »

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #6 on: February 01, 2013, 08:04:28 AM »
While I'm waiting for more PCB to arrive. Today I put my bus pirate in SPI Sniffer mode and this is what happen when I power up a "GREEN DOT" Vue console

Quote

SPI>(1)
Sniffer
Any key to exit
[0x6B(0xFF)0x80(0xC6)][0x3B(0x7F)0x80(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x85)0x00(0x
81)0x00(0x07)0x00(0x02)0x00(0x9D)0x00(0x18)0x00(0x0F)0x00(0x91)0x00(0x00)0x00(0x
00)0x00(0x2F)0x00(0x00)0x00(0x7F)0x00(0xFF)0x00(0xDE)0x00(0x7F)0x00(0x98)0x00(0x
18)0x00(0x26)0x00(0x99)0x00(0x1B)0x00(0x1B)0x00(0x1C)0x00(0x9C)0x00(0x03)0x00(0x
AF)0x00(0x16)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xA1)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0x
FF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)0x00(0xFF)]

As I understand, the console try to wirte 0x6B and 0x80 to the chip. and then 0x3b 0x80 0x00 0x00 then read in 128 byte of data. I try to find out what 0x6B 0x80 command is with no luck, I neither can't find anything with 0x3B 0X80 0X00 0X00.

Any Idea?
« Last Edit: February 01, 2013, 09:11:52 AM by iBangkok24 »

Offline rdsman

  • Senior Contributor
  • ****
  • Posts: 198
Re: DIY "GREEN DOT" Data Logger
« Reply #7 on: February 01, 2013, 01:56:51 PM »
I am not familiar with your test equipment, but it looks to me like the trigger point is too slow or the sampling rate is off (or both).  If I take the following sequence:

0x6B(0xFF)0x80(0xC6)

convert it to 32 bits:

0x6BFF80C6

Shifted 1 bit to the left, it becomes:

0xD7FF018C

This comes real close to reading the Status Register and getting a valid response.  On the otherhand, if I take the following sequence:

0x3B(0x7F)0x80(0xFF)0x00

And use just the outgoing portion:

(0x3B80 < 1) = 0x7700

I don't know.................

 

« Last Edit: February 01, 2013, 02:11:50 PM by rdsman »
Ray

Offline DeKay

  • Forecaster
  • *****
  • Posts: 397
    • Mad Scientist Labs
Re: DIY "GREEN DOT" Data Logger
« Reply #8 on: February 01, 2013, 08:59:34 PM »
I am not familiar with your test equipment, but it looks to me like the trigger point is too slow or the sampling rate is off (or both).


I had odd results when I used my Bus Pirate as well.  I might play around with this on the weekend and will post here if I figure out the problem.

Offline kb1pvh

  • Member
  • *
  • Posts: 3
    • My weather
Re: DIY "GREEN DOT" Data Logger
« Reply #9 on: February 02, 2013, 09:11:35 AM »
iBangkok24

  I have a dreaded GREEN DOT console and unfortunately it won't allow me to use the setup af4ex did. If you get something to work, I'll buy one from you for sure. I have a pair of XBEEs sitting here waiting for a working solution.


Dave-KB1PVH

Offline C5250

  • Forecaster
  • *****
  • Posts: 840
    • Local weather
Re: DIY "GREEN DOT" Data Logger
« Reply #10 on: February 02, 2013, 11:41:36 AM »
I had odd results when I used my Bus Pirate as well.  I might play around with this on the weekend and will post here if I figure out the problem.

Double speed is used when talking to the radio, but not when talking to the logger.
Precious little in your life is yours by right and won without a fight.

Offline DeKay

  • Forecaster
  • *****
  • Posts: 397
    • Mad Scientist Labs
Re: DIY "GREEN DOT" Data Logger
« Reply #11 on: February 03, 2013, 12:39:52 PM »
I am not familiar with your test equipment, but it looks to me like the trigger point is too slow or the sampling rate is off (or both).


I had odd results when I used my Bus Pirate as well.  I might play around with this on the weekend and will post here if I figure out the problem.

I've sorted out my Bus Pirate problem.  I needed to connect the Bus Pirate's Vpu (voltage pullup line) to 3.3V and enable pullups on the Bus Pirate.  I'm also in the middle of writing a Python script that talks to the Bus Pirate using its binary mode interface.  This will make the programming of the security key trivial to anybody who has this cheap and wonderful little device.  Here is a teaser from my DIY logger:

Quote
[dekay@laptop dataflash]$ python2 spi_test.py
Entering binmode:  OK.
Entering raw SPI mode:  OK.
Configuring SPI.
Chip Status: 0x8c
Chip ID: 0x1f 0x22 0x00 0x00
Reading Security Register:
[ 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]
[ 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]
[ 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]
[ 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]
[ 0x0b 0x01 0x1e 0x0e 0x13 0x15 0x1f 0x22 0x00 0x00 0x56 0x00 0xff 0xff 0xd8 0xff ]
[ 0x30 0x30 0x4d 0x32 0x35 0x36 0x32 0x36 0x08 0x31 0x34 0xff 0xff 0xff 0xff 0xff ]
[ 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]
[ 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ]


Offline rdsman

  • Senior Contributor
  • ****
  • Posts: 198
Re: DIY "GREEN DOT" Data Logger
« Reply #12 on: February 03, 2013, 02:06:51 PM »

I've sorted out my Bus Pirate problem.


Nice Work!

Ray

Offline franzz

  • Member
  • *
  • Posts: 13
Re: DIY "GREEN DOT" Data Logger
« Reply #13 on: February 06, 2013, 04:32:14 PM »
I think that Davis uses both sections of security register (0..63 and 64..127) for decryption, because it makes no sense to use only a static key in the 1st block of security register to be save. My opinion is that Davis uses the unique ID in the second part for encryption of a view bytes in the first part of security register.
If I empathize me with the part of Davis, I would write some coded product info (serial, revision, production date,...) + encrypted info from 2nd part of security register (unique ID) into this 1st part of security register.
But to prove this theory we need at least a second owner of a green dot datalogger which is able to read out security register to compare the data of the 0..63 byte of security register with data of rdsman. I fear that this 0..63 bytes differ for every green dot datalogger.

BR
franzz

Offline DeKay

  • Forecaster
  • *****
  • Posts: 397
    • Mad Scientist Labs
Re: DIY "GREEN DOT" Data Logger
« Reply #14 on: February 06, 2013, 11:12:38 PM »
I think that Davis uses both sections of security register (0..63 and 64..127) for decryption, because it makes no sense to use only a static key in the 1st block of security register to be save. My opinion is that Davis uses the unique ID in the second part for encryption of a view bytes in the first part of security register.
If I empathize me with the part of Davis, I would write some coded product info (serial, revision, production date,...) + encrypted info from 2nd part of security register (unique ID) into this 1st part of security register.
But to prove this theory we need at least a second owner of a green dot datalogger which is able to read out security register to compare the data of the 0..63 byte of security register with data of rdsman. I fear that this 0..63 bytes differ for every green dot datalogger.

BR
franzz

I think franzz is correct.  The key rdsman discovered doesn't show up in the new firmware, so there is likely a computation involved rather than a static key.  The good news is that the console has a pretty feeble processor in it so the computation is likely to be simple.  The other good news is that the commands to read the key from the flash are well defined and this should help narrow things down.

So what we need first is for rdsman or somebody else to dump the full 128 bytes in the security register and then figure out how to get from one to the other.

Anybody know when the console reports the incompatible logger error?  After the first beep?  Second beep?

BTW, my attempts to get my Bus Pirate to talk to my DIY logger chip hit a wall when I found I couldn't reliably read a page of data.  I'll look at it a bit again this weekend and see if I can get it going.  Either way, I'll post my code in case anybody else once to give it a shot and get it working.

Offline franzz

  • Member
  • *
  • Posts: 13
Re: DIY "GREEN DOT" Data Logger
« Reply #15 on: February 07, 2013, 03:20:45 AM »

The key rdsman discovered doesn't show up in the new firmware, so there is likely a computation involved rather than a static key. 

Do you have the new firmware (3.0) as a file? I can't find it in Davis download section.


BR
franzz

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #16 on: February 07, 2013, 06:33:01 AM »

Anybody know when the console reports the incompatible logger error?  After the first beep?  Second beep?


I have VUE Console, both "GreenDot" and "NonGreenDot".

The "NON Green dot" will display all dot in LCD and send out "LCD OK" after the 3(third) beep, and try out SPI communication with my DIY Logger then report a successful with the 4(fourth) beep.

The "Green DOT" does the same procedure, but not beep out the fourth beep due to unsuccessful verify a Green Dot Logger.

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #17 on: February 07, 2013, 06:40:10 AM »
I think that Davis uses both sections of security register (0..63 and 64..127) for decryption, because it makes no sense to use only a static key in the 1st block of security register to be save. My opinion is that Davis uses the unique ID in the second part for encryption of a view bytes in the first part of security register.
If I empathize me with the part of Davis, I would write some coded product info (serial, revision, production date,...) + encrypted info from 2nd part of security register (unique ID) into this 1st part of security register.
But to prove this theory we need at least a second owner of a green dot datalogger which is able to read out security register to compare the data of the 0..63 byte of security register with data of rdsman. I fear that this 0..63 bytes differ for every green dot datalogger.

BR
franzz

I agree with franzz as i mention this in another topic, "Incompatible Logger" and as my SPI sniff shown that the console try to read 128 bytes of data out of the logger, not just 64 butes.

One more concern rdsman, While I'm waiting for my bus pirate I have some feeling that Davis might be using the Security Register from bit 65 to 127, which is unique for every single 45DB to calculate what is to be programmed in the first 64 bit of the Security Register. If my concern becoming true it would be nightmare.

Maybe I just think too much.
« Last Edit: February 07, 2013, 07:09:02 AM by iBangkok24 »

Offline rdsman

  • Senior Contributor
  • ****
  • Posts: 198
Re: DIY "GREEN DOT" Data Logger
« Reply #18 on: February 07, 2013, 04:47:00 PM »
Here is the full dump:

Code: [Select]

Status Register (0xD7): 0x8C

Manufacturer and Device ID Information (0x9F): 0x1F 0x22 0x00 0x00

Sector Lockdown Register (0x35): 0x00 0x00 0x00 0x00

Security Register (0x77):

0x80  0x2D  0x22  0x6F  0x52  0x6F  0x98  0xA9  0x21  0x25  0x5E  0x2D  0x2D  0x31  0xD2  0x39
0x18  0x1C  0x63  0x0C  0x31  0x21  0x2D  0x39  0x90  0xDE  0x94  0x6F  0x6B  0x77  0x73  0x7F
0x63  0x8C  0x88  0x84  0x80  0x9C  0x98  0x94  0x90  0xAD  0xA9  0xA5  0xA1  0xBD  0xB9  0xB5
0xB1  0xCA  0xCE  0xC2  0xC6  0xDA  0xDE  0xD2  0xD6  0xEB  0xEF  0xE3  0xE7  0xFB  0xFF  0xF3
0x0B  0x02  0x16  0x17  0x11  0x15  0x1F  0x22  0x00  0x00  0x46  0x00  0xFF  0xFF  0xAC  0xFF
0x30  0x30  0x4D  0x32  0x36  0x39  0x37  0x31  0x0F  0x1C  0x0C  0xFF  0xFF  0xFF  0xFF  0xFF
0x3F  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF
0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF  0xFF


Ray

Offline franzz

  • Member
  • *
  • Posts: 13
Re: DIY "GREEN DOT" Data Logger
« Reply #19 on: February 15, 2013, 02:06:56 AM »
Does anyone know if the serial interface is also blocked in case of using only the serial to USB converter (FT232) without the Flash(45DB011) with console firmware 3.0?

BR
franzz

Offline belfryboy

  • Forecaster
  • *****
  • Posts: 488
  • waiting for the rain.....
    • Belfryboy Blog
Re: DIY "GREEN DOT" Data Logger
« Reply #20 on: February 15, 2013, 03:12:20 AM »
I beleive that it is. The console looks for a valid liogger on the SPI bus, if it finds one it enable the serial port communications, if it doesn't find one it diasble this function.

Offline rdsman

  • Senior Contributor
  • ****
  • Posts: 198
Re: DIY "GREEN DOT" Data Logger
« Reply #21 on: February 17, 2013, 06:22:29 PM »
It might be possible to just "spoof" the console into enabling the serial port.  This would only interest people that don't need the full logging capability.  You could for example use a setup that provides a USB interface or the XBee footprint.  Write some code and off you go!  Here is just one example:


« Last Edit: February 18, 2013, 06:05:14 PM by rdsman »
Ray

Offline belfryboy

  • Forecaster
  • *****
  • Posts: 488
  • waiting for the rain.....
    • Belfryboy Blog
Re: DIY "GREEN DOT" Data Logger
« Reply #22 on: February 18, 2013, 03:17:51 AM »
It might be possible to just "spoof" the console into enabling the serial port.  This would only interest people that don't need the full logging capability.  You could for example use a setup that provides a USB interface or the XBee footprint.  Write some code and off you go!  Here is just one example:
Good point, and thinking about it using the chip select line you could enable logging after the link is opened.

Offline rdsman

  • Senior Contributor
  • ****
  • Posts: 198
Re: DIY "GREEN DOT" Data Logger
« Reply #23 on: February 18, 2013, 09:03:57 AM »
Yes it did occur to me that you could even parallel the SPI bus and just hold the AT45DB011D in reset until the Security Register has been read.

Ray

Offline iBangkok24

  • Member
  • *
  • Posts: 25
Re: DIY "GREEN DOT" Data Logger
« Reply #24 on: February 20, 2013, 03:55:45 AM »
rdsman, Is it possible to plug in the buspirate and spoof the console (in the power on phase), then take off the buspirate and plug in the NON GreenDot logger (never stop the power to the console). Just some thing like tether jailbreak.

 

anything