Author |
Message |
Intellecta Newbie
 Joined: 07/05/2016 Location: AustraliaPosts: 22 |
Posted: 09:37pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
Dear Members.
Have an issue with USB on a simple 64 pin plus design. Programs OK but no activity on console (pin6 and Pin 58) after reset.
Used the hex file on V5.2 dated 29/6/2016
However, in the siliconchip Aug 2016 article, the hex file mentioned is dated 15/7/2016. I cannot locate this file and thinking I may have the incorrect hex file.
The circuit is really simple, have checked all the solder points, connection to the pins etc and it appears to be correct.
Software issues are the last option.
Thanks
Tony Pugatschew
SIlicon chip hex file is 0710816A.hex |
|
WhiteWizzard Guru
 Joined: 05/04/2013 Location: United KingdomPosts: 2932 |
Posted: 10:01pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
Hi Tony,
When you say 'no activity on console', are you referring to the built in USB connection?
If so, then this is kind of correct! Lets assume you are using on a Windows machine, and using TeraTerm (TT) as the console program to write/edit code. Then when you FIRST physically connect the 64pin MicroMite to your Windows machine, Windows will negotiate the connection to the MicroMite. Then running TT will allow you to work away as expected BUT as soon as the MicroMite is reset in any way (reset button, or WatchDog timer), then the USB connection is 'dropped' resulting in TT not responding. This results in the appearance of the MicroMite not responding - but as discussed on forum before, this is a Windows/USB issue.
In TT, simply 'Disconnect' (option in menu tabs) and then select 'New Connection' (alternatively just physically disconnect the USB lead, then re-insert).
It is one of the most annoying things when 'debugging' code via the built in USB connection.
However, If you use an External USB-to-TTL adaptor and connect directly to the Console pins on the MicroMite, then this will work fine and you'll be able to reset the MicroMite as much as you like without the connection ever 'dropping'.
WW
Edited by WhiteWizzard 2016-07-30 |
|
Intellecta Newbie
 Joined: 07/05/2016 Location: AustraliaPosts: 22 |
Posted: 10:19pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
Dear Whitewizard,
Thanks for rapid reply. I am connected to pin 6 and 58 via a cp2102 usb adapter.
Your explanation is great because I was thinking of dropping the USB converter and using the connections via pins 36 and 37. The rationale is that we will be using these devices in education and these adapters get lost or stuffed.
But, there may be frequent resets if the programs are incorrect so the USB adapter seems like the best way to go.
Will need to look closer at the layout. Had no issues with the 28 pinner.
Thanks again
Tony Pugatschew
|
|
Grogster
 Admin Group
 Joined: 31/12/2012 Location: New ZealandPosts: 9590 |
Posted: 10:33pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
Note there are NO connections to pins 36 & 37 around the edge of the board - they are routed specifically to the USB socket only.
As to the console on pins 6 and 58, that is the way I develop pretty much everything.
Once you have unplugged and replugged the USB cable about a hundred times to rest the freakin' VCP that drops off as soon as you press RESET, you get so annoyed with that method, that the external USB-serial adaptor and the native console pins are really the preferred way. I think most of us here would agree, if that is not too presumptuous on my part.
Using the CP2102(which is a good choice), then Pin-6 of the MM+ module needs to go to the TXD pin on the CP2102 module, and Pin-58 of the MM+ module needs to go to the RXD pin on the CP2102. Ground to ground, naturally.
That done, and TT opened with the correct COM port @ 38k8, the module should respond.
How sure are you, that you are talking to the CP2102's VCP?
Perhaps you have selected another port by mistake? Smoke makes things work. When the smoke gets out, it stops! |
|
WhiteWizzard Guru
 Joined: 05/04/2013 Location: United KingdomPosts: 2932 |
Posted: 10:34pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
Ensure you have the vCap connected, 10K pullup on Reset pin, Crystal & caps, and AVdd is connected to 3v3 (preferably via a 10R).
Also ensure your 3v3 can supply at least 100mA.
I am sure you have the above sorted - but worth mentioning just in case . . .
WW |
|
WhiteWizzard Guru
 Joined: 05/04/2013 Location: United KingdomPosts: 2932 |
Posted: 10:35pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
As Grogster has mentioned (and it catches a few people out) - DO ensure you have the Tx and Rx pins connected the correct way round |
|
WhiteWizzard Guru
 Joined: 05/04/2013 Location: United KingdomPosts: 2932 |
Posted: 10:40pm 28 Jul 2016 |
Copy link to clipboard |
 Print this post |
|
May seem silly to say this but do check you have +V powering your circuit!
I mention this as I made a crazy mistake yesterday while testing an Explore100 Module. I programmed it from a PicKit (without error) with the Explore unit powered from the PicKit3.
Then I disconnected the PicKit, plugged in my console connection (GND, Rx, Tx), and then spent time scratching my head as to why no response. Then the penny dropped - there was no +V.
Bottom line is - it programmed ok, but then no activity on console |
|