Author Topic: Re-Post "No mc-dongle bootloader found"  (Read 294 times)

mcThings

  • We Connect Things To The Internet... That Can't Be Plugged In.
  • Administrator
  • Jr. Member
  • *****
  • Posts: 68
    • View Profile
    • www.mcthings.com
Re-Post "No mc-dongle bootloader found"
« on: June 01, 2016, 05:51:28 pm »
'No mc-Dongle-Bootloader found'

I just received my McStuff. After reading all of the posts, it's clear that the first thing one should do is update the firmware using the OTA Updater. After connecting the McDongle I could see that Win 7 loaded all of the drivers. But after I started mc-OTA Updater – v1.2.1 the status message was ‘No mc-Dongle-Bootloader found’.
I checked Win 7 Device Manager and can see a COM 60 port, which I guessed was the McDongle. If I unplug the McDongle then the COM 60 port goes away, it reappears after I plug the McDongle back in.
I've tried plugging in the McDongle first, then starting the mc-OTA Update, but no joy. The I've tried starting mc-OTA Update and then plugging in the McDongle. In all case I always get the ‘No mc-Dongle-Bootloader found’ message on the lower left part of the status line.
What really obvious thing am I missing?Like


mcJohn
mcJohnAdmin6d
Our expert that wrote the OTA has just left. We will give you an answer tomorrowLike

mct_user
mct_user6d
Hi. I experience the same issue. Win7 64 bit and assigned COM6 for the mcDongle.
Please let me know as wel.
Thanks!Like


urbite
urbite6d
My McDongle was initially plugged into my laptop docking station, which means that there's a hub in the USB chain. I just tried plugging the McDongle directly into one of my laptop ports, but I still get the ‘No mc-Dongle-Bootloader found’ message' from OTA Updater.
I tried this because I've had a few USB devices that didn't work well with a hub, but it made no difference in this instance.Like


mct_user
mct_user6d
Mine is plugged directly in a free PC frontside port. I get green LED3V3 lighting up. LEDnRF is off.Like

woozer
woozer6d
The mcModules updated fine using the OTA update, don't forget to enter the serial number, remove batery, hit search, insert battery, module is found and you can update.Like

urbite
urbite6d
woozer – the issue is that the OTA Updater isn't recognizing the McDongle, thus it never has a change to attempt an update.Like


woozer
woozer6d
Do you see an extra com port in device manager when you connect the McDongle?Like

mct_user
mct_user6d
An extra? No, I only see its FTDI com port.Like

woozer
woozer6d

Device
Are you sure you are using an udb data cable, and not an usb power only micro usb… i had that once…Like

mct_user
mct_user6d
Sure! Othewise I woulnd't had seen the COM port in deviceManager PLike

woozer
woozer6d
Strange stuff ; So your you don't have the ready message in lower left corner, as in the supplied image… OtaLike

urbite
urbite6d
From my OP:
I checked Win 7 Device Manager and can see a COM 60 port, which I guessed was the McDongle. If I unplug the McDongle then the COM 60 port goes away, it reappears after I plug the McDongle back in.
Message in the lower left hand corner (also from OP):
‘No mc-Dongle-Bootloader found’ message on the lower left part of the status line.
McThings admins – any idea what the issue might be? Are you looking for the McDongle on all COM ports, not just a limited lower range such as COM1-COM4?Like


mc-gyver
mc-gyverAdmin6d
We are looking for mcBoot on all com ports.
Can you check in the (USB Serial Port Properties->Property->Device Instance Path) if it has similar string with FTDIBUS\VID0403+PID6015+MCxxxxxx\000
CaptureLike

urbite
urbite6d
From Device Manager properties for COM60, the ‘Device Instance Path’ is:
FTDIBUS\VID0403+PID6015+MC88FNFA\0000Like


mc-gyver
mc-gyverAdmin6d
Sounds like USB chip is ok but you got an unresponsive wireless processor. We will send you a new mcDongle as soon as we can.Like

urbite
urbite5d
It looks like pin 5 (P0.01/AIN2) and pin 6 (P0.02/AIN3) are have a solder bridge between them. Is this intentional?Like
5d
I removed this solder bridge but the OTA Updater still doesn't find the McDongle. I connected to the FTDI 230X chip using PuTTY @9600 and monitored pin 15 (TXD) with a scope and I can see expected serial data when I press a key in PuTTY. Also, when I press a key in Putty I can also see green LED50 blink with each keypress. The TXD signal also appears on pin 18 of the Nordic nRF51422. The 32KHz oscillator on pins 54/46 of the nRF51422 is alive but the 32MHz oscillator on pins 37/38 is dead. nRST on the SWD header is high.
That's all of the troubleshooting I can do without a schematic or an ARM SWD interface.
Do you have my information needed to send me another McDongle? You should be able to cross-reference my name with my order. I'll also send an email to Thomas E. referencing this thread.Like


mct_user
mct_user5d
Admin, can you send a unit also to me? As I already mentioned I experience the same problem.
Thanks!Like
5d
Small diff in the Dev Inst Path, I got : “…+MC8B03FA\0000”Like

mc-gyver
mc-gyverAdmin5d
Urbite,
The solder bridge was intentional.Like
mct_user
mct_user5d
Mc-gyver,
Again, can you please help me in restoring the functionality of my mcDongle?
So far, there was no response from your side. Do you read my posts as wel? It seems that you're not, or at least not willing to answer.Like

mc-T2
mc-T2Admin5d
oops, my post disappeared!
mc-Gyver is on a mission today as the paperclips, tinfoil, rubber bands and chewing gum are missing!
I have sent a private message to you to arrange the replacement dongle. It appears that a very small number of dongles have this issue. Thank you for bringing this to our attentionLike

mct_user
mct_user5d
I saw your post the first time. Thanks a lot! I cannot see the private message though. Any idea?Like

mc-T2
mc-T2Admin5d
private message doesn't appear to be working right now for some reason. please email us at kssupport@mcthings.comLike

mct_user
mct_user5d
I've just sent you the info via the indicated mail.

Share on Facebook Share on Twitter