Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - kamcm

2
Bus Pirate Support / Re: Buspirate 3.6 alive?
genuine FT232RL, 4 number + country of origin at the back of the IC


Counterfeit FT232RL, CHINA marking at the back of the IC, marking is not clear
3
Bus Pirate Support / Re: Buspirate 3.6 alive?
[quote author="Samual"]Why is Seeed using counterfeit chips ?[/quote]

The counterfeit chips are much cheaper.

Bus pirate made by pirate chips. It's cool, isn't it?
4
Bus Pirate Support / Re: Buspirate 3.6 alive?
[quote author="Pieter"]You might like to check this post:
viewtopic.php?f=4&t=6052&p=55828#p55827
It was a driver problem.. Hope this helps for you all too..[/quote]

This is not a driver problem, the counterfeit FTDI chips is the main reason.

THE NEW DRIVER is a means to fight with counterfeit IC.

http://forum.arduino.cc/index.php?topic=173676

-----------
More case
http://forum.arduino.cc/index.php?topic=181434.0
http://club.dx.com/forums/forums.dx/threadid.1314582
5
Bus Pirate Support / Re: Bus Pirate v3.6 (apr 2012) Seeed 10/09/13 Almost DOA
[quote author="Pieter"]Hi Samual, thank you for your quick reply!

[quote author="Samual"]Does windows detect the ftdi chip. A COM port should appear in Device manager. Make sure you select the right COM port and set the baud rate to 115200. [/quote]
Checked and looks good.
[quote author="Samual"]
Make sure the cable you are using is not bad. Some usb cables are only ment for charging.
[/quote]
Double checked with other cable..
[quote author="Samual"]
If yor computer detect the FTDI chip use the GUI firmware upgrade tool to upgrade the firmware. Make sure you select the correct COM port and short pins PGD and PGC.
[/quote]
Initiating download...
      Searching for bl . (discarded null byte)
      Found unknown device id(0) fw ver. 0.0.0
      Tx 1 byte / Rx 3 bytes / 0,3s

[quote author="Samual"]
If that does not work contact Seeed's Q.C and customer support team and ask them to send you a new one.[/quote]
Think I should do that....[/quote]


the main reason is the counterfeit FT232RL.
The marking on the counterfeit FT232RL is CN480661

More info: viewtopic.php?f=4&t=5947&start=15#p55660
6
Bus Pirate Support / Re: Buspirate 3.6 alive?
[quote author="kubikzovocia"]Same here, Bus Pirate v3.6(april 2012) from seeedstudio DOA(well power lights up but thats it). scope shows gibberish on 232RL TX pin so probably that is the problem. I am definitely not ordering from them again since this is second time(out of two) they royally screwed up my order.(first time it cost me around 20€ and lots of time and nerves)[/quote]

As I previously said, the main reason may be the counterfeit FT232RL.
The marking on the counterfeit FT232RL is CN480661.

viewtopic.php?f=4&t=5947#p55429
7
Bus Pirate Support / Re: Everything returned 0xFF, please advice
[quote author="Sjaak"]I'm sorry didn't saw you tried address 0xA0. Also the links are broken (copied from a reply to simular question). This one addressed reading/writing an 24xx eeprom (assuming that is ther one you are trying to program/read)  http://dangerousprototypes.com/docs/3EE ... I2C_EEPROM

Could you please provide which chip your are trying to read/write? How the connections are made between the chip and BusPirate? Is the chip still in circuit? I'm assuming it is since you did use the sniffer. Some circuits interfere/block the buspirate in using the bus.

From the tutorial this should work for reading address, assuming the electrical connection is OK. Reading a byte consist of writing the address, and repeated start to read the byte.

Code: [Select]
WP   <-- enable powersupply and pullups 
[][]   <-- some devices need a stop condition to reset the I2C chiplogic
[ 0xA0 0x00 0x54 ]  <-- start, (write)adress 0xA0, address 0x0054, stop (not mandatory iirc) 
[ 0xA1 r ]    <--- repeated start, (read)address 0xA1, read a byte, stop

Also please provide the full log of session, if still in trouble.[/quote]





The chip is still in circuit, I am not sure if it required me to de-solder it out.
Btw, I unable to find the datasheet for this EEPROM.

Thanks for helping


I2C>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
9. DIO
x. exit(without change)

(1)>4
Set speed:
 1. ~5KHz
 2. ~50KHz
 3. ~100KHz
 4. ~400KHz

(1)>1
Ready
I2C>(1)
Searching I2C address space. Found devices at:
Warning: *Short or no pull-up

I2C>WP
Power supplies ON
Pull-up resistors ON
I2C>(1)
Searching I2C address space. Found devices at:


I2C>(1)
Searching I2C address space. Found devices at:


I2C>[0b10100000 0 84 r]
I2C START BIT
WRITE: 0xA0 NACK
WRITE: 0x00 NACK
WRITE: 0x54 NACK
READ: 0xFF
NACK
I2C STOP BIT
I2C>[0b10100001 0 84 r]
I2C START BIT
WRITE: 0xA1 NACK
WRITE: 0x00 NACK
WRITE: 0x54 NACK
READ: 0xFF
NACK
I2C STOP BIT
8
Bus Pirate Support / Re: Everything returned 0xFF, please advice
[quote author="Sjaak"]The I2C eeprom is at address 0xA0 and 0xA1. there is no I2C device on your bus with address 0x54, hence the NACK.

