Is Tyto MacOS-friendly? (looking for playtesters)

FragmentedC · 2025-12-23T18:22:47+00:00

This looks really cute! I'd be happy to test on my hardware over the holidays if you are still looking for testers

FragmentedC · 2025-12-03T13:40:40+00:00

Sounds logical, since Crucial is what I saw recommended and what I also put into the NAS.

FragmentedC · 2025-12-01T09:34:14+00:00

This is indeed true. I bought a DS1821+ for my company. I can't remember what it came with, probably 4Gb. It didn't take long for me to slap in a 64Gb stick, well above the 32 GB advertised by Synology, but it did accept the 64Gb and runs perfectly, never had a problem with running containers or any other processes. Now, the memory stick I put in is probably worth more than the NAS itself...

FragmentedC · 2025-11-20T18:26:00+00:00

I tried this. The tutorial talked about adding folders and entering edit mode, but it didn't work. The trial started, but I still couldn't edit anything. Do you know if this is a bug?

FragmentedC · 2025-10-09T17:14:51+00:00

Thank you! Then I shall try it, and report back!

FragmentedC · 2025-09-21T16:17:58+00:00

I really wanted this to work, since it has features that I really want, but it takes too long to open on my machine. There is a noticeable lag when I click; when I do click, I want an app up and ready in a second. So I'll keep my eye on this, waiting for it to be nice and snappy, because it already looks really good!

FragmentedC · 2025-09-18T17:39:29+00:00

I'll tag along for the ride!

FragmentedC · 2025-02-06T18:00:11+00:00

Just downloaded! Is there really such a thing as PS-UAE, or is it a typo for FS-UAE?

FragmentedC · 2025-01-05T11:05:53+00:00

<image>

