Oak no longer receiving uploads

[maximo80]

No difference If I swap TX and RX, I can see activity in TX serial module pin but not in RX pin.(it looks normal because it seems oak doesn't answer.
About Com port, I have re-installed the original drivers but with the same result, com3 is communicating but something should be wrong with RX.
About VM in mac OS, it looks fine because when I connect the usb I can choose between mac and win10.
I have re-checked the connections hundreds of times but it isn't.

thanks.

[emardee]

Sounds like a problem with com port adapter to me. Since it is new, you might have got sent a faulty unit from Amazon possibly.
Have you got anything else you can connect so you can test your com port adapter and check the driver settings are correct?

[Blitzfx]

If anyone experiences this and has a serial adapter I would be most grateful for a memory dump of the Oak before you restore it - so we can try to see what is going wrong, or at the least taking a look at the serial output of the Oak

The command to dump the whole flash is:

esptool.py --baud 115200 --port COMX read_flash 0x000000 0x400000 flash_dump_full.bin

Where COMX is your COM PORT

You can email it to me at support@digistump.com

Thanks,
Erik

How long does this take? Because it says: Connecting... Please wait....

Been waiting 5-10 minutes

I tried uploading the LED blink code to particle, and i assume particle tried to upload it to the oak, but instead it just bricked it. Only pwr is on and there's no LED flashing. I also can't see the oak when i scan it on wireless

[PeterF]

@Blitzfx: That command should start showing some activity almost instantly..., and only takes 2 minutes at most, more like 1 minute.  Or at least it did when I used to load the restore firmware!

Did you power up the Oak with Pin 2 connected to GND? I don't think the esptool command works unless you do.

@maximo80: One 'dumb' test to do if you have Arduino or some other terminal program on the VM system, is to just connect the FTDI TX to RX, and see if it echos back whatever you type (i.e. when you type something without TX&RX joined, nothing appears in the Arduino serial terminal but it will when they are joined). Then you know that the RX & TX are working properly on the FTDI board, within the VM. All I can suggest then is use some different jumpers if you can, just in case one is dodgy.

[Blitzfx]

It should show some activity, and it does for a little bit.
Here's how i've connected it. And I've connected pin 2 to ground otherwise it just says failed to connect or something like that:
http://i.imgur.com/S5KRP1p.jpg

http://puu.sh/noaCe.png

This is the second time it's bricked when i'm trying to load the "Start" example code. http://puu.sh/noaFM.png

Which setting did you pick in the Arduino IDE? http://puu.sh/noaQD.png

I've followed the instructions on here https://github.com/digistump/OakCore/releases so I'm starting to run out of ideas now.
-------

Well it seems i've bricked it for a 3rd time now.


The wireless signal isn't being broadcasted from the oak anymore and the LED isn't blinking.

[PeterF]

Blitzfx, I'm still on v0.9.3 - I never upgraded to v0.9.4, I didn't see it until Erik rolled it back, so never moved to it. So I only have the one entry for the Oak (Oak by Digistump) on my boards menu. I'm running Arduino IDE  v1.6.7, and it seems to be playing with my Oak fine when it wants to behave.

Remember to only have Pin 2 grounded when you want to access the config / restore mode - otherwise that would be the cause of your problems.

That is very peculiar that you are having issues that way - it is programming ok, and is rebooting to load your program, but then gets stuck. Might be worth removing v0.9.4 from your Arduino IDE, and rolling back to v0.9.3 if you can? It doesn't look like the package supports multiple versions, and I don't want to break my working config just yet , so I don't know if you re-install the oak boards package if it will install v0.9.3 again... I'm just wondering if it is something that broke for your setup when the fast OTA updates function was released in v0.9.4??

[Blitzfx]

Ah, I didn't realise the v0.9.4 referred to the Arduino IDE board version as well. I thought it was something to do with the http://rawgit.com/digistump/OakSoftAP/master/config.html

I'll downgrade/re-update and give it another try. Not going to use v1.6.7 though. Maybe if it fails again I will.

I also disconnect everything after I restore the oak and plug it into a separate usb power supply.

[Blitzfx]

yaaay it works


but quite a long time to program lol

[PeterF]

Yay! Success! Yeah, I noticed the same as well. When FastOTA is ready, code uploads should be a lost faster. My setup usually takes about five minutes, sometimes longer, but seems to get there in the end, so not too worried yet!

[maximo80]

@Blitzfx: That command should start showing some activity almost instantly..., and only takes 2 minutes at most, more like 1 minute.  Or at least it did when I used to load the restore firmware!

Did you power up the Oak with Pin 2 connected to GND? I don't think the esptool command works unless you do.

@maximo80: One 'dumb' test to do if you have Arduino or some other terminal program on the VM system, is to just connect the FTDI TX to RX, and see if it echos back whatever you type (i.e. when you type something without TX&RX joined, nothing appears in the Arduino serial terminal but it will when they are joined). Then you know that the RX & TX are working properly on the FTDI board, within the VM. All I can suggest then is use some different jumpers if you can, just in case one is dodgy.

Hi everyone,

I've checked TX/RX in FTDI board and it seems OK, I attach a screenshot on arduino serial monitor and an image of FTDI.
I don't know what to check now. How can I check if Oak TX is working fine?
If I take out the Oak GND from FTDI board GND then TX/RX in FTDI are blinking but with the same error message.

Help please!!! I am desperate

[PeterF]

It looks like your problem may be in fact the FTDI board, given the message you're getting from the serial console  - the “NON GENUINE DEVICE FOUND!” message - as you shouldn't be getting that. I don't expect the esptool is robust enough to remove that message (which is injected into the serial stream by the latest FTDI driver, as FTDI are busy ruining peoples days yet again[1]). See if you can roll back to an earlier driver, or remove the current one and manually install an earlier version. The only thing that you should see in the serial console when TX & RX are looped is what you type and send to it - it should merely echo what you send. Anything else, and it ain't gonna work!

[1] http://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/

[Blitzfx]

oh my god lol

Poor maximo

Where did you buy it? Was it Ebay? It would be nice so everyone else here can avoid that place.

[PeterF]

lol... hope you mean that seller! eBay is a good place... a nice place... as long as the buyer beware!

If you can't get back to an older driver for the FTDI, grab a CH340 USB to Serial adapter (actually, just get one anyway!!) - even the cheapest ones on eBay now ($1.04 in Australian Dollars  - my local currency - http://www.ebay.com.au/itm/Adapter-STC-USB-To-RS232-TTL-CH340G-Converter-Module-replace-PL2303-CP2102-Z3-/131558679211?hash=item1ea18222ab:g:-VQAAOSw9N1VqHym) seems to have a 3.3v option, which you need for the Oak.

[maximo80]

Thanks pfeerick,
It was exactly what you said, I had to downgrade FTDI drivers as you posted and problem solved.

About second Step to restore OAK ( this is what I read )
This will not restore an Oak that has had its Particle Config overwritten at 0x100000 and 0x201000 - a device where that has occured can be partially restored by this method but then will need its device id set via serial, and you'll need to have recorded it previously. Then connect at 115200 baud and send set\n40\n{"device-id":"123456789012345678901234"}\n where 123456789012345678901234 is replaced by your device-id. You can also send a raw POST to 192.168.0.1/set with the same JSON while connected to the AP of the Oak

I have device id number but I do not understand when it indicates POST to 192.168.0.1/set with or connect to 115200 baud or set\n40\n{"device-id":"123456789012345678901234"}\n
where have I to connect it ? via arduino IDE(serial monitor) or command prompt

Thanks

[digistump]

Arduino Serial monitor set to 115200 baud would work for that - you only need to do this step if you overwrote your Oak firmware with some other firmware (like NodeMCU/Arduino ESP8266)