Permissions for Including Memory Screenshots in an Academic Thesis (STM32N6570-DK)

[Tom87]

Dear STMicroelectronics Support Team,

I hope this email finds you well.

My name is Alan, and I am a master's student in the graduate school of an University in Taiwan. Currently, I am conducting research and development for an academic project utilizing the STM32N6570-DK discovery kit.

During the development process, I implemented a feature that saves user configuration settings into the external NOR Flash memory. To validate the success of this storage mechanism in my academic thesis, I intend to provide a visual verification. As shown in the attached screenshot, the memory content displays the specific CAN packet format data that I defined.

Regarding the software license agreement (such as SLA0044) and ST's intellectual property policies, I would like to kindly inquire about the following:

1. Is it permissible under the current ST license to include this specific STM32CubeProgrammer screenshot in a publicly accessible academic thesis in Taiwan?
2. If direct screenshots are restricted or discouraged, are there any recommended alternative methods, anonymization guidelines, or blurring requirements I should apply to the user interface (e.g., hiding the device UID, external loader model, or specific memory addresses) before publication?

Ensuring full legal and compliance clearance is highly important for both my university and my research team. I would deeply appreciate your professional guidance on this matter.

Thank you very much for your time, assistance, and continued support for academic research.

(NOTE : Since I am currently uncertain about the exact terms and restrictions of the software license, this screenshot has been temporarily censored/anonymized to protect potentially sensitive project information.)

Best Regard, Alan.

[Pavel A. · Accepted solution]

@Tom87 Why can't you edit the screenshots and keep only the data dump area, removing all other CubeProgrammer GUI elements?

[Tom87]

Dear @Pavel A. ,

Thank you so much for your practical advice and prompt response. I sincerely appreciate your guidance. I will proceed by cropping the screenshot to keep only the pure data dump area and completely removing all CubeProgrammer GUI elements for my academic thesis. This solves my dilemma perfectly!

Taking this opportunity, I would like to kindly ask for further clarification regarding another part of my thesis.

My research heavily involves the advanced vision peripherals of the STM32N6 series, specifically the DCMIPP and ISP blocks. To properly explain the system implementation in my thesis, I need to include some official hardware block diagrams and operational schematics (e.g., the functional block diagrams or pipeline processing workflows found in the ST Reference Manuals or Datasheets).

Regarding these official hardware schematics, could you please advise on the standard guidelines?

1. Is it permissible to directly include these official block diagrams (such as DCMIPP/ISP workflows) in a public academic thesis, provided that proper source citation and copyright attestation to STMicroelectronics are included?
2. Or would ST strongly recommend that students manually redraw/recreate these block diagrams instead of using direct clippings from the official documentation?

Thank you again for your invaluable support to the community!

Best regards ,Alan

[Andrew Neil]

---

@Tom87 wrote:

Regarding these official hardware schematics, could you please advise on the standard guidelines?

---

That's a new question - so please start a new thread for that.

Please post a link here to your new thread - so people can find it.

You can include a link in your new thread back to here for context, if you like.

Did you see this thread: Can I use STM32 datasheet screenshots in a commercial course?

[Tom87]

Dear @Andrew Neil :
I have carefully reviewed the thread link you suggested, and it has been incredibly helpful. Thank you so much.
As for the forum's posting rules, I will pay closer attention to them in the future to keep the threads concise and benefit more users.

Thank you again for your invaluable support to the community!

Best regards ,Alan