Arduino YUN Kernel version wrong

Official Hardware Classic Yún
1

Hello everyone

I had a new arduino YUN, it is using in lab .
When I use it to connect Wi-Fi, I found it can not working normally.
I try to upload YunSerialTreminal and restart, at the Serial Monitor show some message, I had attached the file.
The message show "Linux version 3.18.23 (admin@compile-01-prod) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r48749) ) #34 Tue May 10 08:20:13 UTC 2016" and "nonblocking pool is initialized".

I try to push "YUN RST" bottom over 30sec to reset to factory setting, it can not work.
And I can not find it from Wi-Fi (Not show linino-XXXXXXXXXXX).
It seems that the update is mistaken for the version, making the system crashed.

How to do it can make the system work properly ?

524C8.txt (16.9 KB)

2

wesleylai:
I try to push "YUN RST" bottom over 30sec to reset to factory setting, it can not work.

That reset button only works once Linux has fully booted up. Your board is failing the boot process, so it never gets to the point where it looks for the button press. That button won't help you with the current situation.

It seems that the update is mistaken for the version, making the system crashed.

You must have left something out of your post - what update? What have you done to your Yun since the last time it booted up properly?

Did you install the 1.6.2 system update using the instructions on THIS PAGE? If so, that is almost certainly the problem. There is a paragraph in bold print down at the bottom of that page:

Note: if you applied the Web Panel or Command Line procedure to an original Yún board - not the new 2016 products - the device won't boot because it has an incompatilbe u-boot image. You can still recover your device and you have two options: go back to its original image following this Image Restore procedure and keep your original warranty status or void your warranty and upgrade the bootloader following the bootloader update procedure.

The fact that your bootup messages show an Oct 2015 date and mention Linino (an older version of the system software) is a pretty strong argument that you do not have one of the recent 2016 build boards. Besides the system software, you must also upgrade the uboot bootloader image. You should be able to get your board booting properly again if you follow the complete procedure on this page: Reflashing the OpenWrt-Yun image on the Yún

It's unfortunate that the warning about incompatible uboot images has been moved down to the bottom of the page. When the 1.6.2 image first came out, the warnings were right at the top of the page, and they didn't have a cryptic description like "2016 boards" it explicitly warned that this was a problem with upgrading from 1.5.3 or earlier. Then, the page and the 1.6.2 image was taken down for a while, and now that they are available once again, the warning has been moved to the end of the page where it may not be noticed until it's too late. Most unfortunate.

3

Hi ShapeShifter,

Thank you for your reply.

But I think I had some information not clear description.

The dead YUN, I can not find it from Wi-Fi or LAN, it means I can not find IP of YUN.
So I can not update the U-boot, kernel...etc.

You provide the message is need using IP, based on the information of up description, I cannot update.

4

Read it again carefully - you are using the USB port to connect to the Yun and issue commands. At the point where it talks about the Yun's IP address, you are assigning it an unused address, not typing in an existing address. You don't need an existing Ethernet connection, you are manually setting one up from scratch.

5

ShapeShifter:
That reset button only works once Linux has fully booted up. Your board is failing the boot process, so it never gets to the point where it looks for the button press. That button won't help you with the current situation.

You must have left something out of your post - what update? What have you done to your Yun since the last time it booted up properly?

Did you install the 1.6.2 system update using the instructions on THIS PAGE? If so, that is almost certainly the problem. There is a paragraph in bold print down at the bottom of that page:
The fact that your bootup messages show an Oct 2015 date and mention Linino (an older version of the system software) is a pretty strong argument that you do not have one of the recent 2016 build boards. Besides the system software, you must also upgrade the uboot bootloader image. You should be able to get your board booting properly again if you follow the complete procedure on this page: Reflashing the OpenWrt-Yun image on the Yún

It's unfortunate that the warning about incompatible uboot images has been moved down to the bottom of the page. When the 1.6.2 image first came out, the warnings were right at the top of the page, and they didn't have a cryptic description like "2016 boards" it explicitly warned that this was a problem with upgrading from 1.5.3 or earlier. Then, the page and the 1.6.2 image was taken down for a while, and now that they are available once again, the warning has been moved to the end of the page where it may not be noticed until it's too late. Most unfortunate.

