Menu

#48 reproducing (UART) buffer overruns with TestCase

open
nobody
btnut (45)
1
2006-04-26
2005-05-20
No

In some cases this test case results a buffer overrun
(on hci_layer) on the btnode.

General:
- one side is not a btnode (different speed,
bluetooth-stack)
- no ack communication architecture (I used a
request/reply for kind of flow control)

Java:
- no waiting time between connect, send, receive (COSE,
RESE, SERE)

C:
- turn on all debug messages (bt_hci.c, bt_hci_event.c)
- no sleeptime in sendmsg() (located in Thread STREAMER)

Discussion

  • Matthias Ringwald

    Logged In: YES
    user_id=687107

    this is very likely related to long critical section. see
    bug 1063795 for more details. A blind guess, after proping
    nut/os earlier, is that using timeouts leads to this
    problem. a better approach for timeout handling (just don't
    do it in the IRQ context, but during the next thread switch
    should be ok for most cases, where an application is waiting
    for something.

     
  • Mustafa Yuecel

    Mustafa Yuecel - 2005-05-24

    TestCase (java/c sources/hexfile/classes)

     
  • Matthias Dyer

    Matthias Dyer - 2005-07-07
    • summary: reproducing buffer overruns with TestCase --> reproducing (UART) buffer overruns with TestCase
     
  • Jan Beutel

    Jan Beutel - 2006-04-26
    • priority: 5 --> 1
     
  • Jan Beutel

    Jan Beutel - 2006-04-26
    • labels: --> btnut