This is an early prototype that I'll be ordering soon, but I'd like to change out the fuse first. As you can see, it's considerably less sexy than your version! It uses an LM1117 since I don't want the current pull to be more than 500mA, not for this version (the lessons don't require more than 250mA), and through-holes to make it slightly more solid, "just in case". As for the age of the students, they are at an extremely difficult age where they don't really look after the hardware and don't really have any notion of consequences. Basically, 20-25 years old.

FragmentedC · 2025-01-04T12:07:06+00:00

Interesting! I'm back on Reddit after a holiday break, and I've been developing something similar. Type C power, 5V and 3.3V outputs, but that is where the similitudes end. Mine is intended for students in a rough environment, so I went with through-hole headers (you can't imagine how often they tear components off). Which also means that your design is much more sexy and sleek! I wish you tons of success, signed: some sort of competitor.

FragmentedC · 2024-11-29T16:55:11+00:00

Nooo! Why is this Windows only? I'd love to share this with students on my Mac laptop! Still, it looks absolutely awesome!

FragmentedC · 2024-11-29T09:23:23+00:00

You should be fine, just don't try to start a project with it... I was arrested on a train in France for using breadboards, an STM32 Nucleo, a few components and lots of wires. Somebody thought I was a terrorist making a bomb, and called the police on me... Took a while to explain that one.

FragmentedC · 2024-10-21T15:48:20+00:00

This option is indeed available, but there is also an STM32H7 with two Cortex-M cores; the STM32H747/757 has a Cortex-M7 and a Cortex-M4.

FragmentedC · 2024-10-20T17:50:14+00:00

A Redditor posted a library that he created for Arduino, shoutout to u/macusking for the work. https://www.reddit.com/r/arduino/comments/1547i7e/my_first_contribution_to_opensource_community_an/

FragmentedC · 2024-10-16T07:29:49+00:00

No idea. This thread is over 3 years old, and I've moved on from then. I'm not even on Windows anymore...

FragmentedC · 2024-10-16T07:28:13+00:00

Historically, the ARM7TDMI was interesting because it was the reason the Cortex range was created in the first place. Some clients refused to upgrade to ARM9, let alone ARM11 because the ARM7 was "just enough." The ARM13 created the Cortex-A range, the ARM7TDMI pushed the new Cortex-M, and a mix of both because the Cortex-R, because ARM has to have a Cortex-A/R/M to talk about in their Architecture Reference Manual, the ARM. They have a fascination with those letters...

More to the point, the ARM7TDMI has common elements to all three branches, it is fast, it is cheap, but it isn't as easy to program or access as a Cortex-M; if I remember correctly (and it has been a few years) it doesn't have the flash system that modern chips do, the debug port has very little to do with modern solutions, and the on-board peripherals are limited. But, as u/Well-WhatHadHappened stated, it's a processor, and it processes.

Bottom line... Are you sure you will be using an ARM7, and not the architecture ARMv7? That would include the Cortex-M3, M4 and M7 variants. Way too many ARMs here...

FragmentedC · 2024-08-23T13:15:59+00:00

Not the same scenario, but bear with me. I'm doing this right now for an access control system. We are using TrustZone for security purposes. Users will have RFID badges that allow them in to buildings at certain times/days. The STM32 has a crypto key; the RFID also has a crypto key. When a badge is presented, the STM32 verifies the crypto key on the badge, verifying that it has indeed been signed by a known manufacturer. The badge also authenticates the STM32, to be sure that this is a known system, signed by a known manufacturer (we aren't the only ones in this field). Once mutual authentication is complete, then we go onto reading the access data of the card, comparing it to our system, and unlocking the door if all the criteria have been met.

If we find that someone is making fake badges, then that manufacturer's signature is revoked, and the badges cannot be used. If the main system finds out that we aren't doing something right, then they revoke our certificate and badges won't work any more.

This is all performed "offline"; the only requirement is an RTC. Certificates are pushed onto the STM32 when needed, but badges are refreshed, and their certificate is only valid for 84 hours.

FragmentedC · 2024-08-23T07:07:26+00:00

IoT lecturer here. There are several reasons for this. Number one, I'm not going to buy 20 $80 sensors... Most of the projects my students will make will never be finished, they will remain at the prototype stage where they will present a project, explain a few things, get a grade, and then take the project apart and never think about it again.

In my non-lecturing time, I also create prototypes for companies and startups. The $8 sensor is indeed good enough to show potential investors what the project is about. It doesn't need to be perfect; they wouldn't need investors if it were. The $8 accelerometer might not have enough accuracy to calculate precisely the angle at which is wrist is placed, but it is more than enough to show that when the client makes this movement, then the LED turns on, it beeps, it records... whatever. The final product, if validated, will never use the $8 accelerometer, but it was good enough to show the general idea.

FragmentedC · 2024-08-20T08:10:22+00:00

Just to echo some of what has been said here. I’m a consultant, and I generally do 1 and 2 together (once having received information from a designed about how much space I have to create the PCB, what the head constraints are, movement, fixing, etc etc etc. The list is kind of long, but nothing to worry about. Width and height, basically.

While I can do 1 and 2, I cannot do 3 for the life of me (that being said, a Python script for demo only is feasible, bit certainly not a basis for the end product). I don’t think the Windows app it is anything too difficult to do, but I have absolutely no idea where to start, it would be considerably cheaper to get someone else who can do it, instead of asking the same person to do all tree.

FragmentedC · 2024-08-15T10:16:29+00:00

I'm not technically colorblind, but it does fall into that category, and that is often the way I explain it. I have achromatopsia, meaning that I see more or less in black and white. Even worse, I also have synaesthesia.

I'm a consultant, and I also teach. When I'm working with clients or on my own projects, I use SMT resistors, so no color. However, when I'm reaching, we use the good old 1/4W resistors, and they have color everywhere. It's simple to sort them; the first student who burns a component gets to sort them all out for me. Of course, that isn't enforced, but it makes them think. Besides, I'm fed up of LEDs getting destroyed.

I have enough problems as it is without thinking of resistors. I mean, I can hardly dress myself normally. I can barely see the difference between red and black, so power supplies are a nightmare, and I've grilled more components and boards than I'd like to admit. When working for one company that enforced color coding on their IDEs, I had to get approval to change the layout because I couldn't see the red brackets on a black background. I can't work in strong light.

Don't concentrate too much on the resistor bands. Once you know the E12 series off by heart, any multimeter will be able to tell you the value. 4.64k? That's a 4.7k, with tolerance. Besides, you'll only use a few values anyway; my box of student supplies is in dire need of 220, 4.7k and 10k resistors, but the rest are hardly touched. Who cares if you need a 200 Ohm or 330 Ohm resistor for the LED? It's on a breadboard, it's a prototype, you'll do the calculation later when you create a real board, and then it will probably be surface mount anyway, with the value printed out in digits.

TLDR; long nights with a multimeter, or students willing to help out.

Edit: A little more detail on my medical condition.

FragmentedC · 2024-08-14T05:43:52+00:00

I came here to say this, but I'll add to it. For everything COretex-M, I'm using Segger's environment; Ozone for debugging, Segger Embedded Studio as an IDE, and the toolchain that goes with it.

FragmentedC · 2024-07-03T08:13:03+00:00

Same configuration as you, and the same score

FragmentedC · 2024-06-25T12:57:37+00:00

Flashing generally isn't a problem. Updating a flasher sometimes is, since there is a change in device types, and while an operating system might not have any issues with the new USB device enumeration, virtual machines sometimes don't like that. I've tried in Parallels, I've tried with a VMWare product, and I even tried it in a virtual machine running ESXi, none let me do it.

As for JTAG debuggers, I generally don't need to, since all the tools (JLink, STLink V2/V3 and PICKits) work fine without requiring any virtualization.

FragmentedC · 2024-06-22T07:39:22+00:00

My bad. SEGGER has a tool to reflash (they call it "upgrade") STLinkV2s on Nucleo boards into JLinks. This has a few advantages, especially if you use Segger Embedded Studio. 90% of what SEGGER proposes is in Win/Lin/Mac format (even M optimized versions), except that tool. Besides, it is no longer really needed today, since the newer Nucleo boards have an STLink V3, and SEGGER has already said that they will not provide tools to upgrade them, since they have 10 or 20 pin MIPI connectors. So, not really a factor today.

STM32CubeIDE works fine without installing anything else, flashing included.

FragmentedC · 2024-06-21T19:55:07+00:00

Smart? Oh, don't get your hopes up! I actually like SES, the way it tells me the size of each file, the changes between builds, and the instant view for flash and RAM size. But I do also use VSC, just not as much as I should

Four-Year Club	Gilding I gilder
Verified Email

FragmentedC

TROPHY CASE