GP2X likes my batteries

-
I have been learning about the GP2X I received the other week. I have an arm gcc tool chain setup on my windows box, and my linux box. It could have been a much easier experience. However hopefully now the gp2x dev wiki has gathered enough information so new commers should have an easier time.

It has a bunch of potential to be a really nice device. It just needs a whole bunch of bug fixes. I think the people at GPH will eventually fix things up.

So I wait until I can afford a power supply for the unit. So that I do not have to recharge batteries all the time. Having to copy the file to the SD card via the card reader, then put it in the GP2X and reboot is no fun at all. Considering boot time is 25 seconds or so. Which means a lot of iterative development will not work if I need to wait 1 minute between changes. I am used to waiting 1 second between changes.

In the meantime someone else has already gotten python, and pygame working on the machine. Which is great! As soon as I get my power supply(about $40 AUD at dick smiths) I'm going to play around with that.

If someone can get tcp/ip over usb working with the machine, then iterative development with python should be a bunch easier. All the software is available for it. It just needs to be compiled into the kernel, and tested. Unforuntately GPH has not released the code for their modifications to linux. So this will have to wait.

I want to add a gp2x module to pygame. With all the extra things that can be done with the GP2X. For example, turning the red led light on and off. Putting the LCD to sleep when a game is paused. Nicely named constants for all of the joystick buttons. Putting the second CPU to sleep. Using the hardware overlays, scaling, and other abilities of the video post processor etc etc.

Comments

Post a Comment

Popular posts from this blog

Draft 3 of, ^Let's write a unit test!^

-
Image
So, I started writing this for people who want to 'contribute' to Community projects, and also Free Libre or Open source projects. Maybe you'd like to get involved, but are unsure of where to begin? Follow along with this tutorial, and peek at the end in the "what is a git for?" section for explanations of what some of the words mean. Draft 1, 2018/07/18 - initial draft. Draft 2, 2019/11/04 - two full unit test examples, assertions, making a pull request, use python 3 unittest substring search, "good first issue" is a thing now. Started "What is a git for? Jargon" section. Draft 3, 2020/12/12 - default branch name is main. What's first? A test is first. A unit test is a piece of code which tests one thing works well in isolation from other parts of software. In this guide, I'm going to explain how to write one using the standard python unittest module, for the pygame game library. You can apply this advice to most python pr
Read more

Is PostgreSQL good enough?

-
Image
tldr; you can do jobs, queues, real time change feeds, time series, object store, document store, full text search with PostgreSQL. How to, pros/cons, rough performance and complexity levels are all discussed. Many sources and relevant documentation is linked to. Your database is first. But can PostgreSQL be second? Web/app projects these days often have many distributed parts. It's not uncommon for groups to use the right tool for the job. The right tools are often something like the choice below. Redis for queuing, and caching. Elastic Search for searching, and log stash. Influxdb or RRD for timeseries. S3 for an object store. PostgreSQL for relational data with constraints, and validation via schemas. Celery for job queues. Kafka for a buffer of queues or stream processing. Exception logging with PostgreSQL (perhaps using Sentry) KDB for low latency analytics on your column oriented data. Mongo/ZODB for storing documents JSON (or mangodb for /dev/null replacemen
Read more

post modern C tooling - draft 6

-
Image
Contemporary C tooling for making higher quality C, faster or more safely. DRAFT 0 - 10/11/18,  DRAFT 1 - 9/16/19, 7:19 PM, I'm still working on this, but it's already useful and I'd like some feedback - so I decided to share it early. DRAFT 2 - 10/1/19, mostly additions to static analysis tools. DRAFT 3 - 10/4/19, updates on build systems, package management, and complexity analysis.  DRAFT 4 - 10/6/19, run time dynamic verification and instrumentation, sanitizers (asan/ubsan/etc), performance tools, static analyzers. DRAFT 5 - C interpreter(s).  DRAFT 6 - 11/6/19 , mention TermDebug vim,  more windows debugging tools, C drawing for intro. In 2001 or so people started using the phrase "Modern C++". So now that it's 2019, I guess we're in the post modern era? Anyway, this isn't a post about C++ code, but some of this information applies there too. No logo, but it's used everywhere. Welcome to the post modern era. S
Read more