• State Verified Answer
  • Replies 7 replies
  • Subscribers 73 subscribers
  • Views 3773 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 109399
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF8001/MSP430; cannot receive/transmit after pairing

n.t.

Hi,

I'm trying to interface the nRF8001 using an MSP430 device (specifically Adafruit's breakout board and MSP430fg439) for sending analogue data from the sensor hosted by MSP430 out to a smartphone.

I have followed the example from this thread (devzone.nordicsemi.com/.../, the BLE Demo.zip), making adjustments to only to main.c, hardware.h, spi.c, and hal_aci_tl.c I have been able to pair my device with Nordic's UART android app. However, I cannot receive/transmit after pairing, even though there was no indication of unpairing. I have tried to diagnose the problem using a logic analyser: image description

I suspect there should be some activity in the MOSI, REQ, RDY, and RST line after pairing for handshakes, but I don't see it here, and I cannot figure out how to sustain this connection for transmission of data.

Thank you very much.

Parents
  • 0

    Runar,

    Thank you very much for following up.

    I have not figured it out.

    I believe you are correct about the lib_aci_init function. We've had to rewrite this function quite a bit to address the errors that arose from TI Code Composer Studio. We could not declare it as "lib_aci_init(aci_state_t *aci_stat)". This generated errors throughout from aci_state_t and aci_stat not always being identifiable.

    The way we write it at the moment (lib_aci_init(services_pipe_type_mapping, NUMBER_OF_PIPES, setup_msgs, NB_SETUP_MESSAGES)) generates no errors and allows for pairing but not transmission.

    The files for the project and the Serial Debug Log can be found here

    Thank you very much for your help; I very much appreciate it.

Reply
  • 0

    Runar,

    Thank you very much for following up.

    I have not figured it out.

    I believe you are correct about the lib_aci_init function. We've had to rewrite this function quite a bit to address the errors that arose from TI Code Composer Studio. We could not declare it as "lib_aci_init(aci_state_t *aci_stat)". This generated errors throughout from aci_state_t and aci_stat not always being identifiable.

    The way we write it at the moment (lib_aci_init(services_pipe_type_mapping, NUMBER_OF_PIPES, setup_msgs, NB_SETUP_MESSAGES)) generates no errors and allows for pairing but not transmission.

    The files for the project and the Serial Debug Log can be found here

    Thank you very much for your help; I very much appreciate it.

Children
No Data
Related
Terms of service