[mbedmicro/pyOCD] Support for S5JS100 Needed (#604)

[Andrew Chong]

cc @flit @mmahadevan108

Please add support for debugging S5JS100 (id: 3701) with pyOCD. This would enable debugging with Eclipse, GDB Server, and scripting with Python.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[Chris Reed]

Thanks! I forgot the name of the S111 board was S5JS100, so I was thinking it might be a different MCU. 😄

[Andrew Chong]

Hi, @flit

From this file: https://github.com/ARMmbed/mbed-os-rjio/blob/25be2e52948409727f29d353637beb28c9b2f192/targets/TARGET_Samsung/S111_FW_Write_190103_mbed.zip

There is OpenOCD way to debug as S111_FW_Write_190103_mbed\OpenOCD\openocd\windows_64\fusing_dbg.bat
This enables OpenOCD debugging. Any chance you can reference that OpenOCD example and make it work for PyOCD?

If you need S111 reference manual, any chance you can elaborate which information is needed? As far as I know, Samsung may not be able to provide the reference manual but is able to answer any HW/embedded related questions.

[Chris Reed]

Thanks, I'll look.

We require that the reference manual be publicly available for any device added to pyOCD (or DAPLink), since this is an open source project. Anyone in the community should be able to see where the target support data came from.

As far as information from the RM, I need the detailed block diagram, memory map, and debug architecture details. Often other information is useful, but you don't know until you start testing and debugging.

[Chris Reed]

The OpenOCD scripts help, but I need the reference manual to understand what they are doing and why. For instance, what does the cmu_init routine do? What registers is it writing, and why? I need to be able to distinguish between code in the OpenOCD scripts that is required for basic target connection and control, versus code used for flashing the firmware. The latter would be handled by an external script, not part of pyOCD itself.

[Chris Reed]

Hi @andrewc-arm , I'll also need an SVD file for the S111.

[Andrew Chong]

Hi, @flit

I searched about how to create SVD file.
This is the file type you are looking for?
https://www.keil.com/pack/doc/CMSIS/SVD/html/svd_Format_pg.html

I will discuss with Samsung on creating this file.
Do you have any tips on creating this file?
Do you think SVD is related with CMSIS-Pack?

Thanks,

[Andrew Chong]

Hi, @jh6186
We might need your assistance on getting these files to enable pyOCD + S111.

• S111 reference manual (register map, debugging level)
• SVD file

Thanks,

[Jihoon Park]

Hi,

We already shared S111 reference manual, kimmo or joseph may get this long ago. please double check.
and
what is SVD file?

[Chris Reed]

The link @andrewc-arm provided above documents the SVD file format. It is a standard format in the Cortex-M ecosystem for describing memory mapped registers. All Cortex-M debuggers support this format, and it will shortly become a requirement for pyOCD target support.

[Andrew Chong]

Hi, @jh6186
There are Arm Keil related tools at this location.
https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/Utilities/Win32
I observe that SVDConv.exe is there.

[Chris Reed]

@jh6186 SVD is the standard format for memory mapped register definitions in the Arm ecosystem. Pretty much all debuggers support this format. The docs are here: http://arm-software.github.io/CMSIS_5/SVD/html/index.html.

With #618, all new builtin targets in pyOCD need an SVD file.

[Andrew Chong]

Hi, @flit
Since Samsung provided us way to debug with OpenOCD + DAPLink. There is no urgent need for this enablement. If possible, could you please consider this issue instead?
ARMmbed/Samsung_projects#3
Thanks!