• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 548 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

V2.2.0 UART host_test not working

Matthias Mueller
Intellectual 380 points
Other Parts Discussed in Thread: CC2650

Hi Forum

In Addition to my previous post UART_open null pointer return I tried to use the host_test release (host_test_cc2650_app) from the stack as Zahid mentioned. The problem is, it also does not work!

The BTool can not access the USB dongle. And when I pause the application in the CCS, the application hangs between 0x1001bbd8 and 0x1001bbd6... the very same location where my new personal application (mentioned in the link above) jumps when it tried to access the UART (UART_open returns NULL pointer). Therefore, I strongly assume that the UART_open in the host_test release also returns a NULL pointer.

I changed nothing in the host_test, because we use on our custom PCB the UART0_TX on DIO_0 and the UART0_RX on DIO_1 which is automatically set correctly when I use the define CC2650DK_5XD. Also, the datasheet of the SABLE-x module it is mentioned to use this compiler option.

I strongly suspect that the UART driver on the V2.2.0 does not work. Has anyone from TI or anyone else has a running host_test release via UART? Or does it work on your side? What could it be?

I use CCS Version: 6.1.2.00015.


Cheers

Matthias

  • 0
    TI__Mastermind 33460 points
    Hi Matthias,

    It looks like your link to Zahid's response may not be working, feel free to send again if you'd like.

    I was able to analyze your issue, and it seems that your conclusion that the device is crashing due to a null handle being returned by the UART is correct. If the UART_open returns a NULL handle and then later the app tries to tx/rx to that UART then an exception will occur.

    Additionally, changing the define from CC2650DK_7XD to CC2650_5XD should be all that is required to pull in the correct board file found at (C:\ti\simplelink\ble_sdk_2_02_00_31\src\boards\CC2650DK_5XD) for BLE stack v2.2.

    However, I am confused about your hardware setup. Can you confirm that you are using a custom PCB with the SABLE-x module mounted on it?

    The usual reason why the UART driver returns NULL is because another resource is using the PINs required by the driver. Can you confirm that you have not modified the board file that came stock with the BLE stack?
  • 0 in reply to Sean2
    TI__Mastermind 33460 points
    Additionally, if possible can you provide a schematic or a schematic snippet that involves the UART connections of your design?
  • 0 in reply to Sean2
    Intellectual 380 points

    Hi Sean

    Thank you very much for your fast reply. Sorry about the dead link, I hope this should work now: UART_open NULL pointer return

    I tried now again it with a clean install of the V2.2.0 stack, and run the host_test again with the CC2650_5XD option. At first, there is a compiler error, that the identifier "Board_SPI1" is not defined in npi_tl_spi.c on line 153. According to the CC2650DK_5XD.h file, the SPI should be on other pins than the UART. And I did not change anything, therefore the option NPI_USE_UART should only enable the UART, right? In my opinion there should be a switch which uses Board_SPI0 define in npi_config.h when CC2650_5XD is defined (instead of Board_SPI1). I did so in this project to get the compiler to run, this is what I changed. In my last try I just uncommented the line.

    It still has the same problem, regardless if I use a compiler switch or I uncomment this line. The debugger hangs still at 0x1001bbd8.

    Do you or any of your collegues have any HW board to test this compiler option on your side? Even that there is a compiler error with the 5XD option shows, that this was not fully tested...

    Yes, we use a custom PCB including the SABLE-x module. I have attached a snippet of the schematic. We use level shifters between the module and a FTDI USB-to-UART converter: pretty basic stuff, I can not imagine that this could be a problem, right?

    What do you think?

    Thank you very much in advance

    Best Regards,

    Matthias

  • 0 in reply to Matthias Mueller
    Mastermind 6125 points
    Hi Matthias,

    Do you test this function with CC2650EM+smartRF06? In my test, it can work correctly with CC2650EM(7x7)+smartRF06+BLE Stack-2.2 HostTest project.
  • 0 in reply to Kimi Hu
    Intellectual 380 points

    Hi there


    No I did notz test it, but it works now: I have uninstalled the old V2.1 stack, recompiled everything and it does now work. Therefore it was an installation problem.

    But thank you for your suggestions