11 posts / 0 new
Last post
Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
Boot test mode

Hi Dialog team,

I have a problem with the connection manager's boot test mode.
Boot mode was successfully activated only with DEVKIT-B and dongle.
It fails on Pro board and my working DA 14580 device.
I will attach a log.

The following information is written in the connection manager's manual.
"Boot Test Mode" button - this activates the production test commands. The production
Test firmware must be loaded before this mode is entered.

我tried loading "prod_test_ 580.hex".
But the result was a failure.

Please tell me the necessary requirements for the connection manager boot test mode.

Best regards,
Sean

一个ttachment:
Device:
MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Sean666,

Hi Sean666,

What i can see from the log is that the tool downloads properly the fw and sends the reset command to the 580 but there is no response from the 580 side (pro kit and custom fw - try to boot as peripheral or as central and check if that makes any difference), so at least on the pro kit, make sure that the proper jumpers are in place (on the pro kit the jumpers that connect the UART with the FTDI's TX , RX, RTS and CTS ), also make sure that the COM port at the drop down box is the one that the pro kit receives data (the pro kit has two virtual ports).

Thanks MT_dialog

Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
Hi MT_dialog,

Hi MT_dialog,

I succeeded in connecting with the Pro kit.
The reason is because I connected SWDIO and SW_CLK jumper.
(I will report that RTS and CTS was not mandatory.)

These two terminals can not be connected to the custom device I created.

Please tell me how to start with Boot Test Mode with Connection Manager without connecting SWDIO and SW_CLK.
一个lso, please tell me whether the reset switch is required for the device to work with Connection Manager.

Best regards,
Sean

MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Sean666,

Hi Sean666,

I am not sure i get this, i dont see any reason for the connection manager not to be able to work with the SWDIO and SWCLK jumper pins connected, those pins are needed when the tool downloads the full_emb.bin fw to the 580, after the fw has been downloaded the device is able to operate over UART. So the tool have to download a fw to the 580 and this is done via those pins, you can work with the tool by bypassing the initial downloading procedure (that means that you will have to provide the fw in another way, UART download, or via an SPI). After the 580 has a fw running on the sysram then you can start in Boot test mode via the appropriate button. Regarding the reset, it is required in order start the bootloader running when downloading fw via UART or any other serial interface, the connection manager downloads the fw via JTAG that doesn't need a bootloader in order to load the fw to the sysram.

Thanks MT_dialog

Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
Hi MT_Dialog,

Hi MT_Dialog,

I examined using DEVKIT-B based on your answer.
我想询问以下。

What I did,
· Burned full_emb.bin on SPI-FLASH which DEVKIT-B has.
· Burning work set J4 in SPI_config.
next,
· Jumper inserted only for P0_4 and P0_5.
· TMS and TCK jumpers are not connected.
Then,
· I started the connection manager.
· Please refer to the log.

What I want to know is below.
· Operate DEVKIT-B in "Boot test mode" of "connection manager" without connecting TMS and TCK jumpers.

一个ttachment:
MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Sean666,

Hi Sean666,

一个s far as i can tell the log shows that the Connection Manager could not find the basic kit in order to download the fw, which is normal, since you have removed the SW jumpers. After the sw is downloaded into the 58x then the communication is via the UART not via the SW. So since you have the fw in the spi you can let the 580 boot from there, connect the UART port and hit the "Boot test mode" button so that the UART RESET command is sent to the 580.

Thanks MT_dialog

Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
Hi MT_dialog,

Hi MT_dialog,

I am still trying into the problem of boot test mode.

Use the pro board only to connect to the DA 14580 daughter board.

Connect the PC to the basic board.

Between the basic board and the pro board was connected as shown in the attached file.

The boot test mode is not activated.
I will attach a log.

Please tell me the correct connection between the basic board and the pro board.

regards,
Sean

Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
attached

attached

一个ttachment:
MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Sean666,

Hi Sean666,

I am sorry, but i am quite confused, you are using the basic kit in order to program a pro dev kit and issue commands from the basic's kit UART to the 580 that is attached to the pro kit, is there a reason for that ? Regarding your connections, i think that the UART wires should be switched (the wires on the table seem proper but if can see the wire coloring properly on the image you have switched the cables). Also please try the following:

1) Keep the connections on the boards as is, start the connection manager and leave the fw to be downloaded into the board.

2) Open the prod_test project from the SDK, compile it and donwload it via JTAG using keil.

3) Hit the "Boot Test Mode" with the proper UART selected and with no flow control.

Thanks MT_dialog

Sean666
Offline
Last seen:2 years 9 months ago
加入:2016-08-04 03:56
Hi MT_dialog,

Hi MT_dialog,

I am sorry for confusing you.

I only use the pro board as a relay of the DA 14580 daughter board and basic board.

一个nd I have prod_test_ 580.hex.

Please tell me the meaning of the word "switch cable" as you said.

That is, connect the DA14580 daughter board with the basic board (not using the dialog chip on the basic board board).
一个nd I want to work the boot test mode.

Best regards,
Sean

MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Sean666,

Hi Sean666,

I am not sure if i see the wires properly in the picture, but it seems to me that you have connected the TX of the FTDI with the TX of the 580 and the same for the RX side (again not sure if i am seeing the connections properly on the picture). At least on my side with the wiring that you have i can download the prod_test (build and download the prod_test file from the SDK and not the default fw that the Connection manager has) from keil and i am able to boot in Test mode from the connection manager.

一个lso just to make something clear, when you mention that you have prod_test_580, and because i saw in a previous post that you mentioned that you have burned that flash, you mean the flash on the pro dev kit ? If that is the case i dont see any connections between the flash and the 580 on the pro dev kit and also as soon as you open the connection manager the tool will download into the sysram its own fw, so appart from connecting the flash to the 580 pro kit you will have to hit the reset on the pro kit in order for the fw in the flash to be downloaded again.

So just to keep things simple follow the connections on the attached picture, plug in the USB only on the basic kit, open the connection manager an leave the tool to download the default fw, after doing that load the prod_test fw from the SDK (either download it via keil or hit the "Load firmware" in the connection manager and set the .hex file from the prod_test example in the SDK), as soon as the fw is downloaded hit the Boot Test button in the connection manager in order to command the 580 to start.

Thanks MT_dialog