Path: ...!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: antispam@fricas.org (Waldek Hebisch)
Newsgroups: comp.arch.embedded
Subject: Re: 32 bits time_t and Y2038 issue
Date: Fri, 14 Mar 2025 01:48:07 -0000 (UTC)
Organization: To protect and to server
Message-ID: <vr01sl$cpvn$2@paganini.bofh.team>
References: <vqpkf9$1sbsa$1@dont-email.me> <vqpoi3$226ih$1@dont-email.me> <vqre18$2g8c8$1@dont-email.me>
Injection-Date: Fri, 14 Mar 2025 01:48:07 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="419831"; posting-host="WwiNTD3IIceGeoS5hCc4+A.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: tin/2.6.2-20221225 ("Pittyvaich") (Linux/6.1.0-9-amd64 (x86_64))
X-Notice: Filtered by postfilter v. 0.9.3
Bytes: 1884
Lines: 25

pozz <pozzugno@gmail.com> wrote:
> 
> How do you debug your projects without a full-features and ready-to-use 
> IDE from the silicon vendor?

With STM devices I use Linux 'stlink' program and gdb.  That is
command line debugging.  I can set breakpoints, single step,
view and and modify device registers, those are main things
that I need.  I also use debugging UART.  For debugging I
normally load code into RAM which means that I can have
unlimited number of breakpoints without writning to flash
(I am not sure if that is really important, but at least
makes me feel better).

I have also used stlink with some non-STM devices (IIRC LPC),
but that required modification to 'stlink' code and IIUC
use of of non-STM devices is blocked in new firmware for
the debugging dongle.

'gdb' can be used with many other debugging dongles.

Visual tools may be nicer and automatically do some extra
things.  But I got used to gdb.

-- 
                              Waldek Hebisch