I'm using hex2bin to convert a hexfile with several gaps in it. But I have found that if the hex file ends in a line with zero bytes, hex2bin will stop there and not process the rest of the file. An excerpt of the file is below: :101F2000E780BE72456200FF1F1341FD88EF00008D :001F3000B1 :101F40000100020103020403050406050706080751 But if I delete the zero byte line as shown hex2bin will convert correctly: :101F2000E780BE72456200FF1F1341FD88EF00008D :101F40000100020103020403050406050706080751 Or if I add a byte to that line hex2bin will convert correctly: :101F2000E780BE72456200FF1F1341FD88EF00008D :011F300000B0 :101F40000100020103020403050406050706080751 This is a critical problem since my TI tools will create hex files that have zero byte lines (which is a perfectly valid hex file)
Email the tech support address with your sample file that has a problem, and Keil can decide whether and when to fix it. Keil employees do read this message board, but it's not their primary means of bug reporting. I can't say whether they'll fix it, but hex2bin has always felt old to me, like they last compiled it for DOS 3.3 and are still using the same .exe. I see the copyright date in the banner is 1995. I wouldn't bet my project on a fix soon.