Search:

Ok.
Do you send the bit pattern 1010<3 high bit address>0 followed by 8bit low address and then 1010<3 high bit address>1 followed by 8bit low for then to read 1 byte data?
Something like tihis:
...

How does the chip get power if you don't connect VCC or the USB cable to the pcb?
Is your reader powered with 5v or 3.3v?
I still cant get it to work :)

I ordered up a new 036NHA that I can use for testing and I also got my FlashCAT I2C reader. I tried to read the eeprom without removing it but that did not work. What I did was just connect all wires...

I measured my power consummation at the 230v side (so not to accurate) but I notice that when changing txpower from 0 up to 23 I could see and increase in power usage.
However going higher that 23...

Hi
Can you specify what options you used with mdk3 so I can try the same test on my adapter?

I ordered this from ebay:
http://www.ebay.com/itm/331717106581?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

I have now updated the checksum on my chip and now it seems to work fine. No error messages under boot etc.
Here are som log data:

(Oh and I used BO as the new region)



[ 34.780000]...

I ordered the "new" FlashCat USB that comes with the PCB v2.x and with it I also ordered this test clip. With PCB 2.x it can now also do i2c.
But I did not get it yet and I just cant wait to test...

Found some info about the checksum here:
http://lxr.free-electrons.com/source/drivers/net/wireless/ath/ath9k/eeprom_9287.c
At line 231 they calc the checksum.

So it looks like the eeprom struct...

Gah!
There is a checksum in there.



Jan 21 23:18:06 OpenWrt kern.info kernel: [ 34.460000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
Jan 21 23:18:06 OpenWrt kern.info...

Hi
I just removed my eeprom from the PCB and read it out to see that it's locked to 0x33A. (0x833A) (at offset 0x88 in the rom file)
Now I can write a different region code to it but wonder what...