How do you use the embedded debug probe on the Morello hardware board to connect to Development Studio (Morello Edition)?

Hi Jen, I can answer part of your question. The single USB connection gives access to the onboard Ulink debugger, the MCC management mass storage and the UARTs.
Thanks
Jon

Hi Jen,

Ensure you have the latest Arm Development Studio 2022.0M0 installed (Help > About Arm Development Studio IDE). If not, you can download from here:
https://developer.arm.com/architectures/cpu-architecture/a-profile/morello/development-tools#arm-development-studio

From the IDE menu, go to File > New > Hardware Connection, and give the Debug connection some meaningful name. For ease of file management (the connection will be defined in a .launch file), I recommend associating with your project. Click next, then select Morello SDP, which is the only available option (Add a new platform is unavailable in this release). Click Finish. You will now go to the Debug Configuration pane.

Select CMSIS-DAP from the Target Connection pulldown, then Browse button in Connection, and you should see your board pop up. Select that, and you should be able to debug. Navigate to Files tab to load image and/or symbols, and Debugger tab to control how you connect (just connect, debug from entry point...).

Regards, Ronan

Hello, I'm a beginner trying to debug a baremetal application running on the Morello board.

I followed the "User Guide" and "Running a standalone baremetal application" documents from release1.4. I created the "fip.bin" from "helloworld" executable, and copied it to "SOFTWARE" directory of storage device that pops up after plugging Debug USB cable. The AP port prints "hello" correctly. In Arm Development Studio 2022.0M0 I followed steps from the answer to the original question and I was able to view the following:

Below is the configuration I used:

I can see that some information is outputted like disassembly, memory contents, and registers. But there are errors and warnings in the "Commnads" tab like:

"ERROR(CMD16-COR107):
! Failed to load "helloworld"
! Unable to detect image type of file "/home/michal/morello_board/standalone_build/helloworld/helloworld""

"WARNING(CMD399-CMD38-CMD722):
! Failed to start the target
! The string "$ENTRYPOINT" cannot be interpreted as a positive int
! Entry point not set
WARNING(CMD407): Trying the entry point instead
ERROR(CMD426): Cannot find symbol to start or entrypoint, the file or load commands may be used to set the entrypoint"

Do you know what I may be doing wrong?

Also, should I somehow modify the compilation commands to output a file with symbols?

I assume that typically in IDE like this, it is possible to compile a program, set a breakpoint, run the program (possibly on external hardware), examine its state during a breakpoint and then proceed with execution, stepping line by line. Is such "line by line stepping" possible using Arm Development Studio 2022.0M0 and Morello board?

Thank you in advance.

Hi Michal

The errors you see coming from the Arm DS Debugger are because it is expecting an ELF image, possibly containing DWARF debug information.

The "helloworld" binary generated by the llvm-objcopy step is a plain binary, with no ELF wrapper or DWARF debug information.

An ELF version of the image is generated by the link step, but it looks like that is being overwritten by the objcopy step.

You'll need to:
- add "-g" to the compile step to add debug information
- change the output filename of the link and/or objcopy step, so that both helloworld.elf and helloworld (.bin) are generated
- rebuild

The helloworld binary is already loaded on the target, so there is no need for you to tell the debugger to load it too, however, you will need to load the debug symbols into the debugger, so add helloworld.elf into the "Load symbols from file" option in the debug configuration.

To avoid the helloworld binary from completing execution before you've had a chance to connect the debugger, you may need to add a branch-to self loop into the beginning of it.  Then, after connecting the debugger, you can stop, set the PC to the next instruction, and then continue running.

Please also take a look at
https://community.arm.com/support-forums/f/morello-forum/52905/how-to-load-a-bare-metal-el3-program-onto-the-hardware
and
https://community.arm.com/support-forums/f/morello-forum/52923/baremetal-tfa-payload-built-for-capability-mode-still-in-pstate-a64-on-el2-entry

Hope this helps

Stephen

Where "TOOLCHAIN" leads to "baremetal-release-1.4" branch of llvm-project-releases. I'm using ARM Development Studio version 2022.0M0 (build 202200006).

Do you know what may be the reason for this error?