[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FBUS_FRAME_HEADER vs 0x00, 0x01
From: |
BORBELY Zoltan |
Subject: |
Re: FBUS_FRAME_HEADER vs 0x00, 0x01 |
Date: |
Thu, 23 Feb 2006 00:43:34 +0100 |
User-agent: |
Mutt/1.4.2.1i |
Hi,
On Thu, Feb 16, 2006 at 11:24:37AM +0100, Morten Bogeskov wrote:
> I'm trying to get a grip on the protocol used for communicating with my
> old nokia phoneš.
> However I've come to a grinding halt with sending/receiving packages
> Many requests starts with the:
> { FBUS_FRAME_HEADER, ...
> but some start with { 0x00, 0x01, ...
>
> Having plowed through the Docs catalogue I still can't figure out when to use
> what (and why).
If the docs aren't clear, look into the source.
> fx.
> (from nk6110.txt)
> ...
> 0x40: Security commands
> ...
> s Get IMEI { 0x66 }
> ...
>
> the frame looks like this:
> 1e 00 0c 40 00 05 00 01 66 01 41 00 35 45
> ^^ ^^ ^^ ^^
>
> from nk6100.c
> ...
> unsigned char req[] = {0x00, 0x01, 0x66};
> ...
> if (sm_message_send(3, 0x40, req, state)) return GN_ERR_NOTREADY;
> ...
>
> Where do I find where the "00 01" comes from and when to use "00 01 00"
> (FBUS_FRAME_HEADER)
0x40 commands are using just "00 01" frame headers, the other commands
require "00 01 00". We aren't know the reason (maybe the 0x40 commands
are older than the others).
Bye,
Bozo