[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] btd and btdm problem

You should undefine USE_IPASSIGN in bt_conf.h since you don't 
have an IPA server on your system. To avoid these problems we 
will change btdm shortly so that it won't exit when giving up 
on IPA and instead just behave as USE_IPASSIGN never was defined.

What about that seg fault ? Do you have logs on it ?

Generally if btdm fails to read local bd or you get command timeouts
this is basically always due to wrong baudrate or faulty HW. We run 
btdm as it is in the CVS without no problem. 


> -----Original Message-----
> From: Chou, Alexander T [mailto:alexander.t.chou@xxxxxxx.com]
> Sent: den 15 maj 2001 01:50
> To: 'bluetooth-dev@xxxxxxx.com'
> Subject: [bluetooth-dev] btd and btdm problem
> Hello all,
> The newest release (5/7) of the experimental multipoint btd 
> seems to have
> "broken" for us. I say this in quotes because it never really 
> worked for us.
> Here is the problem:
> in the old march release of the stack, btd would fail to get 
> a bluetooth
> address, and there is no communication with the hardware at 
> all. However,
> btdm would be able to retrieve an address, but then seg 
> faults immediately
> afterwards. The odd behavior occurs when we then run btd 
> (non-multipoint)
> again, it then works flawlessly. It seems that btdm does some 
> initialization
> in the bt.o driver that btd does not.
> However, now the newest release of btdm no longer obtains an 
> address and
> states that it "Found no IPA server" and shuts down when 
> starting SDP, but
> the btd still is unable to talk to hardware.
> here are the log files for the may release btd and btdm:
>  <<btd.ZIP>>  <<btdm.ZIP>> 
> thanks for any reply,
> Alex
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com