 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Bricked explore 64+
  Page 2 of 4   |
|||||
| Author | Message | ||||
| robert.rozee Guru  Joined: 31/12/2012 Location: New ZealandPosts: 2442 |
three rules for a happy life: 1. if your device has on-chip USB device-class support (ie, it plugs into a PC), DO NOT make use of said support. on-chip USB device-class support will always eventually end in tears, no matter how good everyones intentions are. always use an external USB bridge: CP2102, CH340G, or 1455 ('microbridge') are the preferred choices. 1a. truth be known, God only ever intended for on-chip USB device-class support to be used by the peoples of finland and neighbouring regions. 2. if your USB chip has the word 'prolific' on it (or a PLxxxx part number) immediately and violently place it in a trash can. do not pause to think about it, just do it NOW. no good will ever come from a prolific USB chip, no matter how much you may wish to think otherwise. 2a. FTDI have in recent years upgraded their drivers to provide the same level of quality offered by prolific. where once there was just one true path to madness, now there are two. 3. always have a SHORT FAT USB cable to hand. when things go to custard, switch over to using it. by SHORT, i mean less than 12". by FAT, i mean able to support the weight of a full-grown politician (that is, if the cable was not so SHORT). one can not emphasise enough the virtue of such SHORT FAT cables. cheers, rob :-) |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4044 |
I've used Prolific PLxxxx devices without issues - but never tried with WinSucks, only Linux. John |
||||
Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
Well I'm never to give up so tried out that prolific driver again and got nothing at first. So looked at the manual and it did say to load anew driver just let windows do the work and find it. So did that and now got it working with no problems. Gotta say this has taken a while but finally got the ili9341 working and after several attempts using a pen kept getting errors on the touch calibration. So tried again just using my fat finger and it passed first time. I used an external power supply ( 4 off AA batteries in series), rather than use the voltages from the driver board which I found didn't work. Now for a search thru the forum to try and find some library files and some other code so I can get a few pointers. Regards Bryan |
||||
Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
Bryan, that's great you got it up and running. What is it you are trying to get pointers for? |
||||
| Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
G'day Guy's, Got a question about SDCards as I tried to use my old Verbatim 2 gig card and it won't connect at all. So went and bought a new 16gig card today and it is still refusing to see the card. I have put OPTION SDCARD 12, 14 in as I am using the explorer board so I do assume the 12 and 14 are the right pins, as that is what is listed in the PDF file. Now I did put some old bas files on aswell as a bitmap pic of my dog. When hit click on files in MMedit the pic just and software just hangs and I need to do a reboot. Regards Bryan |
||||
| Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
Which explorer board? |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
On my Explore64 > option list > OPTION SDCARD 12, 14 > > files A:/ 4437 ta.bas 4698 tain.txt 47000902 tajunk.txt 2702 taout.txt 5529 taouta.txt 4445 test2.bas 4445 test3.bas 4445 test4.bas 0 directories, 8 files > With MMEdit you need to select the correct syntax for some of the commands to work. I use "Micromite_Plus_V5.3" I had the syntax option stuffed up for some syntax files so try a few different MM_Plus ones. THis ZIP has the 'fixed' files which need to go into the data folder. The Dtat folder can be found from Help/About 2018-08-19_145506_data.zip In the Chat window, you should be able to type in "files" and get a response whatever syntax you have selected. The card I currently have in is a 2GB but just about any size should work OK. Jim VK7JH MMedit |
||||
| Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
The first one that Grogster brought out so I think it's version 1A explorer 64+ Regards Bryan |
||||
| Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
I will see if I can give it a try on my SC MM+64 BP tonight. |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
1A is from the prototype run - very old...... From what I remember, the 1A DID HAVE AN ERROR ON THE LAYOUT with respect to the SD-card. I remember having to cut tracks and run thin jumper wires to get it working. Perhaps this was just my prototype. Does YOUR one say "(PROTOTYPE)" on the bottom silkscreen? If so, it might need a gentle hack..... I've just looked this up on my files, and YES - the 1A PCB's have errors with the SD card slot, so that is where your problems will be. HACKS NEEDED TO MAKE IT WORK: 1) Pin-12 on the PIC32 is connected to pin-1 on the SD card, and it should be pin-2 on the SD card. 2) Pin-5 on the PIC32 is connected to pin-2 on the SD card, and it should be pin-3. 3) You will need to cut the ground reference on pin-3 of the SD card and reconnect. I seem to recall this means you have to REMOVE the SD card socket, as the ground track is connected on both sides of pin-3 on the SD card. Probably not worth the effort for a 1A board.  Smoke makes things work. When the smoke gets out, it stops! |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
I just checked mine - it's a 1B. Jim VK7JH MMedit |
||||
| Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
G'day Guy's my mistake I took the module off the breadboard and it is Version 1B Regards Bryan |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
1A's were the only ones to have that error. 1B's and 1C's had that error corrected so the SD card would work as expected!  The thing I really need to know at this point, is if Bryan's one has that "(PROTOTYPE)" marking on the bottom silkscreen. I might have done a version 1A1 where the SD card error was fixed - but it would still have been called a "1A". I don't normally sell the prototype run boards unless they prove to have no faults. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Whew.  It SHOULD be working then, as 1B's and 1C's are definitely correct. Smoke makes things work. When the smoke gets out, it stops! |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
Bryan, If you haven't done so already, just type OTPION LIST at the command prompt to ensure the pins for the SDCARD are 12, 14 Mentioning this as I sometimes type too fast when setting OPTIONs and what I thought I had set have actually been different; i.e. a '1' gets dropped and it would become something like OPTION SDCARD 2,14 (for example) WW |
||||
| Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
G'day Guy's, Just did a fresh hex rewrite with beta 10 and having fun getting the touch to calibrate. Got the lcd working nicely and when I use my finger to do the touch screen check after the second screen it goes hardware failure. Use a pen and it gives the out of range values. Now I did have fun with this yesterday and finally got it with using my fat finger. I have included a chat window log and as one can see after I tried the calibrate routine it just just resetting with the lcd screen flickering everytime it reset. Do a hard reset fix's the problem but using a pen pressing at the cross hairs should calibrate the touch screen but it is way out. Jim I did download that file and install it too and still no change it won't see the sdcard. Regards Bryan 2018-08-19_164349_beta_10_log.pdf |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
Bryan, Can I just confirm: 1> You have an Explore 64 module (Grogster design, NOT the BackPack design from SC) 2> You have an ILI Touch screen wired to the above as per MM Plus User Manual 3> You can't read the SD card still First obvious question. Which SD socket is the card in? The one on the TFT, or the one on the E64? Ensure you use the E64 uSD socket and NOT the TFT SD socket! Awaiting your reply . . . WW |
||||
| Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
Bryan, I have had similar experiences. Although I am not 100% confident I have found my problem I did find that: If you hold the pen/finger in place until the screen prompt moves to the next position it generally works. If you release before it is ready you will see those sorts of errors. |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
I forgot to mention above that I have seen issues with Touch when an SD card is in the TFT's SD socket. |
||||
| Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1483 |
Hi WW I an using the sdcard slot on the explorer board |
||||
| Page 2 of 4 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
