Home > other >  About the boot and the APP. Hex file manually merge into burning. Hex in '05,' began to li
About the boot and the APP. Hex file manually merge into burning. Hex in '05,' began to li

Time:09-24

Recently in the APP and boot merger, general manually merge is to boot. In the end of the hex statement: 0000001 ff and: the beginning of the 04000005000000 c136 into linear address record after removing copy and paste the APP. Hex, suddenly found the merged. Hex 0 linear address record is used. The APP: 040000050000020 c116, after watching him afterwards. The map files found this record is _main. O address, does show that SCM operation will only start from the APP's main operation rather than the main began to run in the boot, so don't cause the boot is skipped useless?

CodePudding user response:

Your bootloader program, there is no main main program?

CodePudding user response:

Consult the building Lord, what's the use of hex merge tool?

CodePudding user response:

Can have a try, to merge the 00000001 ff removed the app, then add the boot to the behind

CodePudding user response:

reference 4 floor winnerwei1 response:
can have a try, to merge the 00000001 ff removed the app, then add the boot to the behind

Is the app to the back of the boot?

CodePudding user response:

Why do you want to manually merge, APP is the PRM or similar documents can be allocated in the address, and then compiled automatically merged,

CodePudding user response:

reference datao125 reply: 3/f
consult the building Lord, what's the use of hex merge tool?

No, has always been manually close,

CodePudding user response:

refer to 7th floor Java6c_c6 response:
Quote: reference datao125 reply: 3/f
consult the building Lord, what's the use of hex merge tool?

No, has always been manually, using the

Simple also, delete a row put tail,
  • Related