Remember Remember to Blog in September

Sorry I've been away so long, but I've been very very busy, in the office I've had a paradigm shift in my projects, away from coaxing old C# systems and writing little C++ items to developing for Android.

I've therefore had to set up, and document, a whole manner of working with a new set of devices on an OS most of the folks in my office don't want to acknowledge, no not Android... Linux... They line Android... But detest and hate seeing Linux.

Yes, yes I know Android is Linux, and I know you know... But you tell some of the folks in my office, and the ones who don't have an opinion generally have an iPhone stuck to their ear.

So, developing for Android... I must have been doing Java eh?... Nope... Remember I said I was into Python, well I've been developing Python for Android, I've learned the languages, got to grips with Kivy and used buildozer to create my APK's for distribution to the devices.

I've dabbled with PyJNIus as well as other Android API libraries.

I will be bringing some tutorials to these pages about all this, once I've gotten the project itself completed.

My current challenge is animation of the active pages within the Application with Kivy.

Working with Taiwan Twinglish Embedded Development Kits

You know sometimes, I wish people would just write a manual.  I've just come across a chap who wants to sell a development kit to the company I work for, he's in Taiwan and very excited, he knows all about his kit, and he's been on the phone bulling it up for the boss.

He has ticked all the boxes with the boss, and they've gone a head and ordered the extortionately priced item, and it's arrived on my desk.

I took one look, and asked "Where's the manual", there isn't one.  Because this is a development kit... Right, what power does it take.. No-one knows, the only way to tell has been to look at the chips and see what the lowest possible power feed should be to the lowest value chip.

Which prong was the negative?... Only could tell that by tracing - by eye - back from an obvious earth plane and a couple of large caps and checking that the line was the negative rail.

This level of just basic documentation, being lacking, immediately makes me worry about the whole bundle.

They're trying to sell this, but I think they're actually trying to get a native English speaker - i.e. me - to write their manual for them.

Next thing, how do I build software to run on this kit?... They don't know... Seriously, this is what the chap has said to me, "It in C, write in C"... okay, what compiler you got?... "We no got compiler"...

So I have to go to the chip vendor and ask for their compiler?... These people throwing this kit together don't have a compiler?  And don't have any recommendation of which compiler to use?....

Luckily I can look at the board and see the processor, so I know what architecture I'm going to target, but I was about to ask "What's the architecture", and I'm pretty sure he'd not know.

How to get the software as built onto the kit, also seems a mystery, there's no obvious portable slot, no ethernet, no USB, no serial... I can't believe I have to burn EEPROM's and plug them in... In this day and age, I've been told "Firmware take your software in, firmware do it"... but not been told how.

I swear, I could pull the last shreds of my hair out with this, not least because I have to appraise this for use by our whole UK arm before this guy jumps on a pre-booked plane ticket from Taiwan over to here.... Gah