As to what the LED flashes mean, there are many possible configurations for the LED patterns, which are customized by each distributor of these modules, so I don't know what state the module is in. I would have thought you have either got it stuck in config mode, or corrupted the EEPROM config (very easily done since everything except PSTools only writes back certain areas). However for some of the later CSRA64215 modules, these actually have flash on board which *does* store the firmware. Did you make a backup of the config with PStools first? These devices are often ROM-based, so there is no firmware. It is possible you have got the module stuck a "boot loop". So the question boils down to this: is there a way to drive a PIO pin high for as long as CSR8635 is awake? Thank you for help! I could sacrifice one of the three indicator LEDs that the module is driving, and have that signal control the LT1308, but I will do that only if I can't use one of the other PIOs. But I can't find any setting in the config program which would do this. The module would drive the pin high as long as it is awake, and a pull-down resistor would shut the LT1308 off when the module goes to sleep. LT1308 has an enable pin (active high), and I would like to be able to use one of the general purpose PIO pins of the CSR8635 to drive this enable pin. A solution to this problem would be to have the CSR8635 turn on the power section when it wakes up, and shut it down when it goes to sleep. And this is my problem: I have already over-discharged a few batteries by forgetting to shut the damn thing off. But the voltage regulator and the things it powers will not. The CSR8635 module is powered directly from the battery, and it will shut itself off at around 3.2V as it should. There is also a quad opamp powered by LT1308 which works as 4 comparators giving me a 4-level battery gauge.
The circuit has two mono PAM8304 amplifiers which are powered from a 18650 Li-ion battery boosted to 5V by an LT1308.
BLUESUITE CSR BLUETOOTH
I've built a bluetooth speaker based on CSR8635, and I need some help. If you connect the black magic's vcc to spi_en and a 1.8V target point, you will be powering the translator chip at that voltage and it should talk properly(at 1.8V).
BLUESUITE CSR CODE
If the code sees a voltage greater than 1V it leaves it's 3.3v power supply off. The Blue Pill can only talk in 3.3V but I updated the code so that when programmed to a black magic probe it checks target power voltage on power up. Here's a link: BlueMagic Also note, after playing with it for a bit, I realized I broke the csr8630 chip by yelling at it in 3.3v. The code also works if you have a black magic probe already, as it bitbangs the same pins that the probe does. If anyone wants their own csr programmer, they can purchase a " blue pill" and program it with any uart programmer to the CSR-SPI functionality. Not willing to pay the 15$ for a programmer, and looking to get more comfortable with the family of processors, I ported the code to the bluepill/black magic probe. Of course it broke and I was out of a programmer and had a new csr8645 module to play with/ need of reprogramming my hacked HD201 headphones.
BLUESUITE CSR DRIVER
Will work with the original CSR driver and should allow all CSR BlueSuite tools to work on BlueCore chips, with the notable exception of the ones requiring JTAG.
Hey All, I had a stellaris board kicking around for a long time programmed to GitHub - Frans-Willem/CsrUsbSpiDeviceRE: Reverse engineered reimplementation of the CSR USBSPI converter device on a Stellaris Launchpad.
0 kommentar(er)
