|
Mr Dog posted:It's a pity that putting together an ARM toolchain is much much more painful than it strictly needs to be or I'd just advise hobbyists to put one together. is codesourcery still a thing? the last time i did anything serious with arm you couldn't use mainline gcc, you had to download a specific two releases old version of codesourcery, or your program would crash
|
#
¿
Dec 2, 2014 02:54
|
|
|
|
| # ¿ Apr 29, 2024 14:53 |
|
|
Sagebrush posted:poll: is it pronounced "A T Tiny" or "at tiny"? "A T Mega" or "at mega"? at-mega, as in atmel
|
|
#
¿
Dec 8, 2014 02:47
|
|
|
eschaton posted:so the Intel Edison stuff, with the Arduino board has an Arduino-compatible IDE. how should I go about figuring out what all of the Arduino stuff actually maps to in terms of memory-mapped I/O (or whatever) so I can wire it up to Lisp instead? here's a cool paper about writing code for a space probe back in 1999: Like all spacecraft, DS1 placed constraints on compu- tational and telecommunication bandwidth (both uplink and downlink) resources. For computational resource, DS1 has a total of 128 MB RAM, 16 MB EEPROM, and a 20 MHz RAD6k. During the RAX experiment time, the uplink and downlink data rates were about 1 kbps and 4 kbps, respectively. Based on early estimates, RAX was allocated 32 MB of RAM, 16 MB of file space and up to 45% of the CPU. At the time of this alloca- tion it was not clear if RAX could meet these resource constraints. To fit within the 32 MB memory allocation and the CPU fraction constraints, the RAX team thoroughly analyzed their code for memory and performance inefficiencies and employed a "tree-shaking/transduction" process to the Lisp image. The analysis is, of course, common for any high performance software. However, transduction is Lisp- specific and arises from the tight coupling of the Lisp runtime and development environments. Transduction removes the unneeded parts of the development environment, e.g., the compiler, debugger, windowing system. The result is a significantly smaller image, both in terms of file system and runtime memory. During RAX testing, peak memory usage was measured at about 29 MB, which was more than was actually observed in flight. To reduce the uplink time and the spacecraft file sys- tem usage, we employed a custom Lisp image that sup- ported ground-based compression and spacecraft-based decompression. Upon completion of the transduction process the RAX Lisp image was compressed by a factor of about 3 to 4.7 MB and uplinked to the spacecraft. On-board decompression was initiated at the start of each RAX run, with the file being inflated directly into the 32 MB RAX memory space. Use of this custom compression drastically reduced the file uplink time and kept the RAX file space usage within the agreed upon limits. http://www-aig.jpl.nasa.gov/public/planning/papers/rax-results-isairas99.ps
|
|
#
¿
Feb 1, 2015 09:43
|
|
|
you could use all 8 and show positive values like this g g g . . . . . and negative values like this . . . . . . r r (it's color-blind-friendly!) and use pwm to scale the intensity of the outermost light for fractions, or even just blink it logarithmic may be good anyway e: blinking is annoying because it attracts attention but it would look cool if the value is moving quickly because it's like blink blink blink blink blinkblinkblinkblink *solid*, next light starts blinking suffix fucked around with this message at 20:46 on Mar 7, 2015 |
|
#
¿
Mar 7, 2015 20:39
|
|
|
protocol buffers require a schema, but will be smaller if you want to use message pack but need to optimize for size you'll end up giving fields one-letter names
|
|
#
¿
Sep 24, 2015 20:51
|
|
|
JawnV6 posted:m4 here's the wire format for protocol buffers, fwiw https://developers.google.com/protocol-buffers/docs/encoding it wouldn't be that hard to mash together valid messages ad-hoc if you're just sending if you're receiving it's sketchier but i'm pretty sure there exists c bindings, even if they're not official
|
|
#
¿
Sep 26, 2015 00:31
|
|
|
|
| # ¿ Apr 29, 2024 14:53 |
|
|
gonadic io posted:Also it runs arm so it's fairly easy to get rust to compile on! i tested compiling and running rust on the m0-based microbit based on https://github.com/SimonSapin/rust-on-bbc-microbit, but then i realized i didn't have time to reimplement everything i needed from scratch so i just used python
|
|
#
¿
Jan 4, 2017 15:14
|
|