I'll clarify a bit:
To boot you need to enter "emergency" mode first - turn off, turn on for 4sec, turn off, then turn on with USB stick inserted as described here http://www.home.agilent.com/agilent/redirector.jspx?action=ref&lc=eng&nfr=&ckey=670496&cname=AGILENT_EDITORIAL
For 6k series you need to have both BIN and JZP on USB stick (or even BIN only, seems that some or all 6k bootloader versions doesn't understand JZP, unlike 7k that understands JZP only).
For a permanent install you need to do it manually, so if you want just to try some bin - boot it from USB, but don't touch any JZP in scope's File explorer (that's where install is performed).
OK I've just found the first new thing I can do that wasn't possible with trials - CIR option for circular segmented memory.
Front-end is obviously different from the 6034. Interestingly the trigger channel uses the same front-end as the analogue channels.
Carrington, there are even bigger memories...
There are no bandwith options to enable with keys...
There are some NV capabilities flags programmed from factory also (one of them limits decoders usage on 2CH models).
I am aware that you can enable all the options and then set back the clock to keep these options enabled indefinitely. That's certainly livable. However, that's not a pretty solution, and it's nice to have the clock set properly for screen shots, etc.
I am aware that you can enable all the options and then set back the clock to keep these options enabled indefinitely. That's certainly livable. However, that's not a pretty solution, and it's nice to have the clock set properly for screen shots, etc.
This text just hit my eyeballs. Can't you set date to 12.1.2037 then apply options and roll back to current date? Then your screen shots would be correct etc. (2037 because Unix epoch is 1.19.2038.)
The only thing remaining is to see if the decoders can be made to work on 2-channel models
That is flash memory. J2400 looks intriguiing...
There is no need to open the scope at all to read the flash. Just telnet to VxWorks debug console and dump the uppermost memory addresses:
FFF00000-FFFFFFFF - bootloader
FFEF0000-FFF00000 - NV area:
FFEF0000 [7] - MAC address
FFEF0020 [2] - "feature register" (SEC option flag)
the rest (before FFEF0000) should be a C:\ file system
It should be possible to program flash from debug console too - by invoking the programming function with "sp" command, but this can brick the scope easily, so better I'll not publish a detailed instruction until there will be some clear plan what and where to program.
IMO, there is no need for raw flash access at current stage. The bootloader part is much more obscure to work with (there is no symbol table), all interesting stuff is in sys part, really no idea what to look outside JZPs now.
Changing the model type in NV will not work - Mike had tried my patch that sets 4CH flag in RAM and the scope just hung, so the only hope is some fine grained compatibility check patch in sys.
The other interesting direction is C:\bin\CmdLine.cmd file - it is not present by default, but it is possible to specify several parameters to sys in it (i.e. there are parameters to enable each feature w/o key - can be more handy than patching sys because they will stay there after updates), look for hasOption() calls.