I have a CrossWorks project that I can download and debug with no problem using CrossStudio however when I try and download the project with CrossLoad it doesn't work, why could this be?
The most likely causes for this problem are:
- Different target property settings between CrossStudio and CrossLoad. CrossLoad does not share target properties (e.g. JTAG Clock Divider, Adaptive Clocking, etc) with CrossStudio. Instead you need to set them with the "-setprop" option (you can get the list of target properties using the "-listprops" option.
- Different solution file specified. Make sure the solution specified by the -solution option is the same as the solution you are using in CrossStudio.
- Different project selected. Make sure the project specified by the -project option is the same as the active project selected in CrossStudio. You can find out which is the active project in CrossStudio by clicking Project > Set Active Project, the active project is the one with a tick by it.
- Different build configuration selected. Make sure the configuration specified by the -config option is the same as the active build configuration selected in CrossStudio. You can find out which is the active build configuration in CrossStudio by clicking Build > Set Active Build Configuration, the active build configuration is the one with a tick by it.
Comments
2 comments
I'm trying to use Crossload (Arm 2.07) on an LPC1768 with a Crossconnect without any success.
Within Crossstudio I can compile and download it and it runs successfully after a reset. When using crossload, (without recompiling the code) it will run after the download but not after a reset. This is the commandline I'm using:
"crossload.exe" -target usb -setprop "Adaptive Clocking"="Auto" -setprop "JTAG Clock Divider"="2" -setprop "Erase All"="No" -setprop "Fast Memory Accesses"="Yes" -solution SquidBootLoader.hzp -project SquidBootLoader -config "THUMB Flash Release BL"
Any ideas what may be going wrong?
This is the wrong place to add this comment; I suggest you download using CrossLoad, then attach with CrossWorks and use Verify to verify that what is programmed is what you think should be programmed in the IDE. That is, are you really programming the same thing with CrossLoad that you are in CrossStudio? If verification succeeds, you are programming correctly and there is no difference. If there is a difference, then what you are loading with the two is different. You should open a ticket.
Please sign in to leave a comment.