HackPOD : A smartphone powered by the Teensy 3.1

Status
Not open for further replies.
K

kundu

Member
Hi,

We made a cool little thing called HackPOD.

HackPOD is based on the Teensy 3.1. The consumer model would be updated to Teensy 3.2 and more aesthetic look of the device.

HackPOD features an integrated 3.2" touchscreen TFT, SD/SDIO card slot, an in-built protoboard and SMT space and a 1800mAH LiPO battery, all within a portable smartphone form factor. It also hosts an antenna port for greater range.

We'll be launching on Indiegogo on June 15. Special Early Bird offers are available through our site.

You can find more information here.
1 - The HackPOD Website https://hackpod.github.io
2 - The HackPOD Blog https://hackpod.gitbooks.io/blog/content/
3 - The HackPOD Indiegogo draft campaign https://goo.gl/xWNaeS
4 - The HackPOD facebook page https://fb.me/gethackpod/

HackPOD caters to the needs of hobbyists, students and engineers by presenting them with great power but also ease.

(•̀ᴗ•́)
 
What's the display controller and resolution?
Does it fold open to solder to the breadboard underside?
There must have been a reason for fullsize SD socket. Though Micro SD would have been much more space efficient and discrete.
Really cool would have been a way to make an edge connect proto area that locked in place.
 
What's the display controller and resolution?
Click to expand...
The Display resolution is 320x240 and the controller is SSD1289. But for the consumer model we are planning to get the 480x320 res. screen and ILI9488 controller

Does it fold open to solder to the breadboard underside?
Click to expand...
Yes I does.

There must have been a reason for fullsize SD socket. Though Micro SD would have been much more space efficient and discrete.
Click to expand...

Yes. There is a reason. We wanted SDIO cards to be compatible too. That is the only reason for opting a full SD card slot. A notable SDIO card that we found fascinating is the Electric IMP.

Thanks.
 
Electric Imp doens't use the SD pinout, just the form factor. It's not SDIO compatible.
Click to expand...

It does for the most part. It requires an extra Atsha204 Chip. We modified our SD slot connections in such a way that it is compatible with SD/SDIO including Electric IMP.
Check the schematics from our website for details.
 
Indeed? It looked like a generic platform - but seems to be somewhat designed for some special use cases. It might border on cool for those but be limited in connectivity as a general Hackable base?
Click to expand...
what will it do?
Click to expand...

It will do everything your Teensy does. Plus it will make it compact and portable. It eliminates the need of a computer monitor to log your data. It can even be connected to Raspberry Pi Zero and make it even powerful if your project needs a high dose of processing and number crunching. Simply plug in a wifi module or electric IMP and you can program wirelessly too. The TouchScreen is a great HID.

One can even make it an ultracheap signal generator .. by moving sliders on the touchscreen and taking the o/p from the DAC pin.

If you want a radio project an antenna conn. is also provided for grater range.

Couple a low power device with a 1800mAh battery and you have enough juice to power it a long long time.

One can make a custom circuit on the protospace and you have a "customPOD".

In fact, I can go on and on.

The SSD1289 display has code in TeensyDuino - seems to be a parallel (8 or 16 bit?) driven display? Library search on ILI9488 came up empty - so switching to that controller would be new work?
Click to expand...

We donot use that library. We use our own HackPOD library which is modified form of UTFT library from HenningKarlsen.
 
You may want to revise the claims re 16 bit ADC performance unless you've added your own ADCs. Paul has been very clear re expectations and so has Freescale.

Paul doesn't expect better than 13 ENOB, IIRC. And that requires differential inputs. 12 bits ENOB on single channels.

Neither does Freescale, with the exception of the 16 bits they claim for one pair of differential inputs that likely require monumental efforts on the front end to present a perfect signal to the ADC, a sleeping CPU, an amazingly stable power supply, etc. In other words, unless you are using 'real' external ADC's I would shy away from claiming 16 bit performance based on the CPU.

It likely would be cheaper to get to 16 bit performance with an external ADC than the one on the MCU. On the other hand, I'd be stumped re how to make an external ADC easily accessible.
 
Last edited:
Status
Not open for further replies.
Back
Top