Firmware update, not possible on either windows or mac osx...

[soren]

EDIT Now it freakin works.. SOooo, there's a difference between vcp and the dxx ftdi drivers.. i did not know about the vcp before until just now. installing the vcp seems to be working now. also, i have currently unloaded the apple ftdi driver which might also be necessary but i'm not sure. phew, this is a rather frustrating process to go through.. thanks so much for the help @jmarcelino though!

Hello,

Running Mac OSX 10.12.3 with the lopy connected via an original apple dongle to the USB C port. Lopy inserted correctly into the expansion board, all headers inserted properly and jumper is in place. When trying to run the firmware updater tool I just get "the upgrade failed, please check the connections...."

after several attempts I tried running it on my windows 10 PC, but here there are just no visible ports in the update tool... jesus

any suggestions ?

EDIT (just to give an overview):

• I tried a different USB cable, without any different result.
• I do see the lopy listed as an ft230x basic UART device in my System Report in OSX
• Arduino's work just fine on the same mac laptop

[rskoniec]

With W10 installation of the VCP (Virtual COM Port) driver is pretty straightforward.

@mmarkvoort said in Firmware upgrade troubleshooting - checklist/procedure:

I don't know if it is relevant but when i wanted to update/connect through USB I had to install the USB driver manually. Mine called FTDI driver where VCP or D2XX are types of drivers. With one of the two it said it was installed but still i coudn't update/connect.

OK, I took my notebook with Windows 10 Pro x64 with internet access and plug LoPy on Expansion Board to it for the very first time.
Here is Device Manager just after connection:

After about 30 seconds Windows Auto Update mechanism has done all the job:

[jmarcelino]

@soren
You posted a few days ago in another thread saying you were trying to use the cu.lpss-serial2 device to access the REPL on your Mac and I replied saying that wasn't the correct device.

Are you still trying to use cu.lpss-serial2 in the firmware upgrade tool? Have you found the correct device ?

[soren]

@jmarcelino Hi, i did not see your reply in that thread sorry.
Looking into it now. I didn't realize the REPL and firmware update was related so closely

[jmarcelino]

@soren
Yes both firmware update and REPL are done over the UART serial.

If you're not seeing the correct device try installing the FTDI drivers from http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_3.dmg

[rskoniec]

@soren Or http://www.ftdichip.com/Drivers/CDM/CDM v2.12.26 WHQL Certified.zip For Windows. ;o)

[mmarkvoort]

@rskoniec @soren My problem why I had to install manually was probably because I had my windows updates shut down. So it wouldn't update automatically. So probably installing it manually will help.

[soren]

@jmarcelino Right!

I installed FTDI drivers on windows now which made it possible to update on my windows PC (actually thought that was only necessary for mac), but having installed ftdi drivers on my mac doesn't make any difference unfortunately..

[soren]

@jmarcelino I do have ftdi drivers installed, but that does not seem to make a difference on my osx system. It shouldn't be the USB C dongle obscuring things, because it's working just fine with eg. Arduino boards

[jmarcelino]

@soren
Try looking in  (Apple) menu -> About This Mac -> press System Report and then choose USB from the list

If your Mac can see the Expansion Board you'll have a device saying FT230X Basic UART , like this:

[soren]

@jmarcelino yes, my mac see's the unit as a ft230x basic UART.

EDIT: I also tried a different USB cable now, just for the sake of excluding that.. no difference

[jmarcelino]

@soren
Ok that looks good, so what do you get from a ls -l /dev/cu.* ?

Is there a line with /dev/cu.usbserial-xxxxxxxx ? (the xxxxxxxx part doesn't really matter)

EDIT Also can you post the result of

kextstat -b com.FTDI.driver.FTDIUSBSerialDriver

[soren]

@jmarcelino

EDIT EDIT
Now it freakin works.. SOooo, there's a difference between vcp and the dxx ftdi drivers.. i did not know about the vcp before until just now. installing the vcp seems to be working now. also, i have currently unloaded the apple ftdi driver which might also be necessary but i'm not sure. phew, this is a rather frustrating process to go through.. thanks so much for the help @jmarcelino though!

I don't see a cu.usbserial-xxxx... no, sorry. this is what i get:

crw-rw-rw- 1 root wheel 20, 3 Mar 23 10:41 /dev/cu.Bluetooth-Incoming-Port

crw-rw-rw- 1 root wheel 20, 5 Mar 23 10:41 /dev/cu.JabraStylev130-CSRGAIA

crw-rw-rw- 1 root wheel 20, 7 Mar 23 10:41 /dev/cu.iPhone-WirelessiAP

crw-rw-rw- 1 root wheel 20, 1 Mar 23 10:41 /dev/cu.lpss-serial2

here's my result of kextstat -b com.FTDI.driver.FTDIUSBSerialDriver:

list itemIndex Refs Address Size Wired Name (Version) UUID <Linked Against>

EDIT
so.. this looks like the ftdi driver is not being found at all, right?

[jmarcelino]

@soren
Yes it's not loading the driver for some reason. Can you post the result of:

kextfind -case-insensitive -bundle-id -substring 'FTDI' -print

to see if it's correctly installed and if there's any conflicts?

you can also try manually loading it with

sudo kextload -bundle-id com.FTDI.driver.FTDIUSBSerialDriver

[soren]

@jmarcelino said in Firmware update, not possible on either windows or mac osx...:

kextfind -case-insensitive -bundle-id -substring 'FTDI' -print

kextfind gives me:
/System/Library/Extensions/AppleUSBFTDI.kext
/Library/Extensions/D2xxHelper.kext
/Library/Extensions/FTDIKext.kext
/Library/Extensions/FTDIUSBSerialDriver.kext

this is so weird though. trying to unload the mac ftdi driver with:

sudo kextunload -b com.apple.driver.AppleUSBFTDI

just gives me:

Can't create –b.
Can't create com.apple.driver.AppleUSBFTDI.

[soren]

@jmarcelino
so, after being able to connect and I synced a project several times - now I suddenly am back to being unable to connect. I did not reboot my system.. It just tells me "invalid device address.." and the lopy doesn't show up in configurations.. this has got to be the most uneasy mcu i've ever dealt with

[jmarcelino]

Just saw your edit on the original post. Glad you got it working in the end!

Yeah USB serial drivers can be a confusing mess - and actually FTDI has some of the best drivers.

[robert-hh]

When you say: "synched a project", does thar mean you#re using Pymakr? If yes, don't do that. Pymakr simply adds another layer of strange issues. Better use basic tools, like an ftp client of your choice, screen or telnet, ...
There you have much better response, and if you have issues, the reason is obvious.

[jmarcelino]

I agree, stick with telnet + ftp for development and leave the serial connection for firmware upgrades and debugging.

I do think you have too many serial drivers installed and active and - as they say, too many serial drivers in the kitchen spoils the broth - you'll need to actually disable or delete the ones you don't need.

[soren]

@robert-hh hi Robert, thanks for your reply.

So I managed to get an FTP access up and running (awesome!!) but I also managed to try and change the server and wlan login credentials, which now resulted in the lopy not showing up as a wlan.. (well f*'** done soren).. so now I literally have no idea how to get access to my lopy with USB not working propperly.. any ideas ?

EDIT
did a factory reset, but this did not seem to change my boot and main files.. which means i still can't see the lopy on wifi