使用外部主机的CYBLE-212019引导加载错误代码0x4004

你好，
我用CyBur-212019使用一个堆栈引导加载程序。我能够成功地使用UART外部嵌入的主机引导字符串图像。在引导加载过程中，引导加载程序报告错误0x400。从CytLtDr.UtiL.H，0x400是CyrthyelybTrdRy掩码和CyrthyeleRead数据的组合。
我重新生成.CyACD文件并再次启动引导加载。对头文件（CYACD文件中的第一行）进行了验证，但是对于UART发送的字符串行，引导程序没有响应。嵌入式主机无限地等待引导加载程序的响应。关于调试这个有什么建议吗？
编辑：
代码陷入困境
int CybTLDR.TeleDATA（无符号CHAR*INBUF，INT INSIZE，UNCORCHARCHAR*UTBUF，INT OUTSIZE）
{
INTRR = GY-COMM& & G.DeDeDATA（INBUF，INSIZE）；
如果（CyReTyRealEng=＝Err）{
Err＝GyCAMM & G. Read DATA（OutBuf，超大）；
}
如果成功了！= Err）
厄尔尼诺；
返回错误；
}
GyCAMM & Gt；Read DATA（）无限地等待引导加载程序响应。
示波器：
在范围上，BLE UART信号看起来不像方波。它看起来像是一个RC电路充电信号。这意味着UART在重新启动时没有初始化。在这一点上，这可能是因为Bootloader没有踢进去，或者芯片坏了。我怀疑第二个是真的。虽然我可以使用SWD接口来反射Bootloader，但我想调试这个问题，而不需要重新启动Bootloader，了解损坏的原因以及如何克服它。对此有何想法？
谢谢
德黑拉杰



     以下为原文
  Hello,
I am using CYBLE-212019 with a single stack bootloader. I was able to successfully bootload a string image using an external embedded host over UART. During bootloading, bootloader reported error 0x4004. From cybtldr_utils.h, 0x4004 is a combination of CYRET_ERR_BTLDR_MASK and CYRET_ERR_DATA.

I regenerated .cyacd file and started bootloading again. The headers(first line in .cyacd file) are verified but there is no response from the bootloader for the string line sent over UART. Embedded host is infinitely waiting for the bootloader response. Any suggestions on how to debug this?

EDIT:
Code is getting stuck in

int CyBtldr_TransferData(unsigned char* inBuf, int inSize, unsigned char* outBuf, int outSize)
{
    int err = g_comm->WriteData(inBuf, inSize);

    if (CYRET_SUCCESS == err){
        err = g_comm->ReadData(outBuf, outSize);
    }

    if (CYRET_SUCCESS != err)
        err |= CYRET_ERR_COMM_MASK;

    return err;
}


g_comm->ReadData() is infinitely waiting for the bootloader response.

OSCILLOSCOPE:
On the scope, BLE UART signal doesn't look like a square wave. It looks like a RC circuit charging signal. This means that UART is not initialized upon BLE reboot. At this point, it could be because bootloader didn't kick in or the chip went bad. I doubt the second is true. While I can always reflash bootloader using the SWD interface, I want to debug this issue without re-flashing bootloader and understand the reason for corruption and how to overcome it. Any ideas on how to proceed on this?

Thanks
Dheeraj