prod_test "void hci_custom_action_cmd(uint8_t *ptr_data)" | Dialog Semiconductor customer support - 雷电竞下载app,雷电竞官网登录,雷竞技安卓下载

4 posts / 0 new

Last post

Thu, 2016-11-03 10:40

ciano

Offline

Last seen:2 weeks 3 days ago

加入:2014-10-03 08:13

prod_test "void hci_custom_action_cmd(uint8_t *ptr_data)"

Hi Dialog,

We are building our own prod_test.bin, and we want to add some tests in "void hci_custom_action_cmd(uint8_t *ptr_data)".

We have tried to modify the function for testing the behavior... so we did like this
void hci_custom_action_cmd(uint8_t *ptr_data)
{
struct msg_custom_action_cfm s;
s.packet_type = HCI_EVT_MSG_TYPE;
s.event_code = HCI_CMD_CMPL_EVT_CODE;
s.length = 5;
s.param0 = 0x01;
s.param_opcode = HCI_CUSTOM_ACTION_CMD_OPCODE;
s.data = ptr_data[0]+10; // MODIFIED by +10
uart_write((uint8_t*) &s, sizeof(s), NULL);
}

so it passes until our custom command with input = 0x34.
If we leave the output equal the input in "void hci_custom_action_cmd(uint8_t *ptr_data)", then it all passes.

Now for our question:
In general, how is "void hci_custom_action_cmd(uint8_t *ptr_data)" intended to be used?
In which testcases are "void hci_custom_action_cmd(uint8_t *ptr_data)" used?
and which input values are reserved and used by other test cases?
Which input values may we use for our custom test without interfering with other testcases?

Best Regards,
Ciano Frost
Denmark

Device:

DA14580

Tue, 2016-11-08 16:25

MT_dialog

Offline

Last seen:2 months 2 weeks ago

加入:2015-06-08 11:34

Hi ciano,

I dont quite understand what is the reason for the +10 to the ptr_data[0], the custom function is triggered when the command operation code is 0x40D0, that is the op code that a command should have in order for the 580 to execute a custom function. If you want to execute more than one custom function you will have to tag the custom functions and place the custom tag in the payload of the command.

Thanks MT_dialog

Thu, 2016-11-17 21:19

(Reply to #2) #3

ciano

Offline

Last seen:2 weeks 3 days ago

加入:2014-10-03 08:13

Hi Dialog

yes, I guess we need to step back here, to clarify our question.

We are using the PLT and want to add a selftest function in prod_test.bin. According to PLT parameter file this can be initiated with the following lines in the params.ini file
custom_data_enable = true
custom_data_value = 01

so far so good.
For catching this command in prod_test.bin with value argument = 0x01 we have to modify the function "void hci_custom_action_cmd(uint8_t *ptr_data)" in customer_prod.c
这就是我们需要一些支持明星ted.
Now the input argument is "uint8_t *ptr_data".
Question: how much data is stored at ptr_data ... what is at ptr_data[0] , ptr_data[1], ptr_data[2], ptr_data[3]?
and how should we interprete this data?

Best Regards,
Ciano Frost
Denmark

Fri, 2016-11-18 15:29

MT_dialog

Offline

Last seen:2 months 2 weeks ago

加入:2015-06-08 11:34

Hi ciano,

Since this is custom command there is no implementation in the fw side, there is no use for this command from the PLT tool for other commands, if you check the fw you will see that this is an empty command, so you will have to add additional implementation according to the tag that you ve entered in the params.ini file. So in order to access this command you will have to add the tag 0x40D0 in front of the 0x01 (if you want to test it via UART with a simple terminal). For example lets say that we want to implement a custom command that will have a tag of 0x34 so after implementing code in the prod_test fw for parsing the command, when we send from the UART port 0x01 D0 40 01 34, the code should see the tag and execute the function accordingly.

0x40D0 -> The tag for the custom command opcode

0x01 -> the length of the payload

0x34 -> the tag for executing the proper custom test

The ptr_data its just a uint8_t pointer that points to the start of the data send by UART. The ptr_data[0] will have the first byte of the payload of the command that you ve just sent, in the previous example it will contain the 0x34.

At the PLT tool case, in the param.ini file the value that you ve set at the custom_data_value will tag the custom command that you would like execute, in your case you ve set 0x01 as a custom command tag.

Thanks MT_dialog