View Single Post
Old 10-29-2012, 08:46 AM   #339
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by hawhill View Post
knc1: Are you sure it's tri-color? I've only ever seen green and amber, neither blue nor red... Or is this about the K4? BTW, I did not forget about having k3flasher talk to the battery controller. It would reeeeally help in situations like these. However, I'm unsure if we can readily use the SPI controller and what we need to do about chip select lines...
On the K3, it is - I have visually confirmed Red and Green.

On the DX, it should be - the firmware is written to control a tri-color led. But I don't have a DX to bork it bad enough to get it to "flashing red" state.

You should find "flashing white" during network boot loading.

On the others - not a clue.

I have only read the DX firmware in enough detail to say that we can access the battery state via the SPI bus the external chip is on.

I have not (yet) read the K3 firmware in enough detail to say the same thing about it.

Like nearly everyone else here -
I have to use my available hobby time for my own requirements first.
Public Service work gets whatever is left over.

Last edited by knc1; 10-29-2012 at 08:54 AM.
knc1 is offline   Reply With Quote