Hi - just getting started using Ozone.
We're targeting an LPC4350. It has external SDRAM attached that needs to be configured prior to using it (i.e. downloading elf code to it). We've been doing this in other debuggers (JtagJet/Chameleon; JLink/GNUARMEclipse) by a two-step process that can be configured in the Chameleon and GNUARMEclipse setup: downloading the SDRAMSetup.elf, which the debugger does the reset, download (to internal ram), then run until main which configures the SDRAM; then download the App.elf (which downloads to internal ram, overwriting SDRAMSetup, and SDRAM), and no reset but start from the initial vector location and break at main.
I've been trying to do this with a custom TargetReset() in the .jdebug but not getting it to work. Could you provide a .jdebug example, or similar, how to go about doing something like this?
Thanks.
-Kevin
Target: LPC4350
OSX 10.11.6
Ozone 2.22j
JLink Ultra+
We're targeting an LPC4350. It has external SDRAM attached that needs to be configured prior to using it (i.e. downloading elf code to it). We've been doing this in other debuggers (JtagJet/Chameleon; JLink/GNUARMEclipse) by a two-step process that can be configured in the Chameleon and GNUARMEclipse setup: downloading the SDRAMSetup.elf, which the debugger does the reset, download (to internal ram), then run until main which configures the SDRAM; then download the App.elf (which downloads to internal ram, overwriting SDRAMSetup, and SDRAM), and no reset but start from the initial vector location and break at main.
I've been trying to do this with a custom TargetReset() in the .jdebug but not getting it to work. Could you provide a .jdebug example, or similar, how to go about doing something like this?
Thanks.
-Kevin
Target: LPC4350
OSX 10.11.6
Ozone 2.22j
JLink Ultra+