I followed the hardware manual "TWR-LS1021A Reference Manual" section 5.3 "CMSIS-DAP debug support", however I cannot download the firmware described in that section,
1 Download the CMSIS-DAP firmware and documentation from http://compass.freescale.net/livelink/livelink?func=ll&objId=232410365&objAction=browse&viewType=1
So I want to switching back the mode, that is switching the usb port back to serial-to-usb mode. However, the board has no response even if I plug it to PC.The D2 LED is turned off after pluging. I cannot find answer form manual, so I have to ask for help from Freescale.
Thanks and Merry Christmas!
已解决! 转到解答。
The link to compass.freescale.net is internal link, as per my understanding it should not be mentioned in public board Reference Manual document.
UPD: I've sent you the contents of this link via Service Request.
The link to compass.freescale.net is internal link, as per my understanding it should not be mentioned in public board Reference Manual document.
UPD: I've sent you the contents of this link via Service Request.
Hi Adrian,
I have opened a service request (Service Request number 2-4786882631). Could you please help me to get the latest CMSIS-DADAP firmware for TWR-LS1021A-PB? The K20 chip is M28AGV.
BTW, I just want to use the USB-UART converter for the serial communication between Windows7 PC and the target board.
Hi Adrain,
I have a TWR-LS1021A-PB rev 2 board, and I am facing the same above problem with the usb to serial port, where LED D2 never turns on even after connecting to the Windows 7 machine. Can you help me out in fixing this.
I guess I will be needing the same link to recover the serial port.
Thanks
Nisar
Hi Alexander,
Thanks for your update!
It seems the flash of MBED circuit on TWR-LS1021A board is cleared, so I cannot restore it back to serial-to-usb mode. I'm using X4 board, the K20 chip is M20AGV.
Could you let me know how to restore it once there is update from engineers? Thank you very much for your help.
I've sent you the contents of the above link via Service Request. As per your reply, this solved the problem.
Factory confirmed the link is internal and should not be mentioned in public documentation. Hope they fix this in the next document revision.