Bc2000 (for the BCF2000 & BCR2000)

The problem with that "translation" is that your disassembler must
really understand your code. I'm jumping here so this location is
really code ... But I'm reading from here so it is data, ...
Disassembly is an art ;)

And some software developers put false instructions like "read data
@A0010" from one part of the program but in fact the data at @A0010 is
in fact instructions, ... (I don't know if my explanation is so
clear). But they use that in order to fool "intelligent disassemblers"
and so on automatic disassembly.

Take an ARM Instruction Sheet like this one:
http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf

But if you don't know anything about how assembler works and how to
understand assembler code, you would better start by something easier
than an hardware system firmware.


For those interested, I also made python programs to remove the sysex
 s firmware headers and footer for each packets and made individual
files for each of the blocks, ... 
And I found that between 1.07 and 1.10 for example some blocks are
identical in the sysex, so I think they have done that to provide
direct update from 1.03 (or lower maybe) and not incremental updates.


--- In bc2000@yahoogroups.com, "goyya76" <goyya76@...> wrote:
>
> --- In bc2000@yahoogroups.com, "Tony Cappellini" <cappy2112@> wrote:
> 
> > You don't need a disassembler to look at a sysex file, just use a hex
> > editor. It's just sysex
> >
> yeah of course - i did it, but i didn't understand anything so i 
> thought that the disassembler (maybe it's a disassembler targeted at 
> that specific chip) could "translate" groups of bytes into more 
> significant words/expressions etc...
>