Recent Posts

Pages: [1] 2 3 ... 10
Technology / Re: Multi-Touch Screens (Opensource)
« Last post by Destroyer on August 18, 2012, 11:07:47 PM »
Thanks for your valuable input...... Idiot.
 It is down to the Bluetooth chipset and the drivers, and the make of the tablet.
Since the Chinese suppliers do not share the code or changes they make to the kernel and as a result getting this stuff to work can be flakey at best.........


Thank you for posting this informative tutorial..

I am trying to connect a Bluetooth dongle to my Android 2.2 tablet like you did. Same problem as siscor, Bluetooth appeared only once and then never again.

I think it has something to do with the type of Bluetooth chip. Can you share the chip number.brand of the BT module you used.

Mostly because we work with freescale processors where I work, so I have access to their internal copies of ICS/HC and was able to modify what we were working on to work for the tablet as well.  (Basically I took the mx51_babbage or whtever they call it and renamed it... but newer releases of theirs target only mx53 and mx6.  Which is fine, you can use the rootfs from one of the mx53 boards just fine on mx51 by swapping in a proper kernel and such)
5 images for A8 G10

A8 SD IMAGE 4GB part1 part2 part3 part 4

G10 SD IMAGE 4GB part 1 part 2 part3 part4

Strange but i cannot find a single file in this G10 4GB IMAGE. Even the first partition that should be fat32 is completely blank!
Anyone confirms this or has an idea what i'm doing wrong.

Flashed with USBit and Winimage (2nd attempt). no success.


Please reup "G10 SD IMAGE 4 gigabytes," megaupload is down, thank you very much
Be more specific on your question.

TinyWebServer / TinyWebServer now works with Ardunio IDE >=1.0
« Last post by Destroyer on January 08, 2012, 08:06:46 AM »
We have worked out a patch to get the 'TinyWebServer' by Ovidiu Predescu working on the latest  arduino IDE

This is an initial fix, just to get us up and running with some Ideas we are working on, there is still some work to be done inside the 'TinyWebServer' code base, specifically we need to re-write a bit of code and remove some 'dead' libraries.
Nand Flash / 02_Nand Flash chip reader (Read Page)
« Last post by Destroyer on January 06, 2012, 03:13:56 AM »

Command format
READ PAGE [0x00 0x30] [<Col Add.><Col Add.><Col Add.>][<Row Add.><Row Add.>]
Nand Flash / 01_Nand Flash Chip reader (Read ID)
« Last post by Destroyer on January 02, 2012, 10:11:15 AM »
We put together a Nand Flash chip reader library which after several days of testing the 'READ ID' functionality appears to be stable.
Initially there were some issues related to the ID being offset, usually with some sort of dummy byte before the first  genuine ID byte.


This seems to be related to some sort of glitching on the WE# line, so after doing something stupid by inverting the WE#( which should not work). Because looking at the data-sheets the WE#, should only go low after the ALE goes high to latch in the dummy address.

The 'something stupid'

I suspect that this is not the whole picture, because in theory this is preventing the  dummy address byte being written because the  WE# downward edge does not occur inside the  ALE which should take the chip out of specification but instead it makes it work.

Specifically in the top capture (malfunction) you can see the WE# going 'down' then 'up', inside the ALE, but in the next capture  the WE# is 'down' but then it just goes 'up' which does not match the data-sheet but works.

Again, this is possibly why so many people have failed getting this to work because the  Mega is just too slow to operate the Nand-flash chip at the  speed require. To get the mega functioning appears to require the use of a logic analyzer to  physically 'see' what is going on, then 'fiddle' with the waveforms until it works

Open NAND Flash Interface (ONFI ) is supposed to be a standard for Nand Flash chips.
Way way back in the past, Nand Flash chips had different functionality,packaging,timing,command sequences and pin outs, this was great for the industry as it resulted in 'tie in' but bad for everyone else, since it requires you to stick with a standard manufacturer or  have multiple PCB layouts and code bases.
The ONFI was a way to standardize the functionality and pinouts (initially Samsung and Toshiba united to destroy the ONFI)
To test if a chip is ONFI compatible you can replace the 'Address cycle 0x00' with 'Address Cycle 0x20' when issuing a read ID
The chip is supposed to respond with "ONFI" instead of the chip manufacturers ID.
Since it is a no brainer to implement this functionality, we added it to the library, but don't get too worked up about it even now the functionality is still not common, but the manufacturers have at least settled on the pinouts and some commands.

It is usually better to keep things exactly the same until the thing is up, then start to make changes.
Iv'e seen cases where I have made changes that 'did not matter' only to find out later that it would cost me several days and it 'did matter'.

I was recently running some timing tests with a logic analyzer, on power up of the particular board, all the I/O were randomly strobing during bootup, making the Logic analyzers trigger conditions difficult to setup, so in my code I set a unique combination of bits.


then looked for a high toggle on bit 7 plus 0x81 on the Logic analyzers triggers, and it worked fine
but then I got clever and cleaned up the code


and it stopped working........

the reason was that the  Logic analyzers triggers were looking for a high toggle on bit 7 then checking for 0x81, but because the timings for setting the port were delayed by 100ns, the logic analyzer was being woken for the high toggle on bit 7 (0x80) which is not 0x81 and then ignored the 0x01 which is also not a toggle on bit 7, so even though the overall result in the port was 0x81 the reversal of two lines of code made it fall apart.


The test was for the Arduino, I had seen some software timings for setting/unsetting ports on the internet and they did not look right.
Pages: [1] 2 3 ... 10