[PATCH] Cochran_commander refactoring

[Jef Driesen]

On 19-12-14 21:23, John Van Ostrand wrote:
> I did more investigating of setting commands and encoding. I've updated 
> the
> trac wiki with the full information. It should be complete but it's not
> tested or strongly verified. There may be mistakes.
> 
> I did some testing today reading raw data to see if I could download a
> usable memory dump for the dump function and avoid all that work done 
> in
> _dump and eliminate the need for cochran_download.c.
> 
> The read command (0x15 <start> <bytes>  0x05) only reads logbook and 
> sample
> data. I suspected that the gap between logbook and sample contained 
> config
> or other data but that isn't the case. There is no gap between 
> Commander
> logbook and samples and the EMC has no data of significance there.
> 
> Also, when asked to read past the end of data on the Commander, It 
> returns
> 0xFF for data that doesn't seem to be there. For example, the Commander 
> I
> have has rolled the sample data buffer so all the memory has been 
> written.
> Sample data stops at 0x100000 (1MB). When I asked for 8MB of data I got 
> 7MB
> of 0xFF.
> 
> Unless i discover a new command to read data I won't be able to deliver 
> a
> raw memory dump.
> 
> I'm also no closer to deciphering the feature data from the computer so 
> I
> don't know how much memory is present and enabled.

I'm not sure I'm understand what you're saying here. First you say you 
can download 1MB of data. But then you say you can't download a memory 
dump? I don't know what you consider a memory dump, but I would say it's 
that 1MB of data! Combined with the id, misc and config blobs that has 
everything we need. I have no idea what else you want.

PS: Can you send me the data from your Commander too. If you have data 
from the other models, I would like to have a look at that too.

Jef