嗨对话框，
我有以下设置为生产线工具将第二个引导加载程序编程到OTP中，以及我的ETA中的组合图像进入闪存。
但是我收到了如下所示的错误日志，您有建议和解决方案吗？我还附上了图片的图片
11：48：45：409 [debug] [u_dll] [udll_dbg_init |296] >>> dbg_enable = [1]，dbg_level = [0x5]，dbg_out = [0x4]，dbg_clbk = [0xd80a7e]，dbg_file_path = [udll_debug.txt]
11：53：01：569 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [9]上不匹配
11：53：01：599 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [8]上不匹配
11：53：01：599 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [16]上不匹配
11:53:01:649[错误][U_DLL] [udll_main_thread | 1272] >>> ERROR: OTP IMAGE files do NOT match on com port=[7]
11:53:01:649[错误][U_DLL] [udll_main_thread | 1272] >>> ERROR: OTP IMAGE files do NOT match on com port=[11]
11:53:01:649[错误][U_DLL] [udll_main_thread | 1272] >>> ERROR: OTP IMAGE files do NOT match on com port=[6]
11:53:01:649[错误][U_DLL] [udll_main_thread | 1272] >>> ERROR: OTP IMAGE files do NOT match on com port=[14]
11：53：01：709 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [4]上不匹配
11：53：01：709 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [18]上不匹配
11：53：01：709 [错误] [u_dll] [udll_main_thread |1272] >>>错误：OTP图像文件在COM端口= [12]上不匹配
11:53:29:439 [ERROR] [U_DLL] [close_device | 2652] >>> ERROR: WaitForSingleObject in device_opts_t->ovlRd.hEvent WAIT_TIMEOUT com_port=[8]
11：53：30：439 [错误] [u_dll] [close_device |2687] >>>错误：wainforsingleObject在device_opts_t-> hthread wait_timeout com_port = [8]
11：53：30：469 [错误] [u_dll] [print_sys_error |4544] >>>错误：6：句柄无效。
11:53:30:469 [ERROR] [U_DLL] [reset_buffer | 2424] >>> ERROR: PurgeComm with handle=[cb8] com_port=[8]
11:53:30:469 [ERROR] [U_DLL] [udll_main_thread | 976] >>> ERROR: buffer reset on com port=[8]
11：53：31：549 [错误] [u_dll] [close_device |2652] >>>错误：wainforsingleObject在device_opts_t-> ovlrd.hevent wait_timeout com_port = [7]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [16]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [16]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>> ERROR: fw download on com port=[12]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [9]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：FW下载COM端口= [18]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：FW下载COM端口= [11]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [14]
11：53：31：679 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [14]
11:53:32:549 [ERROR] [U_DLL] [close_device | 2687] >>> ERROR: WaitForSingleObject in device_opts_t->hThread WAIT_TIMEOUT com_port=[7]
11：53：32：549 [错误] [u_dll] [udll_main_thread |966] >>>错误：FW下载COM端口= [0]
11:55:33:509 [ERROR] [U_DLL] [close_device | 2652] >>> ERROR: WaitForSingleObject in device_opts_t->ovlRd.hEvent WAIT_TIMEOUT com_port=[8]
11：55：34：509 [错误] [u_dll] [close_device |2687] >>>错误：wainforsingleObject在device_opts_t-> hthread wait_timeout com_port = [8]
11:55:34:509 [ERROR] [U_DLL] [udll_main_thread | 966] >>> ERROR: fw download on com port=[0]
11：55：35：509 [错误] [u_dll] [close_device |2652] >>>错误：wainforsingleObject在device_opts_t-> ovlrd.hevent wait_timeout com_port = [7]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>> ERROR: fw download on com port=[12]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>> ERROR: fw download on com port=[12]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [16]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [9]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>> ERROR: fw download on com port=[4]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>>错误：COM端口上的FW下载= [14]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>>错误：FW下载COM端口= [18]
11：55：35：759 [错误] [u_dll] [udll_main_thread |966] >>>错误：FW下载COM端口= [18]
嗨Liuluan002，
请您报告您正在使用的PLT SW的版本，也可以上传PARAMS.INI和PARAMS.xml文件以查看？
谢谢mt_dialog.
嗨对话框，
I am using the PLT sw: "DA14580/581 Production Line Tool v_3.170.2.36"
I have only find the "params.ini" and attached in the file, I have not found the "params.xml", could you please help?
嗨对话框，
I have updaload the params.ini in the previoulsly comments, you may need to take a look.
布罗尔，
liuluan002
嗨对话框，
The chipset I am trying to program is DA14583, Since I I read the UM-B-012, seems it already comes out the second bootloader in the OTP, right now I want to update my second bootloader, is any special setting I needs to make to make the PLT works for our production?
嗨Liuluan002，
The params.ini is the proper configuration file for your PLT version the params.xml file is for the latest version of the PLT. Also an additional question until the team checks the configuration file, i suppose that you have applied VPP in order to burn your OTP ? Also can you please check if the PC is recognizing the COM ports of the PLT tool ?
Regarding the bootloader and the 583, you can burn an additional bootloader to the 583 called an advanced bootloader (which is the secondary bootloader in order to implement the dual image), how the 583 is going to know about the advanced bootloader depends on the 0x7F10 address on the OTP header which dicates the offset and the length of the advanced bootloader. Regarding if there is a special setting to do that i am checking with our PLT expert, i will let you know as soon as i have some feedback for the errors that you get.
谢谢mt_dialog.
当我编写OTP时，我已经测量了VPP的电路板，它将它进入6.8V。此外，我也用具有相同PLT的OTP标题成功编程了一个新的DA14583板（应用标志1和荣笛2是否，DMA长度我使用03 BD而不是1F C0。），但我没有用第二个编程OTP图像。引导加载程序。
我今天也只制作闪光部分，一次为64个单位编程为16个单位，OTP图像和OTP标题未编程。它显示PC识别PLT工具的所有17个COM端口。17 COM港口令人犯了16 DUT和1金单位。
嗨Liuluan002，
As far as i can tell there is no provision to burn an additional image to the OTP via the PLT tool, the PLT starts the writing of the OTP at a specific offset (from the start of the OTP image ) there is no option to burn the OTP at a specific offset, i am still checking with the PLT expert to get some feedback on that. I assume that the errors that you get are because you are overwriting the factory 583 bootloader with the advanced bootloader, and when the tool reads back for verification it gets the ored values of the two bootloaders. Also checking if a work around is possible, perhaps by adding to the advanced bootloader image a 0x00 padding up to the address that the advanced bootloader should be located.
谢谢mt_dialog.
是因为它是由于从工厂预先制作的第二引导加载程序和OTP中的高级引导加载程序的重叠使系统无法启动，是此问题的任何解决方案吗？
嗨Liuluan002，
如上所述，仍在等待答复，我会尽快通知您，只要我得到了PLT专家的回复。
谢谢mt_dialog.
Hi,
I have a PLT hardware acquired from customer to develop the testing/programming of their product. My software is Csharp. I would like to get support on how to use PLT DLL libraries in csharp. Please provide contact details.
嗨anunez，
我们将通过邮件与您联系。
谢谢mt_dialog.
嗨对话框，
这个问题有什么更新吗？
嗨Liuluan002，
Sorry for the very late response, but the PLT experts were quite busy, so, as i ve been informed, there is no provision for the PLT to burn an advanced bootloader in the 583, the PLT assumes that the OTP should always be written from address 0 in order to boot from there. So you can follow the below guidelines in order to test burning the advanced bootloader in the OTP via the PLT tool:
谢谢mt_dialog.
Hi,
Can you please advise on how to power cycle and reset the DA14581 chip. Is there a Production Line Tool command line or using DLL?