Search results

great can you comment on the PR as such, as they seem reluctant to add that and it is required.

that patch maybe required. look at the end of the pr github has instructions on how to apply it

did you apply the pr https://github.com/yoonghm/MTP/pull/7 it is required for newer versions of sdfat lib.

I have submitted a PR to the MTP github to fix this properly. The issue is actually in MTP.h OpenFileByIndex which should use oflag_t rather than a byte.

Ahh found the bug line 62 in MTP.h uint32_t to_copy = min(pos - size, avail); should be uint32_t to_copy = min(size - pos, avail); Now it works with Linux. Makes you wonder why the Windows MTP drivers worked at all ;) I'll submit a push request

Seems there is a bug in the TRANSMIT(GetObject(CONTAINER->params[0])); routines. It seems that at the end of a file that is not on a buffer size boundary it sends too much data back, causing the Linux driver to throw an error. I suspect that the Windows driver ignores this error and truncates...

I have been able to make some progress. mtp tools on Linux seem to mostly work, mtp-files lists the files ok, and mtp-sendfile writes files ok, however mtp-getfile fails with an I/O error. Also jmtpfs does seem to be able to mount the device, and list files, but again gets an I/O error when...

Has anyone gotten this to work with Linux (either mtpfs or go-mtpfs). I can get it to work with Windows 7, but there is something mtpfs on Linux does not like about it, and it fails to mount the device with no useful error messages other than "Transport endpoint is not connected". go-mtpfs fails...

This seems to be fixed differently in the most current Teensyduino usb_desc.h and works without this change (which actually will fail).

Yes it is fine with me, can you send me a pull request so i can update my version with the version that works? thanks

yea it needs to be put in flash not ram, the compressed one has the magic incantation for that.

no I never got it to work, which is why I suggest you use the uncompressed version. I did write a verifier for it though and it compares byte to byte with the original.

no that is unrelated, I think you can ignore those errors as they follow a reset and probably the chip is not ready yet.

yea one is compressed the other is not compressed, you can use the uncompressed one as the 1280 has more flash available. The issue is that the standard routine to read flash can not handle 24 bit addresses, so the hack he suggests will fix that. I have not tried it as I switched to using an...

Yea it is related, you need to make the mods he has suggested, as reading from Flash is not as straight forward as I had thought. It runs on teensy as there is no special program needed to read flash.

Ahh That maybe why mine didn't work on the Uno. Thanks for the hint.

and you have pullups on the I2C lines?

did you try my code? are you running through a level converter? as it requires 3v3? I have it working quite well, but not on a 5v arduino. i think maybe the level converters are in the way as it works great on a 3v3 arm chip. I had the same issue with running on arduino, the interrupt line...

you just replace the gslX680firmware.h file with the one from buydisplay.com for the 480x272.

FYI I have not tested it on a teensy though, but it should work :). the FT5x06 is much easier because they actually document the chip, whereas the makers of the GSL1680 decided to not release the register documentation, it also looks like it does not need 28kbytes of firmware downloaded to the...

well this would work on an arduino, except the firmware is too big to fit in the flash of a Uno, it should work fine on a teensy3 or teensy++ though.

cool multi touch is working :) http://youtu.be/REFw3no-Ltk

ya here is the breakout board.. http://www.ebay.com/itm/381051996870

according to the spec it will assert the interrupt after a power loss or after a sleep cycle. They seem easily ignored as the number of fingers value is zero in those cases. I have not done an extensive test on it yet though as I only just got it working. (mine is also currently bare C for the...

@dougm... did you remember to put pullups on SDA and SCL? I used around 10k, but I think 4.7K is recommended.

Ok I made progress, which is good and bad ;) the good news is it works, with the code pretty much as I have posted except for the firmware download (which I now think must be the problem with my posted code). The bad news is I gave up on the Arduino Uno, and used an STM32L100 Discovery board...

This is very frustrating, I am doing everything that the sample code does, the I2C seems to be working and it is setting the registers and uploading the firmware, but it never registers any touches, and any reads are always 0. I'm wondering of the firmware is correct? I may try a random other...

@dougm I have done an initial test sketch for it, I have not tested this yet but this repo will eventually have the library. https://github.com/wolfmanjm/GSL1680 There was an issue with the firmware file, it is so big 27kB that it did not fit in an Uno flash as is, so I wrote a little tool...

hi dougm, Yea I found the gslX680.h file, that is what I was going to use. I didn't notice the firmware was different for the two displays though, I'll make sure I include both. I tried everything with both the adafruit library and the RA8875, the closest I got was by adding the reset line and...

It is actually I2C not SPI, and I think it is using fixed byte transfers. I am about to start working on an arduino driver for this chip as I have the 5" 800x480 buydisplay.com with the capacitive touch screen. However it will not be teensy specific as I could not get my teensy 3 to work with...

Unfortunately I cannot photo it as I dismantled it to test the individual components. The Teensy3 has female headers soldered in (like the arduino). The IMU and motor control board are on a separate proto board, the connections are via male to make proto wires. There was no connection the the...

It wasn't being powered by 5v, it was powered from the USB. and the IMU was 3.3v also.

Hmm well I get 0.7v when nothing else is connected. So I guess it is fried :( I wonder why? Nothing else on the board was damaged, the IMU still works and it is 3.3v as well, and the total current draw was probably around 10-20ms. Oh well, so much for me testing out an ARM. I have had a regular...

No I get about 0.7v on the 3.3v pin, and the CPU gets quite warm.

Hi, I just got my Teensy3. It was working really nicely and had it hooked up to a 3.3v IMU, and everything seemed to be running smoothly. Then suddenly everything stopped. Now when I plug in the teensy3 the system does not recognize it at all, and it appears as dead as a dodo. Clicking the...

Hi, I finally got the scons SConstruct for Arduino from http://github.com/suapapa/arscons working with teensy3. This will compile files in the current directory from the command line. Seems to work better than Makefiles for Arduino sketches. This version will probably not work for other...

Thanks Paul. I'll be using the FreeIMU library on Teensy3, so Hopefully this will help. I have all the components for the board, just need to figure out how to solder SMD ;) BTW the Pololu minimu seems to work on teesny3 with no changes whatsoever.