Hello @all,
I have a problem using Production test with the development kit.
我正在使用从SDK_3.0.4.0的下载CUST_PROD_TESTES5。
A) After command xtrim en the connection breaks down.
DIS or other things no longer possible
(see log below)
b）由于UM-B-008（第7.15章）应该有3个信号。
I only get RC16M on P0_7
Did I miss something.
Production Test:
.\DA14580_SDK_3.0.4.0\DA14580_SDK_3.0.4.0\binaries\da14580\prod_test
cust_prod_testES5.hex
D:\Debug>prodtest.exe -p18 xtrim rd
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 00 00 00
<==== Rx =====
event : 0x0E
length : 0x05
parameters: 0x01 0x80 0x40 0x00 0x00
Payload : 0E 05 01 80 40 00 00
status = 0
trim_value = 0
D:\Debug>prodtest.exe -p18 xtrim wr 500
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 01 f4 01
<==== Rx =====
event : 0x0E
length : 0x05
parameters: 0x01 0x80 0x40 0x00 0x00
Payload : 0E 05 01 80 40 00 00
status = 0
D:\Debug>prodtest.exe -p18 xtrim rd
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 00 00 00
<==== Rx =====
event : 0x0E
length : 0x05
参数：0x01 0x80 0x40 0xF4 0x01
Payload : 0E 05 01 80 40 F4 01
status = 0
trim_value = 500
D:\Debug>prodtest.exe -p18 xtrim inc 50
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 03 32 00
<==== Rx =====
event : 0x0E
length : 0x05
parameters: 0x01 0x80 0x40 0x00 0x00
Payload : 0E 05 01 80 40 00 00
status = 0
D:\Debug>prodtest.exe -p18 xtrim rd
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 00 00 00
<==== Rx =====
event : 0x0E
length : 0x05
parameters: 0x01 0x80 0x40 0x26 0x02
Payload : 0E 05 01 80 40 26 02
status = 0
trim_value = 550
D:\Debug>prodtest.exe -p18 xtrim en
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
有效载荷：80 40 03 02 00 00
<==== Rx =====
event : 0x0E
length : 0x05
parameters: 0x01 0x80 0x40 0x00 0x00
Payload : 0E 05 01 80 40 00 00
status = 0
D:\Debug>prodtest.exe -p18 xtrim inc 50
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 03 32 00
status = 9
D:\Debug>prodtest.exe -p18 xtrim dis
[info] Connecting to COM18
[info] COM18 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 05 00 00
status = 9
D:\Debug>
Hello Josef,
thanks for the extensive logging.
at first glance I think you are using P0_4 and P0_5 for UART communication?
These are the default communication ports when using cust_prod_test_es5.hex.
The problem is that P0_5 is also the port at which the Xtal 16MHz signal will be outputted, when doing this, communication over P0_5 is lost.
If you could change the UART communication to P0_0 and P0_1 in the Keil project, and rebuild the .hex file again, It should work.
The change must be done in periph_setup.c :
// Only one of the following lines must be uncommented.
#define UART_P04_P05
//#define UART_P00_P01
//#define UART_P14_P15
Would the change be possble for your hardware?
Best regards, BB_Dialog.
Hello there,
I found the related section at AN-B-020 cap. 7.1.
It was a bit misleading here, because everything is described with default UART Port setting.
通过GPIO修剪时不可能使用P0_4 / P0_5更清晰的声明“将阻止此。
A solution with selectable GPIO Signal output would be nice.
What's about the other 2 Signals described but not seen?
With regards, Josef
Another question:
is it possible to share the information from HW "TEST_CTRL_REG" definition?
BR
Josef
Hello Josef,
actually 4 clock signals are mapped to 4 ports.
Except the mapping, the 4 ports must be set as output to have the signal available.
The command in Connection Manager or in the CLI tool ProdTest.exe only outputs the 16 MHz from the Xtal oscillator at P0_5.
The other ports are not set as output as far as I know.
The 4 clocks and their ports:
P0[5] = XTAL16M_clk
P0[6] = XTAL32K_clk
P0[7] = RC16M_clk
P1[0] = RC32K_clk
If you like to see the other clocks too, you have to define the 3 other ports as output.
e.g. P0_7:
Register P07_MODE_REG (0x50003014) ; PUPD = 11
Best regards, BB_Dialog
Thanks for the answers above.
One more question:
I added configuration #define UART_P04_P05 to prod_test project.
(P0_2/P0_3 for UART use, due to higher download speed).
Download by Windows SmartSnipptes V3.2 Application and the using Windows command line for "prottest.exe command" works fine.
When using SmartSnipptes by command line application, I have problems with download.
command:
.\SmartSnippets.exe -type Booter -chip DA14580-01 -com_port 18 -gpio P1_2 -uart P0_2 -file D:\Bluetooth_SMART\F-Test_Test\cust_prod_test_ES5-P2_3.hex
(顺便说一下:选择类型uartBooter documentation AN-B-020 seems not correct)
I tried the Reset Bottom from evaluation board several times at different timings after starting command.
Console output:
：\ bluetooth_smart \ f-test_test> doprodtest_p23.bat
从文件d：\ bluetooth_smart \ f-test_test \ cust_prod_test_es5-p2_读取20964个字节
3.hex.
连接到COM18端口已成功打开。
Started download procedure...
Timeout: Reset signal not detected for more than 15000 msecs.
Successfully disconnected from port COM18.
Failed downloading firmware file to DA14580.
Error while waiting to receive STX from FTDI device.
D:\Bluetooth_SMART\F-Test_Test>DoProdTest_P23.bat
从文件d：\ bluetooth_smart \ f-test_test \ cust_prod_test_es5-p2_读取20964个字节
3.hex.
连接到COM18端口已成功打开。
Started download procedure...
Please press the hardware reset button on the board to start the download proces
s.
Timeout: Reset signal not detected for more than 15000 msecs.
Successfully disconnected from port COM18.
Failed downloading firmware file to DA14580.
Again, did I missed something?
Any new ideas regarding the command line topic ?
Hello there,
this morning I did an update on latest Smart Snippes 3.4
这解决了这个问题！
Ticket can be closed.
With regards
Josef
Hello Josef,
thanks for the feedback!
Best regards, BB_Dialog.