Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

MC68336 unknown HEX format ...

Status
Not open for further replies.
yura717

yura717

Advanced Member level 2
Joined
Aug 24, 2009
Messages
692
Helped
90
Reputation
178
Reaction score
89
Trophy points
1,308
Location
USA
Activity points
4,607
Hello there,
How to convert this format to Intel HEX format?
Microcontroller is Freescale MC68336

HEFF
H8323135373430322D30300D
H24B414B444B4D49444948494B9A
H3432D313520547275636B2020202020202020202020202020 202020202020202020202020202020202020
H60AF5
HB05FA
HCFF
Thank you.

- - - Updated - - -

HCFF is end of file /or end of record/
 

It isn't a normal hex format file, I would guess the first two characters are some kind of description of the following data and the rest looks to be ASCII codes.

If you are using this format often, I would recommend a program called "010 Editor" from https://www.sweetscape.com/010editor/ which is like a word processor for data files. With it you can build a conversion template so any data can be converted to and from this format.

Brian.
 

Before to make template ... you should understand format!
 

I was half expecting to see SREC format.

I would agree with Brian, it is not a standard HEX format.

It appears the start and stop codes are HEFF and HCFF respectively.

BigDog
 

Only the person who designed it knows for sure. If you look closely though, there is a pattern to the numbers.

1. all lines begin with 'H' so it is very unlikely it is part of the data itself.
2. all lines have an even number of characters (I'm guessing the one with all the 20 in it is truncated) so the chances are they are in pairs.
3. the last pair on the line is the two's compliment of the sum of all the previous characters so it is probably a checksum.
4. all except the leading 'H' when converted in pairs to ASCII are alphanumeric characters.

Conclusion:
It is similar to an Intel Hex format but instead of the lines starting with ':' they start with 'Hx' where 'x' is probably a line type or an address.
As to what the characters represent, like any listing they could be anything without knowing their context.

Brian.
 
  • Like
Reactions: yura717

    yura717

    yura717

    Points: 2
    Helpful Answer Positive Rating
Heff
h8323436383233372d303002
h2465746564b434b44494349484949494b66
h33331323642204c6f77204e4f7820547275636b204b69742020b9
h346756c6c204665617475726528547275636b204d616e756661637475726572203d204f7468657229206f72202059
h34261736963204665617475726528547275636b204d616e756661637475726572203d20474d29b9
h3546573742045434d2043617061626c65202062
h332373540323230302c2011
h3383630403134343058
h10001000b3d30aa55558f1122ff0031310002b2bc9f
h9000009000af7b1020000000042
h502fd
81e0cfccb88e70afdcb60c
h4d33ddab065
6f409f472f32f7ae8f55aed43ecaa0576eedb345cfccd7786ea9ab
afde11b481b06c0f7e1f0fccb1a69095498d49e957ac96ed80df20
30b3dd808f55cfddd23490b6900fb3fe9fccf50d38ad2c89d23486
9249a3cf7e1f5012988e3c71ad754d4a6d4ea92f80df0bc91670db
705a4391d234d1b0891fb6dfcfccd9ce8f5570891ddec6906eefd0
81a8532fd6701479ad7511146d4e3d337fdf0f8cb88e49a9508905
d315ca3067f33e1f350769b78e552e7520caed486db6bd5fc8d08e
4769ae299785f15482c463797e1ff2aca88ec8b55089d1fd90b020
7000196f2e3217b78f55ce75c3444f4b3e0f1509cfcc55cf6fa9cf
52b2ef43578c96ed7e1fc66eb88eb0bdae754f326d4ea2ec50dfc3
d10dd7b16ea9adf5d434d1b0891f4fabcfcc888e055178872ccab9
9309053580df509a4670b2bdae752f8d6c4d100f80b7efccae8ed6
 

Seems to be a generic ASCII format not specifically tied to the MC68336 either by addresses or machine code. Does this relate to a Caterpillar Engine EMU by chance?

Byte checksum sums to 0xFF

Not sure converting it to Intel or Motorola HEX would really help much, you'd need to associate the fields with specific addresses. Do you have any other examples which might have code associated with them? Or what tools generated the file?

- - - Updated - - -

That latter one describes about 300 bytes, appears truncated.

A quick decode gives
Code: 
<Heff> 4
Checksum valid (FF)
<h8323436383233372d303002> 24
2468237-00
Checksum valid (02)
<h2465746564b434b44494349484949494b66> 36
FWFVKCKDICIHIIIK
Checksum valid (66)
<h33331323642204c6f77204e4f7820547275636b204b69742020b9> 54
3126B Low NOx Truck Kit
Checksum valid (B9)
<h346756c6c204665617475726528547275636b204d616e756661637475726572203d204f7468657229206f72202059> 94
Full Feature(Truck Manufacturer = Other) or
Checksum valid (59)
<h34261736963204665617475726528547275636b204d616e756661637475726572203d20474d29b9> 80
Basic Feature(Truck Manufacturer = GM)
Checksum valid (B9)
<h3546573742045434d2043617061626c65202062> 40
Test ECM Capable
Checksum valid (62)
<h332373540323230302c2011> 24
275@2200,
Checksum valid (11)
<h3383630403134343058> 20
860@1440
Checksum valid (58)
<h10001000b3d30aa55558f1122ff0031310002b2bc9f> 44
    =0 UU  "  11
Checksum valid (9F)
<h9000009000af7b1020000000042> 28

Checksum valid (42)
<h502fd> 6

Checksum valid (FD)
<81e0cfccb88e70afdcb60c> 22
Checksum valid (0C)
<h4d33ddab065> 12
 =
Checksum valid (65)
<6f409f472f32f7ae8f55aed43ecaa0576eedb345cfccd7786ea9ab> 54
Checksum valid (AB)
<afde11b481b06c0f7e1f0fccb1a69095498d49e957ac96ed80df20> 54
Checksum valid (20)
<30b3dd808f55cfddd23490b6900fb3fe9fccf50d38ad2c89d23486> 54
Checksum valid (86)
<9249a3cf7e1f5012988e3c71ad754d4a6d4ea92f80df0bc91670db> 54
Checksum valid (DB)
<705a4391d234d1b0891fb6dfcfccd9ce8f5570891ddec6906eefd0> 54
Checksum valid (D0)
<81a8532fd6701479ad7511146d4e3d337fdf0f8cb88e49a9508905> 54
Checksum valid (05)
<d315ca3067f33e1f350769b78e552e7520caed486db6bd5fc8d08e> 54
Checksum valid (8E)
<4769ae299785f15482c463797e1ff2aca88ec8b55089d1fd90b020> 54
Checksum valid (20)
<7000196f2e3217b78f55ce75c3444f4b3e0f1509cfcc55cf6fa9cf> 54
Checksum valid (CF)
<52b2ef43578c96ed7e1fc66eb88eb0bdae754f326d4ea2ec50dfc3> 54
Checksum valid (C3)
<d10dd7b16ea9adf5d434d1b0891f4fabcfcc888e055178872ccab9> 54
Checksum valid (B9)
<9309053580df509a4670b2bdae752f8d6c4d100f80b7efccae8ed6> 54
Checksum valid (D6)
 
yes, you are right its related to CAT ECM
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top