Hi Raymond, > If I using -r in the bccmd: > > ~ # bccmd -t bcsp -d /dev/ttyS1 psload -r csr.psr > Loading PSKEY_ANA_FREQ ... done > Loading PSKEY_UART_BAUDRATE ... done > Loading PSKEY_UART_SEQ_WINSIZE ... done > Loading PSKEY_BDADDR ... done > Loading PSKEY_PCM_CONFIG32 ... done > Loading PSKEY_PCM_FORMAT ... done > Loading PSKEY_HOSTIO_MAP_SCO_PCM ... done > Loading PSKEY_HOSTIO_MAP_SCO_CODEC ... done > Loading PSKEY_CODEC_PIO ... done > Loading PSKEY_ANA_FTRIM ... done > ~ # > ~ # hciattach -s 921600 /dev/ttyS1 bcsp 921600 > BCSP initialization timed out Which baud rate do you set in your .psr file? You should use the same speed in hciattach command, otherwise chip will be initialized to one speed, and hciattach will try to connect using another one. > I try to use following cmd to see whether the cmd is write in to the chip, > but : > > ~ # bccmd -t bcsp -d /dev/ttyS1 psget -s 0x0 0x1be > UART Baud rate: 0x0000 (0) > ~ # > ~ # bccmd -t bcsp -d /dev/ttyS1 psset -s 0x0 0x1be 0x0ebf > ~ # > ~ # bccmd -t bcsp -d /dev/ttyS1 psget -s 0x0 0x1be > UART Baud rate: 0x0000 (0) > > seems chip just reset it self between two bccmd with bcsp protocol, and lost > everything write to it. Yes, I had the same behaviour, and only if I use -r with first bccmd things worked. Reading the fault code returned FAULT_HOSTIO_INVALID_ACK (the chip received a BCSP ACK for a message it has not sent) - based on this I conclude that repeating bccmd messes the chips state machine during BCHS protocol initialization. Regards, Sanja ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bluez-devel mailing list Bluez-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/bluez-devel
