How to choose the display 8/16/32 IEEE or Motorola?

[tranky]

You do it simple..
What is a byte?

I say to know!!!!
the byte is a set of 8 bits and has 256 vaiabili different from 0 to 255 (same thing goes for the ipv4 and finqui even the most idiot knows what that is)

[munro]

Perfect... this already makes you understand that if you would like to display a value from 0 to 255 in 16bit it would be impossible right?
Then let us always return to the speech that we were doing before on the hex dump..
Are the same values that are contained in a component that will dictate the correct display..
I don't know if it is clear..

[Khendal]

Perfect... this already makes you understand that if you would like to display a value from 0 to 255 in 16bit it would be impossible right?
Then let us always return to the speech that we were doing before on the hex dump..
Are the same values that are contained in a component that will dictate the correct display..
I don't know if it is clear..

BAMMMMM ... tears of terror

Impieghero' all night to try to figure out these 4 lines

Beginning to think by now...

Why is it impossible? If I have to represent a value from 0 to 255 then the 1-byte in 16-bit ( 2-byte), I will have always a 00xx ? no ?
I'm doing a slaughterhouse.

[tranky]

Perfect... this already makes you understand that if you would like to display a value from 0 to 255 in 16bit it would be impossible right?
Then let us always return to the speech that we were doing before on the hex dump..
Are the same values that are contained in a component that will dictate the correct display..
I don't know if it is clear..

the concept is clear that the view is attached to the bit of the component body but not knowing it at first glance, one switcha view until you have a shape drinking..
the question of the 8-bit to 16 bit of course you can do, 16bit has 65536 variables from 0 to 65535, so scale is different from 8bit, of course, in view 16bit, the top-of-the-curve, 8bit, stops at 255 to 65535 bits in the display to 16bit.. then that is a motorola or ieee should be on the basis of which type of memory holds the file open.
right?

[munro]

Exactly...

[Makx]

In fact, I'm just taking that as a cue this ecu EDC16C39... and right here I've noticed this thing is reading online... that is, I open the file with ECM Titanium, I chose the exact driver...and I open the 2d view.
At this point the ECM although I had already loaded the driver...and he knew already what it is...show me all with display 8bit IEEE and Zoom v to minimum or 32k with ECM2001 type... but in reality,' the correct display should be 16bit Motorola (as indicated in some guides, for example, to exclude the EGR with zoom to 16k).

So then I opened this post ... to understand why...and how you can slowly put together the pieces of the puzzle

To me, ecm titanium driver uploaded I motorola 16-bit for this family of controllers.

it is true that visually, taking the known areas is the only type of display that in a graphical sense.

Perfect... this already makes you understand that if you would like to display a value from 0 to 255 in 16bit it would be impossible right?
Then let us always return to the speech that we were doing before on the hex dump..
Are the same values that are contained in a component that will dictate the correct display..
I don't know if it is clear..

ok, it is just a kind of choice for display graphics and ease of understanding with respect to the table esa or binary...

but... then.. I don't know how to explain.... if I open the file to read the flash of a EDC15C7 (which is a component in 8-bit) value from table for one and the same address is in the table that in 2D graphics, by choosing the " display IEEE 8bit is the same. here not ago na the wrinkle.

if I open the EDC16C39 (I suppose, always to see the area of the flash but in this case I imagine to be a component 16-bit) with display motorola 16bit I see something graphically sensible, but every address in the chart has a value including TWO values on the table are hex...

if I had not had the driver, by the only vision of the hex, as I would never have guessed that I would have to use a display 16bit?

do I have to be already aware of how many bits has the component that I'm reading it, no matter what I see in the tabular hex to make a right choice of the graphical view?

and... are not at all well versed in electronics... motorola from IEEE? this also must be a choice made, already knowing the type of component that I want to read graphically?

[tranky]

You're to make a trip friend.
View as you it seems.. in the end you need to know the value of b.p. and the z-axis. The rest is fuffa

[tranky]

If you want to understand is fuffa, use IDAPro and open the dump that you want. Them understand the difference better.

[Khendal]

To me, ecm titanium driver uploaded I motorola 16-bit for this family of controllers.

it is true that visually, taking the known areas is the only type of display that in a graphical sense.



ok, it is just a kind of choice for display graphics and ease of understanding with respect to the table esa or binary...

but... then.. I don't know how to explain.... if I open the file to read the flash of a EDC15C7 (which is a component in 8-bit) value from table for one and the same address is in the table that in 2D graphics, by choosing the " display IEEE 8bit is the same. here not ago na the wrinkle.

if I open the EDC16C39 (I suppose, always to see the area of the flash but in this case I imagine to be a component 16-bit) with display motorola 16bit I see something graphically sensible, but every address in the chart has a value including TWO values on the table are hex...

if I had not had the driver, by the only vision of the hex, as I would never have guessed that I would have to use a display 16bit?

do I have to be already aware of how many bits has the component that I'm reading it, no matter what I see in the tabular hex to make a right choice of the graphical view?

and... are not at all well versed in electronics... motorola from IEEE? this also must be a choice made, already knowing the type of component that I want to read graphically?

Ah yes...this is a good trip... I would highly recommend if you find answers to these interesting questions...don't hesitate to write them down are always all ears

[Errecinque]

Exactly...

Here's to you, I would like to know why on ecm, we have "ieee " and "motorola " and on winols "hi/lo" and "lo/hi" . That seems to me the same thing. Why to 8bit, you cannot change your choice in 16-bit.