Export to GitHub

btstack - issue #357

My code doesn't work on eZ430-RF2560 since revision 1951 (hci.c modifications)


Posted on Nov 26, 2013 by Helpful Cat

Hello,

I'm developping on eZ430-RF2560 kit with BTstack for a while. My problem is that since last update (r1951) my software doesn't work any more.

It seems there are problems on acl and even packet size. These problems were probably already present before but didn't seen because of non presence of asserts in hci.c.

Is there something wrong in my application that I have to correct?

Notice that my board communicates with an Android app and I can't connect from this app.

My application work with previous BTstack versions but some time I get "h4_process: invalid packet type 0xff" message at board reset. But after a second reset it works.

If someone has a suggestion... Thanks

Dimitri

Comment #1

Posted on Nov 27, 2013 by Helpful Cat

I saw changes on last revision but my problem is not resolved.

The last assert correction in "hci.c" seems ok, it's what I expected. Now the if condition correspond to the log message. (// assert packet is complete
if (acl_length + 4 != size){ ...)

But my problem is, I still get even_handler messages and my device doesn't go discoverable.

Comment #2

Posted on Nov 27, 2013 by Helpful Cat

I tryed to compile the SPP Counter example with the last revision. The behavior is the same. I get an error on 0x54 HCI event.

Comment #3

Posted on Nov 27, 2013 by Swift Ox

Hi Dimitri. It might be better to post on the dev list. Sorry for the HCI packet asserts. I think they are correct now. if you get "invalid packet type.." then bytes got lost from the UART, which shouldn't happen. You could try slower UART speeds.

Could you find the last revision that worked for your setup? :)

Comment #4

Posted on Dec 19, 2013 by Swift Ox

HI Dimitri

I just run the SPP Counter example from SVN on the MSPEXP430F5438 without problems. Could you try a clean checkout or so?

Status: Fixed

Labels:
Type-Defect Priority-Medium