7 ms·
Oxide on My Wrist: Hubris on PineTime was the best worst idea
- gnicholas 5y agoCan anyone provide a comparison of PineTime and Pebble? My Time Steel is aging and I'm trying to figure out if the PineTime would be a workable replacement.
- wanderer_ 5y agoThe pinetime can basically do anything you want it to, as long as you're willing to make it so. I'm wearing it on my wrist right now, but I have an iPhone and the support for it is not great. In terms of build quality, it's quite good, and the battery lasts for about a week. It's slimmer than an apple watch, which is a major plus for me. But if you have an iphone, step tracking and limited music control is all you'll get in terms of accessory use. You can always contribute, however, and there is a very active community working on the firmware in the github repo (https://github.com/InfiniTimeOrg/InfiniTime https://github.com/InfiniTimeOrg/InfiniTime). The thing that the PineTime does really well, however, is beat the price tag of basically every other smartwatch out there ($30). I'm not sure how chip-shortage prices might be affecting this though...
- gnicholas 5y agoThanks, I am on iOS so this is helpful. All I really care about is notifications, step tracking, and music control. It would also be nice to look at my calendar and check the weather, but those are not critical.
- wanderer_ 5y agoDevs are currently working on notifications, and you can help too if you are so inclined, but they aren't there yet. I am still on the BLE / GATT / ANCS learning curve, so I have not been much help.
- qualudeheart 5y agoThanks for posting. My girlfriend is an embedded Rust developer. She’ll enjoy reading this.
- zozbot234 5y agoSee Tock OS https://www.tockos.org/ https://www.tockos.org/ for another Rust-based embedded OS with a fairly comparable design to Hubris. The debugging capabilities of Humility make an interesting comparison to what's provided by cargo-embed https://probe.rs/docs/tools/cargo-embed/ https://probe.rs/docs/tools/cargo-embed/ and the Knurling Tools https://knurling.ferrous-systems.com/tools/ https://knurling.ferrous-systems.com/tools/ by Ferrous Systems. Ultimately, the embedded space (including all sorts of low-level, retro, "bare-metal", remote etc. programming) has common needs and it would be convenient to see more widespread cooperation among these projects, improving reliability and avoiding wasteful duplication of work. More resources at https://github.com/rust-embedded/awesome-embedded-rust https://github.com/rust-embedded/awesome-embedded-rust
- panick21_ 5y agoPeople often have good reason to not adopt existing systems. Oxide started with TockOS and have written and talked about why they didn't end up using it. This twitter space goes into a lot of detail: https://www.youtube.com/watch?v=cypmufnPfLw https://www.youtube.com/watch?v=cypmufnPfLw But at the end of the day, no_std will allow a bigger ecosystem and sharing between many of these projects.
- zozbot234 5y agoThing is, it's not even clear that their added elements are all that sensible. If you're always running trusted tasks on your embedded hardware, what do you need the MPU for? Even in principle, it can only save you a bounds check. And if you start running outside code, then the clear privilege separation in Tock between trusted "Capsules" and other "Tasks" starts looking plenty attractive. Even OP notes that this MPU business introduces severe overhead.
- bluGill 5y agoThe real question is what is the correct risk tolerance, there are many degrees in here with trade offs. If I mostly trust the other programmers then I'm just concerned about mistakes. If I'm running code that might have been written by some evil cracker trying to do some evil then I need more protection.
- smbv 5y agohttps://archive.ph/E8rQv https://archive.ph/E8rQv
- f0e4c2f7 5y agoI love projects like this. I've considered getting a smartwatch. Something like this makes the idea more appealing. Whats the most hackable watch? Is there a pinephone of smartwatches?
- nsb1 5y agoThere is! And it's even featured in this article!
- bitdivision 5y agoThe article is about running Hubris on the PineTime. Quite literally the Pinephone of watches. https://www.pine64.org/pinetime/ https://www.pine64.org/pinetime/
- ushakov 5y agoPineTime with wasp-os!
- nickspacek 5y agoIt's not the most hackable, but there are some dedicated folks hacking at the Amazfit watches. I have the original Bip, which has a ridiculous battery life (30+ days easily) and GPS. The GPS will run your battery down with extensive use, but if I'm running a few times a week it'll still go 2 weeks. It isn't that powerful, and I wish it had a second physical button. I haven't explored the mods very much because it does what I need it to do, but the scene has the feel of the early Xbox hacking scene, to me at least. There's this watch which appears to be heavily inspired from the Amazfit Bip: https://www.kickstarter.com/projects/gfw/banglejs-2-the-open-smart-watch https://www.kickstarter.com/projects/gfw/banglejs-2-the-open...
- protoman3000 5y agoThe github repo of hubris [0] is very nice, as they immediately tell you where what is, e.g. drv/ contains drivers, a mix of simple driver lib crates and fully-fledged server bin crates. Current convention is that drv/SYSTEM-DEVICE is the driver for DEVICE on SYSTEM (where SYSTEM is usually an SoC name), whereas drv/SYSTEM-DEVICE-server is the server bin crate. Why does nobody do this in their readmes normally? They just let you look into their code and tell you "now figure it all out yourself". [0] https://github.com/faithanalog/hubris/tree/pinetime https://github.com/faithanalog/hubris/tree/pinetime
- Jerrrry 5y ago
- JadeNB 5y ago> Why does nobody do this in their readmes normally? They just let you look into their code and tell you "now figure it all out yourself". I think it's worth praising this repo without knocking others. Open source authors have no obligation to their users; if they don't have the time to, or just don't care to, so organise their READMEs, then they need not. In fact, if it's sufficiently important, for much open-source software anyone else can do it, and submit a patch.
- nerdponx 5y agoThis isn't just about open source. Developers on internal projects should do this too, but don't.
- bluGill 5y agoHave you ever tried to write useful documentation? As a programmer you are far to close to the code. You assume things are obvious that are not, while going into great detail describing things that are obvious (or maybe not obvious, but only rarely interesting and so should be documented in a deeper link not the main documentation). Or worse because you have to document it you document the code lines (++i; // increment i by one). This is a hard problem. I try to make an effort, but too often I get it wrong.
- visy 5y agoThanks for the shoutout on the twister :)
- wlkjlkeleg 5y ago
- dcow 5y agoThank you for the LoFi tunes. I dig that stuff!
- a9h74j 5y ago> Compare these two videos of writing a solid block of color to the screen, first through the SPI task, and second with direct SPI hardware access: I wonder if the performance difference could, in some applications, create a preference for processors with enough SPI ports to dedicate one per peripheral (no chip select required). Not only no shared bus (as in I2C), but no shared SPI-task.
- AceJohnny2 5y agoLarger chips (like SoC/Application Processors) certainly have multiple such buses for bandwidth & separation-of-concerns (ie security-related stuff like bootrom vs touchscreen controller) reasons, but I think we're far, far away from accepting the cost of extra pins just to accomodate software concerns.
- mkesper 5y agoCool, almost the same chip is used in the microbit v2. https://support.microbit.org/support/solutions/articles/19000119052-details-of-micro-bit-v2#comparison https://support.microbit.org/support/solutions/articles/1900...
- ComputerGuru 5y agoCan anyone clue me in on the status of async/await in hubris? I have some HAL code that both really needs and uses async (or callbacks) to work and currently just use my own homebrew WFE/WFI wakers (with a fixed, known a priori number of tasks) but it would be nice to switch to something more elegant and less brittle. (Context: async/await-based per-task loop to facilitate background LoRa send/receive while other tasks can continue to operate (DMA, SPI, etc) independently, with the overall loop shutting the primary Cortex core down when processing is completed/while waiting for events/updates.) The last I checked, hubris was strictly synchronous and I didn't get the sense that the interaction between tasks was architectured in such a way that would facilitate low-power designs for battery-powered devices.
- steveklabnik 5y agoWe don't use async in hubris, so there is no async/await. Hubris is 99.99999% synchronous. For more: https://hubris.oxide.computer/reference/#_why_synchronous https://hubris.oxide.computer/reference/#_why_synchronous (Basically, this probably hasn't changed since you looked at it, but for anyone else who hasn't seen it yet...) > shutting the primary Cortex core down We don't have mainline support for multicore systems, and there's a big ? in there, design-wise. So yes, you are right to recognize that that is the current state of things.
- ComputerGuru 5y agoHi Steve. Thanks for the confirmation - obviously a synchronous design doesn't automatically/necessarily preclude most high-level use cases that async can support - it just requires an alternative approach and some careful consideration. In fact, it could make it easier to do many things like power management. Can you comment on this: others have asked here on HN before but didn't seem to get an answer - does power management/consumption factor in at all in the architectural design (even if it's "this makes it possible to add power management later") or is it strictly a non-goal? (I know your current particular application domains aren't constrained by battery capacity.) It would be easy enough to hack the kernel to always WFI/WFE if all tasks are exited/completed, but I'm thinking about cases where task(s) are still running but the supervisor process is aware that they're all currently in a busy-waiting state. But that wouldn't be sufficient (on its own) if the OS requires certain peripherals to always remain powered up, uses a high-frequency tick interrupt that will constantly wake the device anyway, etc, etc.
- RantyDave 5y agoZephyr can do MPU https://docs.zephyrproject.org/latest/reference/usermode/memory_domain.html https://docs.zephyrproject.org/latest/reference/usermode/mem...