Me trying to rename a CSR8635...
@buriedcode mentioned, that direct programming of the external eeprom is normally not needed.
Well, i went this route because i do not have a CSR USB-SPI programmer, and i did not want to wait, and the task is most probably a one-off thing anyways.
And after reading the whole thread here, the described process using a selfmade programmer was not clear to me, and going for the eeprom seemed easyer.
I had no success with this, so my questions are around that...
I quickly made a parallel adaptor for ponyprog,
http://www.lancos.com/e2p/easyI2Cbus_mini.gifand was able to read the 24c64 chip using VCC of 3.3 instead of 5V.
Found the name-string, changed it, flashed back, powered off (programmer's voltage to chip), read again, saw my new string, SUCCESS! ... RIGHT? ... NO!
power up the module, aand... old name shows up!
After researching into possible caching things in android's bluetooth stuff, i read the eeprom again, and there was the old string again.
So, why's that?
Is there a checksum in the eeprom, and upon failure the 8635 goes back to the settings in his ROM, or what?
Could i hard-wire the write-protect pin on the eeprom? Most probably would need to disconnect it from the CSR chip i guess, but this would maybe still not help...
Any ideas?
If i would go for a self-made programmer, this still needs this FTTI chip, right?
Or are there options with some simple bitbanging things, similar to what i did with the ponyprog?
The TRANSPORT dialogue in PStools seems to suggest so...
But i did not fully grep the steps needed with the CSR software, and what programmer-hardware options are there.