more info/tutorials about reading/writing I2C EEPROMs here:  http://dangerousprototypes.com/docs/3EE ... orer_board , http://dangerousprototypes.com/docs/2AA ... AC_address , http://hackaday.com/2008/11/19/how-to-t ... ce/#EEPROM

more info about I2C: http://dangerousprototypes.com/docs/I2C[/quote]

Thanks for the reply,

I read all of the docs before asking here.

I tried two methods but both of them did not work

Method1
I2C> [0b10100000 0 84 r] // Read directly from 0xA0+0x00+0x54
I2C> [0b10100001 0 84 r] // Read directly from 0xA0+0x00+0x54




method2
I2C>[0b10100000 0 84 ] //position the read pointer to 0xA0+0x00
I2C> [0b01010100 r:1] //read the values of 0x54 address

Method3

I2C> [0xa0 0x00][0x54 r:2]
I2C START BIT
WRITE: 0xA0 NACK
WRITE: 0x00 NACK
I2C STOP BIT
I2C START BIT
WRITE: 0x54 NACK
READ: 0xFF  ACK 0xFF
NACK
I2C STOP BIT
I2C>

I2C> [0xa1 0x00][0x54 r:2]
I2C START BIT
WRITE: 0xA1 NACK
WRITE: 0x00 NACK
I2C STOP BIT
I2C START BIT
WRITE: 0x54 NACK
READ: 0xFF  ACK 0xFF
NACK
I2C STOP BIT
I2C>

Please advice,

Thanks
9
Bus Pirate Support / Everything returned 0xFF, please advice
I want to Write 0x0F at address 0x0054 on EEPROM, but I don't know why it did not work.

I2C> (1)
Searching I2C address space. Found devices at:


I2C> (2)
Sniffer
Any key to exit
[[][][[0xA0+0x00+0x40+0xA5+][0xA0+0x00+0x41+0x5A+][0xA0+0x00+0x42+0x00+][0xA0+0x
00+0x43+0x01+][0xA0+0x00+0x44+0x01+][0xA0+0x00+0x45+0x00+][0xA0+0x00+0x46+0x00+]
[0xA0+0x00+0x47+0x00+][0xA0+0x00+0x50+0xA5+][0xA0+0x00+0x51+0x5A+][0xA0+0x00+0x5
2+0x01+][0xA0+0x00+0x53+0x11+][0xA0+0x00+0x54+0x07+][0xA0+0x00+0x55+0x00+][0xA0+
0x00+0x56+0x00+][0xA0+0x00+0x57+0x00+][0xA0+0x00+0x58+0x00+][0xA0+0x00+0x59+0x00
+][0xA0+0x00+0x5A+0x00+][0xA0+0x00+0x5B+0x00+][0xA0+0x00+0x5C+0x01+][0xA0+0x00+0
x5D+0x00+][0xA0+0x00+0x5E+0x00+][0xA0+0x00+0x5F+0x00+][0xA0+0x00+0x60+0x00+][0xA
0+0x00+0x61+0x00+][0xA0+0x00+0x62+0x00+][0xA0+0x00+0x63+0x00+]


I2C> =0X54
0x54 = 84 = 0b01010100



I2C> [0b01010100 r:1]
I2C START BIT
WRITE: 0x54 NACK
READ: 0xFF
NACK
I2C STOP BIT
I2C>
I2C>

I2C> [0b10100000 0 84 r]
I2C START BIT
WRITE: 0xA0 NACK
WRITE: 0x00 NACK
WRITE: 0x54 NACK
READ: 0xFF
NACK
I2C STOP BIT
I2C>
0X54 should be 0x07, but it returned 0xFF

I want to Write 0x0F at address 0x0054 on EEPROM.
Before doing that, I want to read the current record at address 0x0054,  I don't know why it did not work.

Please advice,

Thanks
10
Bus Pirate Support / Re: Buspirate 3.6 alive?
I just received the replacement [05/30/13]and now I can connect to the Buspirate via terminal.
The problem has been solved.

Thanks for the help,

Kam
11
Bus Pirate Support / Re: Seeed ship out defective Bus Pirate V3
[quote author="Samual"]Have you selected the correct COM port ?

Well I think Seeed has improved quite a bit in the past few month. They'll send you replacements and most probabily through express shipping.

With the volume they sell there will been a few defective units that get past Q.C[/quote]

I am 100% sure I had selected the correct COM port and having the correct settings in the terminal too.
12
Bus Pirate Support / Re: Buspirate 3.6 alive?
[quote author="Coder"]Hi kamcm

The version of this file is not compatible with the version of Windows I'm running.
Is a 64-bit OS, I tried DOSBox but was not able to run the file, then I tried to edit
the .bat file but I end up giving up, thank you kamcm[/quote]

it works in 64-bit windows, you may download it with the wrong way.

https://code.google.com/p/the-bus-pirat ... lftest.exe

Download it by clicking the "View raw file" on the right hand side.

OR

https://the-bus-pirate.googlecode.com/s ... lftest.exe

The file should be 15K, you may did something wrong if it's not 15k.
13
Bus Pirate Support / Re: Seeed ship out defective Bus Pirate V3
[quote author="tayken"]OK, I'm sending the link of this post to the dev group, lets see if we can do sth about it.[/quote]

Thanks,

I got a reply from seeedstudio .

That promised they will  send a replacement to me

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01892462880session_write_close ( )...(null):0
20.01922594480ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01922595256Database_MySQL->query( ).../DatabaseHandler.php:119
40.09052734000Database_MySQL->error( ).../Db-mysql.class.php:273