| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Use the start address inside the header entry, the start is relative
to the surrounding SDP record which is located in our base offset, when
writing it out also ignore four bytes of something (crc?).
|
|
The first non working version to dump the content of the sdp
to the terminal..
|
|
The sub entry might not be a SDP file so it is best to add the
read entry, add it to the list and then attempt to recursively
parse this one.
|
|
Make the code work/skip the other table and find the entries
at the given offset. This appears to work.
|
|
* The length of the table is not at a fixed position. We will need
to read the offset, seek there, read the data, convert it to the
host endianes.
* Prepare the code to work with offsets of 0...
|
|
* The two dummy bytes appear to be an offset, check that
they are zero and refuse to work when they are not.
|
|
We have derefenced that way before and would have crashed already.
|
|
* Ignore the value of the field there is no sematnic change
to the content of the file..
|
|
This library is intended to collect all generic/common funcitionality
of all Osmocom.org projects, including OpenBSC but also OsmocomBB
The library currently includes the following modules:
bitvec, comp128, gsm_utils, msgb, select, signal, statistics, talloc, timer,
tlv_parse, linuxlist
msgb allocation error debugging had to be temporarily disabled as it depends on
'debug.c' functionality which at the moment remains in OpenBSC
|
|
* This turns ipaccess-firmware.c into a plain helper, fix the
ipaccess name...
|
|
* We are not leaking anything... *yeah*, talloc rocks
|
|
|
|
|
|
* text3 seems to be a version as the text content starts
with a 'v'
* move the sdp_firmware into the ipaccess.h and declare
the function. The headers are returned through a list.
|
|
|
|
* The second magic number is only a short and it is
the same for all of my cases
* This also means that the first and second header
are the same which means the unknown 8 byte are
header and file size... and the 122 bytes are
actually multiple strings (just all empty on the
outermost SDP). Adding the strings left us with 120
bytes so we have two bytes of unknown usage..
* This is now capable of parsing outer and inner SDP
files and print their header.
|
|
* The internal SDP appears to have a different magic number
than the first entry and a slightly different packet format
* There are 8 byte of binary for at the beginning and the header
ends with a table pointing to some strings and then the actual
firmware follows.
* We currently only parse the strings of that header.
|
|
* Start parsing the sub SDPs with the same analyze method
|
|
Read everything we need to determine the version first and then
the rest. This will allow to be able to poke into the other SDP
bits.
|
|
The something3 points to the next start of the SDP
entry. The four bytes in front of the " SDP" are not
known and just discarded. Prepare to be able to
recursively parse the SDP header...
|
|
* Read the entry and print it out
|
|
|
|
|
|
|
|
I must have picked in the wrong section of these
files... There are some kind of header entries
that are all 138 byte long and this is the total
length...
|
|
|
|
|
