Command line tool for production test fails with DA14531

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Bill Su
Offline
Last seen: 2 years 3 weeks ago
Joined: 2019-12-24 07:59
Command line tool for production test fails with DA14531

Hi Dialog supporting team,

I tried to run prodtest.exe (the command line tool for the production test under the SDK_folder\6.0.12.1020.2\binaries\host\windows\prod_test_cmds with the firmware SDK_folder\6.0.12.1020.2\binaries\da14531\prod_test\prod_test_531_1wire_P05.bin, result in otp_read commands failed, write_reg32 commands sometimes returned normal but sometimes failed.
The hardware setup is main board(376-18-B) & daughtet board (376-04-F) with UART connection to PC.
The detail result is as below, could you please look into this issue and provide full function of this tool supporting for DA14531?

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 write_reg16 50000000 008C
status = 0

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 read_reg16 50000000
status = 0
value  = 008C

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 write_reg32 07F40000 00000002
status = 0

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 read_reg32 07F40000
status = 0
value  = 00000002

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 write_reg32 07F40000 00000001
status = 0

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 read_reg32 07F40000
status = 0
value  = 00000001

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 write_reg32 07F40010 0999000F
status = 0

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 read_reg32 07F40010
status = 0
value  = 0999000F

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 write_reg32 07F40014 A4040409
status = 9

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 read_reg32 07F40014
status = 0
value  = A4040409

C:\Users\bsu\Desktop\Test Documents\Dialog\6.0.12.1020.2\binaries\host\windows\prod_test_cmds>Prodtest.exe -p 5 otp_read 7FD4 8
status = 10

Thanks.
Bill

Keywords: 
Device: 
PM_Dialog
Offline
Last seen: 6 months 3 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi Bill Su,

Hi Bill Su,

Thanks for your question online. Can you please read the AN-B-077: DA14531 Bluetooth Direct Test Mode from the DA14531 support portal? Since you are using 1 wire UART, are you using the correct configuration in your board? Please check Figure 4: Jumper settings for 1-wire UART P05. In addition, it would be very helpful to clarify a bit more what you would like to accomplish with the production test firmware. Keep in mind that you can also use the RF Master from the SmartSnippets toolbox. Refer to section 20 of the UM-B-083 SmartSnippets Toolbox User Manual (HTML) in order to fined how you can use the RF Master of the tool.

Thanks PM_Dialog

Bill Su
Offline
Last seen: 2 years 3 weeks ago
Joined: 2019-12-24 07:59
Hi PM_Dialog,

Hi PM_Dialog,

Thank you for the reply. I checked the configuration in my board and can't find any difference from Figure 4: Jumper settings for 1-wire UART P05.
I attached the picture of my board. Because some commands (such as write_reg16) returned correct result, I think UART connection works. I think the existing command link tool 'prodtest.exe' described in UM-B-008 (DA1458x Production Line Tool reference CLI, code in SDK folder 6.0.12.1020.2\utilities\prod_test\prod_test_cmds\prodtest) doesn't fully support DA14531. 

I plan to do the following steps in production test with the command line tool.
1. Write & read Bluetooth address in OTP Header.
2. Do crystal trim and burn into OTP Configuration Script, Mesure RF Tx power, Measure RF Rx RSSI.  We have already had our own code to communicate with spectrum analyzer, what we need is the commands to communicate with DUT for RF test functions (such as transmit continuous sine wave at the RF frequencies 2402/2441/2480MHz, get RSSI value). 
3. Read/write to any address of OTP area.
4. Read/write to any address of resister.
5. Reset the chipset.

Could you please update the tool in SDK 6.0.12.1020.2\utilities\prod_test\prod_test_cmds\prodtest to support testing DA14531?

Thanks.
Bill

Attachment: 
CYibin
Offline
Last seen: 1 year 11 months ago
Staff
Joined: 2017-12-14 02:48
Hi Bill,

Hi Bill,

We have created the Service Desk accounts for you to post your questions on it.

Could you create a ticket for this issue on Service Desk? On which I will share the tool for you.

Please email us if you can't access your SD account.

 

Br

Yibin