9 years, 7 months ago.

cmsis-dap project problems generating firmware_bootloader.bin file for custom pcb

Hello to all!!!

I have designed a custom pcb board using the mbed-hdk. I have separated it in two boards, one for interface LPC11U35/501 chip as a 'flasher' board and another with the lpc1768 chip,an invensense mpu9250 and a fastrax up501 gps.

Initialy the 'flasher' board, without any firmware update connects to my pc as a CRP_DISABLD flash memory.

I have downloaded the github proyect from https://github.com/mbedmicro/CMSIS-DAP in order to produce the 'lpc11u35_lpc1768_if_mbed.bin' file but i cannot reproduce the steps written in http://mbed.org/handbook/cmsis-dap-interface-firmware

-The bootloader proyect in CMSIS-DAP\bootloader\mdk\lpc11u35\lpc11u35_bootloader works ok as described

-but the interface proyect doesnt, it generates the axf depending on the target used like CMSIS-DAP\interface\mdk\lpc11u35\Obj\lpc11u35_lpc1768\lpc11u35_lpc1768_if.axf

but the python script concat.py in tools/concat.py looks for an axf file in CMSIS-DAP\interface/mdk/lpc11u35/Obj/lpc11u35_lpc1768_if_mbed_bootloader.axf

Finally i have found that in the mbed-hdk there is a .bin called lpc11u35_lpc1768_if_mbed.bin and this works perfectly.

Really my questions is: It is this normal?? Have anyone working in the cmsis-dap proyect have updated some behaviour of it like be able to configure it for more TARGETS and hasnt updated the concat.py script.??

Thank you all for building this amazing comunity. cheers p8