Jernej Simončič �

@jernej__s@infosec.exchange
247 Followers
145 Following
20.9K Posts
@nina_kali_nina That was the first printer we had at home, around '91 or '92.
@nina_kali_nina Is that an Epson LX-400?
@eniko The only reason I use a transparent silicone sleeve with my current phone is because it has glass on the back, too, and it kept sliding off the junk on my desk…
Oh no 🔥
Anyone know what this model of monitor is? Amazing industrial design that goes way harder than it has to.
@mcc I sure wish I could.
Poll: Could you care less?
I could care less
I couldn't care less
Poll ends at .
🔴 ❤️ - Budapest Pride March 2025
"It's alarming enough that people with no history of mental health issues are falling into crisis after talking to AI. But when people with existing mental health struggles come into contact with a chatbot, it often seems to respond in precisely the worst way..."
https://futurism.com/commitment-jail-chatgpt-psychosis
People Are Being Involuntarily Committed, Jailed After Spiraling Into "ChatGPT Psychosis"

People experiencing "ChatGPT psychosis" are being involuntarily committed to mental hospitals and jailed following AI mental health crises.

Futurism

I just read through a new, detailed, seemingly statistical rigorous academic study researching why people don't use AI. Its conclusions on this question are not unreasonable, and while I don't agree with all of them, there are salient points.

I am not going to give this study any direct oxygen by linking to it or naming it specifically. Because in my personal view, its entire purpose is nightmarish.

The ultimate focus is obviously on one key aspect, what do the Big Tech Billionaires need to do to suck EVERYONE into using these horrible systems. The entire study -- again, in my opinion -- is an effort to create a roadmap for Big Tech to "adjust" what they're doing to undermine the concerns non-users of the tech have, and seduce them into becoming addicted users instead.

There was no sense that not using generative AI is a valid choice, rather it's seen as an aberration that needs to be eliminated.

I found the entire study to be both interesting and disgusting.

L

×

are you a platform/embedded developer?
do you need to interact with hardware in a semi-custom manner?
would you like to suffer a lot less doing it?

if so, #GlasgowInterfaceExplorer might be for you. the code below is all you need to build a custom testbench for a DUT you've never seen before. just as easily you can add JTAG/SWD debug, protocol analyzers, etc.

oh, and of course, if you use some custom protocol the industry has never seen before, you have an FPGA that can be used to implement it.

e.g. it took me less than a week to build an RGMII Ethernet endpoint that can shuttle packets from a SoC to a TAP interface on the host

Glasgow Interface Explorer

A highly capable and extremely flexible open source multitool for digital electronics

@whitequark i recently got my glasgow btw and am hoping to use it soon for some SPI debugging, also SWD interfacing with rp2040, rp2350 would be interesting, but got no experience with that yet.
@mntmn very nice!! i haven't tested SWD with rp* chips in particular, but i don't expect glasgow-specific bugs (although i know they use multidrop SWD which tickles some issues in upstream probe-rs..._)
@mntmn but also i can most likely just fix any SWD issues if you hit them, i have enough ADIv5.2 knowledge at this point
@whitequark @mntmn RP2040 is multi-drop, RP2350 is single-DP (but ADIv6)
@whitequark @mntmn I flashed both RP2040 and RP2350 successfully using glasgow and probe-rs.
To be honest, for now the only practical advantage compared to the cheap pico probe was that I could power the target from the glasgow. But the possibilities are limitless. For example it should be quite simple to not only flash and debug the target, but also provide a programmable test setup that interfaces to the target over SPI or whatever communication protocol you want to test.
@jannic @mntmn glasgow is also one of the fastest probes you can connect to probe-rs!
@whitequark @mntmn it's indeed impressive! And may allow for much more RTT logging without slowing down the firmware or loss of debug messages. I just didn't have a practical use case yet.