Skip to contentSkip to conversation

FX2 FW: conversion from Intel HEX to DVB USB "hexline"

DISCUSSION Antti Palosaari 2 participants 4 messages Nov 6, 2011 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Is there any simple tool (or one liner script :) to convert normal Intel HEX firmware to format used by DVB USB Cypress firmware loader?

Or is there some other way those are created?

Loader is here:
dvb-usb-firmware.c
int usb_cypress_load_firmware()

Antti

Signature · 1 line
http://palosaari.fi/
#1 lore raw

Hi Antti,

Quoted 8 lines · Antti Palosaari

Is there any simple tool (or one liner script :) to convert normal Intel HEX firmware to format used by DVB USB Cypress firmware loader?

Or is there some other way those are created?

Loader is here:
dvb-usb-firmware.c
int usb_cypress_load_firmware()

I'm sure that you have found something yourself in the meantime, but I used the attached script to convert .hex to binaries.

HTH,

--
Patrick Boettcher - KernelLabs
http://www.kernellabs.com/

#2 lore raw

Many thanks!

Actually, I was just started to write similar Python script! You got maybe 15min late but still 15min before mine was ready :)

Format was nothing more than convert ASCII hex values to binary bytes and stripping out all white spaces and Intel HEX start code ":".

Why it was initially converted to binary and not used Intel HEX as it is? I think you know, as a original author, history about that decision?

regards
Antti

Quoted 20 lines · Patrick Boettcher

Hi Antti,

Quoted 8 lines · Antti Palosaari

Is there any simple tool (or one liner script :) to convert normal Intel HEX firmware to format used by DVB USB Cypress firmware loader?

Or is there some other way those are created?

Loader is here:
dvb-usb-firmware.c
int usb_cypress_load_firmware()

I'm sure that you have found something yourself in the meantime, but I used the attached script to convert .hex to binaries.

HTH,

--
Patrick Boettcher - KernelLabs
http://www.kernellabs.com/

Signature · 1 line
http://palosaari.fi/
#3 lore raw
Quoted 10 lines · Antti Palosaari

Many thanks!

Actually, I was just started to write similar Python script! You got maybe 15min late but still 15min before mine was ready :)

Format was nothing more than convert ASCII hex values to binary bytes and stripping out all white spaces and Intel HEX start code ":".

Why it was initially converted to binary and not used Intel HEX as it is? I think you know, as a original author, history about that decision?

Because doing string-parsing and evaluation in the kernel is something I usually avoid. And it can't sure be done within 300 bytes (the size of the perl script). Also the .bin is smaller in term of size compared to the .hex.

--
Patrick Boettcher - KernelLabs
http://www.kernellabs.com/