Add a dirt-cheap screen to the Raspberry Pi B+
blog.reasonablycorrect.com
blog.reasonablycorrect.com
Far too often I find myself saying "it shouldn't be this hard". Surely there exists a market for an adapter to plug an easily available iPhone screen into an RPi?
https://www.indiegogo.com/projects/pi-top-a-raspberry-pi-lap...
.. but then, this is also pretty usable for the same purpose:
The ideal situation would be where the RPi foundation uses its existing clout to get a PiCalc accepted as a standard calculator in school.
For instance, a TI-89 is allowed on the SATs, but a TI-92 is not. Basically the same calculator, except the TI-92 has a qwerty keyboard. How would a tiny little qwerty keyboard actually give you an advantage on a test like the SAT? Who the hell knows. Remember 10 or so years ago when teenagers were all typing on telephone keypads?
On the other hand, the advantage of a TI-89 (with a CAS) over a TI-83+ (without one) is fairly extreme.
(Also, anyone who bothers to google it can trivially get around the reset key combos for at least 83+ line: http://brandonw.net/calculators/fake/ Somebody who takes the time to program their calculator for cheating on a test can do this)
With the 89's input history, you could effectively record the mathematics section merely by running it all through your calculator and then extracting the history after the fact.
1) fear of cheating
2) because the teachers want you to do the calculation
When I took my Calc and my engineering courses, my teachers would not allow calculators. They would make sure the numbers are nice, not some crazy number or pi to calculate with. Volts, current, all those numbers are so nice we can do on the paper. I like that because it means the teacher actually put effort to ensure the numbers are not just random, they mean something to the teacher who created the exam (even though they might just change the number next semester).
I will say fun and small size notwithstanding the current cost of doing this ($50) is a little high relative to just buying a super-low end LCD monitor ($85 for an 18" by Samsung, Asus, and Acer, $54 for a refurb from NewEgg). But I'm sure that misses most of the point...
Just seems like the $30 for the 5" LCD is a little steep but maybe you're paying a premium because it is so small(?).
Keep in mind this is prototype cost, typically inflated seriously because it's a one off.
I see you can get a generic Pi LCD for $7.65, a 5" LCD with video in for $18.75, and a touchscreen Pi size kit for $19.90[1].
Going to the effort of breaking out DPI through the GPIO was quite creative. If optimized do you think these can hit sub $5? Either way, this was very clever. Thank you for taking the time to document this for others!
[1] http://www.aliexpress.com/wholesale?catId=0&initiative_id=SB...
LVDS is just serialized parallel video. Serializer chips are ~$5 in singles on Mouser. Combining Pee DPI output with SN75LVDS84 ($2.5 if you order 10 from china) will allow you to connect any modern <=1366x768 resolution (single lvds channel limit) Laptop LCD screen. Those can be free if you have a broken laptop. You could even drive older "HDReady" 32' TV LCD with pee this way.
[1] See for instance http://linux-sunxi.org/Cubieboard/LVDS - I believe it supports DPI as well as LVDS. script.fex is basically Allwinner's equivalent of the device tree.
I get the feeling DSI will never happen, or it will be as crippled as CSI - locked down with blob to working with one official product only.
Time to go panel hunting for some more panels :-)
second part of my earlier post:
https://news.ycombinator.com/item?id=9155677&goto=item%3Fid%...
Basically take the tablet manufacturing process and remove most of the stuff thats not a screen and add HDMI.
Meanwhile the competition even has eMMC in the same price range.
However, it seems that crashes are inevitable if you do hobbyist stuff with your RPis. Plug in funny things into your GPIO or USBs and run your own buggy code and you can't always shut it down properly.
False. This depends on the software.
We developed a system for the PrintToPeer Raspberry Pi OS that uses the RAMdisk for read/write operations, and makes the rest of the operating system read only.
You can uplug it whenever and nothing is corrupted.
We don't power off our many pis, but they are on UPSs (we use them for a security system.) However, the corruption happens so much that we keep disk images and have a spare on hand when we have to reboot them for any reason because 1/4 of the time they will not boot up.
Even if it were corrupting the FILES being written when hard booted, it shouldn't corrupt the FILESYSTEM being written.
TLDR, nuh uh.
That's not how SD cards work unfortunately. When an SD card erases data, like if it's updating a file allocation table, it has to erase an entire block of flash and not just the bytes you care about. The card will throw the block into a cache in memory, erase the block, and then rewrite the parts of the block that weren't erased. However if you pull out power during that operation you'll completely kill the block and destroy the filesystem.
There's a great video here from Linuxconf Auckland about using SD cards for embedded systems and these issues: https://www.youtube.com/watch?v=K3zb6p0thQU
If you could use a flash filesystem at the OS level & talk directly to the SDcard flash blocks then you might be able to pull the plug & not risk corrupting an SDcard, but as things currently stand I don’t think that’s possible.