Hello FreeCalypso community, I've got an update on the flash boot problem, or rather several discoveries on that front.
The first discovery is that of the 6 boards I have left after sending one to Harald Welte and another to Serg, the mysterious flash boot problem I've been seeing only occurs on one board, S/N 001 - it is the one on which I've been doing most of my work. 4 of the boards (S/N 002, 006, 007 and 008) boot flash fw images just fine, and the remaining one (S/N 004) is unable to boot the full fw at all - fc-loadtool etc work just fine, but if I try to load a full fw image via fc-xram, it goes through the download process and then hangs once the jump to the downloaded code has been made. I suspect that it is some totally different problem from the flash boot issue on S/N 001. The second discovery is that the S/N 001 board which exhibits the mysterious flash boot problem only manifests the erratic behaviour when the fw image in the flash uses flash boot mode 1, and works just fine when it uses flash boot mode 0. See the doc/Flash-boot-modes article I just added to the freecalypso-tools tree for the explanation of the two flash boot modes. FC Citrine uses flash boot mode 0; unhacked FC Magnetite uses flash boot mode 1, but I just implemented an optional patch that makes it use flash boot mode 0, and the latter works on my S/N 001 board. To Serg: I encourage you to try building FC Magnetite for the FCDEV3B in the flash image configuration and flashing it into your board, to see if the board I sent you has working flash boot. Build Magnetite for the fcdev3b target in the l1reconst configuration, do a regular make to get fwimage.bin, enter loadtool with fc-loadtool -h fcfam /dev/ttyXXX, and then flash it like this: flash erase 0 240000 flash program-bin 0 fwimage.bin I also made the change in the Magnetite source to enable MCSI pins at the pin multiplexing level for the FCDEV3B target, so if you hg pull this latest change, recompile fwimage.bin and flash it, you should be all set to start playing with MCSI - just issue an auw 0 2 command through fc-tmsh to enter the Bluetooth headset mode. Citrine has had MCSI pins enabled at the pinmux level all along, but it does not have the Audio Service component for switching audio routing modes. We previously discussed making Citrine do MCSI via a direct code change in L1 init, but I feel that it would be better to try MCSI in the known-good TI reference environment first. Going forward, I'm going to regard the mysterious flash boot issue as a non-problem until and unless we get reports of the problem happening on more boards than just my S/N 001. With this mysterious problem out of the way, my main focus is now going to be on finishing the automated calibration software, so that I can calibrate all of the boards which are currently still in my hands and finally send them out to the anxiously-waiting community members. Hasta la Victoria, Siempre, Mychaela aka The Mother _______________________________________________ Community mailing list Community@freecalypso.org https://www.freecalypso.org/mailman/listinfo/community