ACI STATUS ERROR UNKNOWN

RE: ACI STATUS ERROR UNKNOWN

David Edwin — Mon, 12 Oct 2015 06:08:24 GMT

Actions requested: 1. Run the efm_ble_aci_transport_layer_verification to verify that your SPI connections are good. This uses the Echo command and the Echo Event to verify that the SPI is working as expected. This is a loopback test. Manually verify that the Echo Event is the expected event. (i.e the data sent and received are identical).

Can you give me an SPI trace of the Commands and Events that are being sent out. (MISO, MOSI, SCK, REQN and RDYN ), a trace using the salea analyzer is helpful on the example

= Let me know your results.

RE: ACI STATUS ERROR UNKNOWN

terry — Sun, 11 Oct 2015 23:26:36 GMT

Hi I used EM32 port on github, It is working EZR32(EMF32 processor with Radio) Development kit, the same code not working on our own hardware, so I am not sure it is software or hardware issue

RE: ACI STATUS ERROR UNKNOWN

David Edwin — Fri, 09 Oct 2015 04:56:25 GMT

If you are sending the command(C) 0x14, according to the datasheet of the nRF8001 , that command is OpenRemote pipe that needs a a parameter. I.e. the Length is expected to be 1. However "C : 1, 14 ", means that the remote pipe parameter is missing.

Even if you were printing it as Decimal i.e. 14 == 0x0D, the Command is still incorrect as there are no parameters for the Command. 0x0D is SetLocalData, which has a length longer than 1.

The Command Response Event is also documented in the nRF8001 datasheet. "E : 3, 132, 128, 130" , means an Event length of 3, CommandResponseEvent (0x84 == 132) , Command code of 128 == 0x80, which does not even exist in the datasheet and the status code of 130 == 0x82 which means, 0x82 ACI_STATUS_ERROR_CMD_UNKNOWN Unknown command.

This is very likely that the ACI command sent was not correct or has invalid parameters.

Have you verified your SPI using the Echo Command and Echo Event loopback so that the SPI issues do not get in here and confuse the issue. Look at the ACI transport verification example in the Arduino SDK and the porting note for the nRF8001.

Are you using the EFM32 port on github ? If so please post an issue on the github as well. OR Are you building your own driver for EFM32 ?