Hi,
and is Yun 1.6.2 working with Uboot contained in 1.5.3 ? For me not.
Is somewhere working uboot version and bootargs (if defaults dont work) for download ?
I figured out if i use uboot from arduino.org and system image from here then its working but wifi. Backed to 1.5.3 exactly followed that tutorials here and still no luck to get full working 1.6.2

thanx

6

Hi,

I have the same problem (I think) :
I have an old yun board (2014) and last week I tried to upgrade my 1.5.3 to 1.6.2, following theslowly and with attention the official instructions.
All steps were OK, and the last message also OK :

Writing from to firmware ...
Upgrade completed
Rebooting system...

But as other people, the Linux never reboot, and no way to get a log or message with serial port.
I successfully send the YunSerialTerminal to the 32U4 and when I press 2 time on the 32US RST button, red led is flashing ... (the program is ok for the 32U4 side).

For use, I tried to Reflash the boot, but the console never respond anything (I tried with the arduino soft and with picocom... result is the same).
I tried to

(Posted by ShapeShifter)

Besides the system software, you must also upgrade the uboot bootloader image. You should be able to get your board booting properly again if you follow the complete procedure on this page: Reflashing the OpenWrt-Yun image on the Yún

I agree, but in this case, that can't work, because we can't process to the step :

In the Serial Monitor, type
tftp 0x80060000 openwrt-ar71xx-generic-linino-u-boot.bin;
and press Enter.

and the YUN RST button and WIFI RST button don't change anything (I thinh it is because the bootloarder is dead or have a bad address...). :frowning:

Is it the same for other people ?

How to find solution to get back the 1.5.3 for old Yun hard version? (before 2016) ?

:slight_smile:
Thank you and hopping all old yun will come back alive again !

7

lopic34:
I successfully send the YunSerialTerminal to the 32U4 and when I press 2 time on the 32US RST button, red led is flashing ... (the program is ok for the 32U4 side).

Why do you say that the red LED flashing means that the program on the 32U4 side is good? Doing the double reset just puts you in the 32U4 bootloader. That red flash means the 32U4 bootloader is working, but it doesn't imply anything about the sketch that may be loaded.

But as other people, the Linux never reboot, and no way to get a log or message with serial port.

If you aren't getting anything at all, I suspect it is something in the way you are doing things. For example, pressing the 32U4 reset button at any time during this process is unnecessary, and will likely cause you problems. For this procedure, don't touch the 32U4 reset button at any time.

The issue may be that unlike most other Arduino boards, the USB serial interface between the Yun and your computer is handled directly by the 32U4 processor, not by a separate translator chip. That means that every time you hit the reset button, you are re-initializing the USB serial port - as far as your computer goes, it's as if you unplug and replug the Yun each time. If you have the serial monitor or other terminal program running and open, when you press the 32U4 reset button you are essentially ripping the Yun's serial port out from under the terminal program, and then plugging in a new port. The connection that the terminal program had with the Yun is gone, and you won't be able to send or receive anything. On my computer, whenever I press the 32U4 button, I need to close my terminal program and re-open it before I can talk to the Yun again.

Follow the procedure again, step by step, and don't add any steps like pressing a reset button. Load the YunSerialTerminal example, open the Serial Monitor, and then press only the YUN RST button (the one closest to the the SD card slot.) At that point, you should start to see the boot messages from the Yun, and you should be able to follow the rest of the procedure.

8

Hi and thank you for your explanation,

Why do you say that the red LED flashing means that the program on the 32U4 side is good? Doing the double reset just puts you in the 32U4 bootloader. That red flash means the 32U4 bootloader is working, but it doesn't imply anything about the sketch that may be loaded.

OK, good to know, thank you.

Follow the procedure again, step by step, and don't add any steps like pressing a reset button. Load the YunSerialTerminal example, open the Serial Monitor, and then press only the YUN RST button (the one closest to the the SD card slot.) At that point, you should start to see the boot messages from the Yun, and you should be able to follow the rest of the procedure.

I did it again, step by step, but the boot message never appear.

I think that the same problem than this one:
http://forum.arduino.cc/index.php?topic=430473.0

Hoping we will find a solution. :slight_smile:

9

Also, for information :

you should start to see the boot messages from the Yun, and you should be able to follow the rest of the procedure.

When I followed the same steps before the 1.6.2 upgrade, the boot message appeared, but not not... :confused: