Hello everyone! After getting my edison, I tried to install Ubilinux for its capabilities to host a ad hoc network, but after trying, my edison board has not been working at all. When both usb cables are plugged in, I see that MERRIFIELD driver pops up and down in the device manager, and am unable to figure out why. After waiting for 1 minute, everything settles down in my device manager, but it just isnt right. Only one COM port shows up, and not the one used to program arduino even though I have both cables plugged in! I tried connecting to the Edison board through Putty, but nothing happens. Is there any way that I can fix this, or do I have to get another one? Thanks again.
refer to this
It looks like you are using Windows host?
Although this link points to a question about a Ubuntu host, it may still apply. You may want to try going thru a hub. I haven't tried on Windows.
There is a COM port open, but is not meant for programming through, rather connecting through it using Putty, even though I have connected both usb cables to my computer. I tried to use a Ubuntu computer to flash the default Linux distribution on the board, but it couldn't connect to the Edison. In the device manager, I see that there is a "Merryfield" device not having a driver, but then goes away all of a sudden and disconnects from my computer when plugging in the Edison to my computer. Is there any way to reset the board and erase its storage directly on the board or do we have to connect to it and flash it via a host computer? Thanks anyways.
First thing to check here is where exactly it fails. That means you need to connect to the serial console - which is on the micro-USB port at the edge of the board (either Arduino or mini-breakout). Don't connect the second USB port (unless you're powering the board that way), it's irrelevant at this step.
After that connect to the console using Putty or other terminal client, specific instructions could be found in e.g. Quick Start Guide. Connecting to this port requires FTDI driver to be installed, so if you haven't done this before, you may need to do this now - again Quick Start Guide is the best source here.
After connecting to the serial console, capture the output of the complete board reset process and post here - that would be a good first step to check what's going on there.
I already have installed all the drivers for the edison. It used to work, but after installing Ubilinux onto the Edison, it seems to have gone throuh all of this trouble. The weirdest part is, is that after installing Ubilinux, it still seems to be holding Yocto as its OS.
There may be several explanatons to the situation you describe, because the description is a bit too generic That's why I'm asking for the console log - that will show everything.
Okay, nice way of presenting several things at once
All in all, I can say after watching that:
Thanks for replying AlexT_Intel,
I am not sure how to do what your saying. What I did was I ran the command journalctl -x --no-pager" and got a bunch of text, and then put it inside of a file, but I do not know how to do the lsmod command that you want me to do. should I pipe the output of the "journalctl -x --no-pager" command into the "lsmod" command, because I tried that and it would not work. Oh and yes, when trying to flash into Ubilinux a while ago, it did not seem to have done anything, because as you saw in the video, the Edison is still using Yocto. Anyways thanks alot.
Okay, so step by step:
So I went into the Edison board and logged on and followed all the commands, but the problem that I had noticed was that there were too many lines for the output of the first command that Putty could not get back, so truthfully, what is on the txt file, is not everything that was being spilled out by that first command.
Okay, so something is apparently wrong there - lsmod shows no modules loaded, which is wrong and this
is an additional specific sign that the cdc-acm driver (the one that creates that USB link to IDE, among other things) isn't loaded as well.
At this point I'd suggest you to reflash the board using the flashall.bat/flashall.sh way (i.e. non-OTA), as it's the most robust way to do that, though it requires some experience - so let's try one more thing first.
Try out these instructions: and let's see if that works. To be honest I doubt it would given the state of the system, but let's see.
Can you guide me into doing this, because after downloading the flashall.bat file with a bunch of other files, it is telling me to install the xFSTK downloader which is only available in Linux. If you can explain to me the same way you did in your previous post, I would be very greatful . Thanks again.
That's exactly I don't recommend you to go this way at the first try Let's first try that Wi-Fi method, it contains the step by step instructions, it should be easy to follow and I have some hopes for it.
If that doesn't work, then I'll explain you step-by-step how to use that flashall method.
I am unable to get the wifi up and going, which I would suspect comes from the errors that I am getting in the txt file I uploaded. I think that we should go with the flashall.bat option.
Okay, so let's try it out. Generally, it's really simple. Sorry I haven't been able to attend to this earlier - this week is a bit busy one.
1) Install dfu-util version referenced in this post: (generally I think non-MSVC would also work, but the recommended one is MSVC and I have only seen this link externally). Either unpack it somewhere and add it to PATH or just put it into the same folder as the unpacked Edison image (where the flashall.bat is);
2) Connect the serial console cable to your PC and start PuTTY to see everything that's going on;
3) in the cmd.exe window, with current directory being the one with the flashall.bat, run "flashall.bat" and as soon as it starts, connect the second USB cable, plugged into the second microUSB port on the Arduino expansion board, to your PC. Connect the power connector from the power adapter right after that as well.
4) flashall.bat should print several messages saying that it's waiting for the board, then as soon as the board gets into the early boot stage, it should recognize it and start uploading the data. If that doesn't happen and the loop continues, then times out - then start the flashall.bat again and simply reset the board by pressing the Reset (SW1UI5) button on the expansion board (the one closest to the Intel logo).
5) After all pieces are downloaded, the board will restart once, do the intermediary boot + setup phase, reboot again and boot into the normal multiuser target.
If anything goes not the way I'm describing above - capture the video of the process just like you did before and post here, we'll see what else can be done.
Thank you so much! that completely resolved my issue! Thanks again for resolving my issue!
One more Question though: How would you set up an ad-hoc network hosted by the edison or something like that because I need an edison and a raspberry pi communicating with one another but I do not have a router. Thanks again!!
I do have another problem AlexT though. Using a different edison board, I tried to do the same thing, but for some reason, the dfu util program would not recognize it, but Device Manager was able to see only the one port( the one for serial connection). But what is really baffling is that if I use Putty, I can not connect to it , and there would only be a blank screen. Also, on the working board, there were two green lights lit on the big breakout board, but on this broken edison board, there is only one. Is there anything you would reccomend for me? Thankyou!