You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It states "This debug probe is supported by the DAPLink project." In the upper right hand part of the page, I see "To compile a program for this board, use lpc11u35_501 as the target name." This leads me to believe I should be looking in the quarterly "0243_release_package_b403a07e.zip" for a firmware file named something like "0243_lpc11u35_501_0x0000.bin"
Note: I dont own a copy of Keil (nor a Windows machine for that matter), so I am unable to compile DAPLink firmware on my own. I see support for gcc has been discussed but that effort stalled: #197
Does anyone know why the lpc11u35_501 firmware isn't being built in the quarterly release or where I need to go to find this file? Any help is much appreciated.
The text was updated successfully, but these errors were encountered:
Through a bit of trial-and-error, I discovered that the 0243_lpc11u35_archpro_0x0000.bin firmware works on the DIPDAP-LPC11U35 debug probe. Debugging with pyOCD/gdb seems to work just fine on my Mac.
There is an issue with drag-drop programming, however: The target device does not reset after being programmed and the USB connection gets reset with a timeout error. Manually resetting the target is all that is required.
Hi @inindev, DIPDAP is built from DAPLink but is not main line on master, since it requires some custom modifications (like turning off mass storage).
Most lpc firmware images will work with the DIPDAP since the hardware is very similar. The archpro firmware expects to have a LPC1768 attached, so you will only be able to program it with drag-n-drop.
Reading the project page for the DIPDAP debug probe:
https://developer.mbed.org/platforms/DIPDAP-LPC11U35
It states "This debug probe is supported by the DAPLink project." In the upper right hand part of the page, I see "To compile a program for this board, use lpc11u35_501 as the target name." This leads me to believe I should be looking in the quarterly "0243_release_package_b403a07e.zip" for a firmware file named something like "0243_lpc11u35_501_0x0000.bin"
Note: I dont own a copy of Keil (nor a Windows machine for that matter), so I am unable to compile DAPLink firmware on my own. I see support for gcc has been discussed but that effort stalled: #197
Looking at the https://github.com/mbedmicro/DAPLink/blob/master/projects.yaml file, it appears that a section like the following is missing:
The file https://github.com/mbedmicro/DAPLink/blob/master/records/hic_hal/lpc11u35.yaml looks to have the target I am interested in:
Does anyone know why the lpc11u35_501 firmware isn't being built in the quarterly release or where I need to go to find this file? Any help is much appreciated.
The text was updated successfully, but these errors were encountered: