Yocto Project - User contributions [en]

Yocto QEMU UNFS test procedure

2017-05-02T22:10:46Z

Juan Ramos: /* Steps to run the NFS test case for all qemu machines */

{{DISPLAYTITLE:Yocto QEMU UNFS test case procedure}}

==Steps to run the NFS test case for all qemu machines==

[[Prerequisites:]]

1. Have a clone of poky
<pre>$ git clone git://git.yoctoproject.org/poky</pre>

2. Checkout the correct hash.
<pre>$ git checkout and/or $ git log</pre>

3. Download the "kernel" file (<ZIMAGE>.bin) and the image compressed file (<IMAGE NAME>.tar.bz2) from autobilder link.

[[Steps:]]

1. Open a terminal and place in poky/ directory.
<pre>$ cd $PATH/poky</pre>

2. Source the environment:
<pre>$ source oe-init-build-env build</pre>
<pre>$ MACHINE=<MACHINE_TESTED> on conf/local.conf </pre>

4. Place the downloaded kernel (<ZIMAGE>.bin) and the <IMAGE NAME>.tar.bz2 file after "build" directory, something like "/home/<YOURUSER>/poky/build/tmp/deploy/images/qemu<MACHINE>/"

'''Note 1:''' First you need to create manually those directories in your system.
a) In poky directory create tmp directory (<code>~/poky/build$ mkdir tmp</code>); b) Then access to tpm (<code>$ cd tmp </code>); c) Create deploy directory (<code>$ mkdir deploy </code>); d) Access to deploy directory (<code>$ cd deploy </code>); e) Create images directory (<code>$ mkdir images </code>); f) Access to images directory (<code> $ cd images </code>); g) create your qemu folder, for example if you are testing qemux86 (<code>$ mkdir qemux86</code> ); h) Access your qemu folder, for instance to qemux86 directory (<code> $ cd qemux86 </code>)

'''Note 2:''' you can avoid to download and copy here the files and directly download in this path, typing in this path the following command:
<pre>$ wget /<WEB_ADRESS_OF_THE_KERNEL_IMAGE>/<ZIMAGE>.bin</pre>
<pre>$ wget /<WEB_ADRESS_OF_THE_IMAGE>/<IMAGE NAME>.tar.bz2 </pre>

5. Go to build directory:
<pre>$ cd /home/<YOURUSER>/poky/build</pre>

6. Extract the SDK, typing in a terminal the following command:
<pre>$ runqemu-extract-sdk tmp/deploy/images/qemux<MACHINE>/<IMAGE NAME>.tar.bz2 rootfs</pre>

'''Note 3:''' "rootfs" is referring to a directory going to be created, you can choose any name as you want.

'''Note 4:''' is it possible that the system will ask you to bitbake the system first. If so, then type in the terminal <code>$ bitbake meta-ide-support</code> (This process would take a while). Then type again in a terminal: <code>$ runqemu-extract-sdk tpm/deploy/images/qemux<MACHINE>/<IMAGE NAME>.tar.bz2 rootfs </code>

7. Start the qemu machine with NFS:
<pre>$ runqemu nfs tmp/deploy/images/qemux<MACHINE>/<ZIMAGE>.bin rootfs</pre>
qemu machine should be launch after this command.

'''Note 5:'''if you get the error:
================================================================================================================
Error: neither rpcbind nor portmap appear to be running
Please install and start one of these services first
================================================================================================================
for recent Ubuntu hosts, run:
sudo apt-get install rpcbind
Then add OPTIONS="-i -w" to /etc/default/rpcbind and run
sudo service portmap restart
and run again step 7.

8. Finally, from qemu open a terminal and type
<pre>$ poweroff</pre>
to exit.

Contributing to any of the yoctoproject.org repositories, including qa-tools, can be achieved with the [[Poky Contributions]] guidelines.

Firmware upgrade on Minnowmax with Dediprog 600

2016-11-30T22:31:48Z

Juan Ramos: Created page with "This tutorial explains how to upgrade firmware in a Minnowmax with Dediprog 600. You must have a Dediprog 600 with the USB cable interface needed to establish communication ..."

This tutorial explains how to upgrade firmware in a Minnowmax with Dediprog 600.

You must have a Dediprog 600 with the USB cable interface needed to establish communication between platform and PC.

[[File:Dediprog.jpg|center|600px]]

The connection to the platform is via the 8 pin connector cable inserted right here:

[[File:Minnow00.jpg|center|600px]]

Note the red line in the cable, this is the right way to connect the cable, oriented with the pin 1.

[[File:Minnow01.jpg|center|600px]]

You need to download the Dediprog 600 engineering software and drivers from:

http://www.dediprog.com/pd/spi-flash-solution/sf600

To install the software just need to go through the process:

[[File:00.jpg|center]]

[[File:01.jpg|center|]]

Now, for the driver installation, you need to download and unzip the files in a folder, go to Control Panel > Device manager and look for the unrecognized device (SF600-ISP):

[[File:03.jpg|center|700px]]

Right clic and update driver, set the path where you unzip the driver files and ok.

[[File:04.jpg|center|700px]]

Now get the latest BIOS file .

Open the Dediprog application, if everything was well configured a screen like this will open:

[[File:06.jpg|center|500px]]

Choose OK and a screen like this will open:

[[File:07.jpg|center|700px]]

From this screen select the button named "File" it will open a Open File window to find the BIOS file:

[[File:08.jpg|center|700px]]

And the next step is to press the "Batch" Button

[[File:09.jpg|center|700px]]

When the process finish, you will see a message like this:

[[File:10.jpg|center|700px]]

--[[User:Juan Ramos|Juan Ramos]] ([[User talk:Juan Ramos|talk]]) 14:31, 30 November 2016 (PST)

File:10.jpg

2016-11-30T22:05:43Z

Juan Ramos:

File:09.jpg

2016-11-30T22:04:55Z

Juan Ramos:

File:08.jpg

2016-11-30T22:03:32Z

Juan Ramos:

File:07.jpg

2016-11-30T22:02:17Z

Juan Ramos:

File:06.jpg

2016-11-30T22:01:19Z

Juan Ramos:

File:04.jpg

2016-11-30T21:50:51Z

Juan Ramos:

File:03.jpg

2016-11-30T21:48:37Z

Juan Ramos:

File:01.jpg

2016-11-30T21:47:37Z

Juan Ramos:

File:00.jpg

2016-11-30T21:47:00Z

Juan Ramos:

File:Minnow01.jpg

2016-11-30T20:01:37Z

Juan Ramos:

File:Minnow00.jpg

2016-11-30T19:57:12Z

Juan Ramos:

File:Dediprog.jpg

2016-11-30T19:54:23Z

Juan Ramos: Juan Ramos uploaded a new version of "File:Dediprog.jpg"

File:Dediprog.jpg

2016-11-30T19:51:45Z

Juan Ramos:

MinnowMax board Serial video connection guide

2016-10-31T18:03:35Z

Juan Ramos: /* To start screen for MinnnowBoard Max serial communication purposes */

=='''Two-Way Serial Communication with MinnnowBoard Max in Linux'''==

This tutorial explains how to set up two-way serial communication between a MinnnowBoard Max and
a host computer running a Linux operating system. These instructions are based upon Ubuntu Linux
and the serial terminal application ‘screen’, but other Linux environments and serial terminal
applications with comparable functionality are also available to perform the same tasks.

== Connection between Host and Target ==

[[File:Minnowmax serial connection.jpg]]

== Serial Cable to USB ==

1. You must have the appropriate USB 6 pin header cable to connect to the MinnowBoard Max. This
is a USB to 3.3V TTL Header. You can purchase on the web by searching for the following part
number: SS-TTL3VT . The cost is approximately $20 USD.

[[File:MMax Serial cable.jpg]]

== To install screen ==

2. With root user permissions run the Advanced Packaging Tool to download and install the screen by
running the following command from a terminal:

'''sudo apt-get install screen'''

[[File:Install screen.jpg]]

3. The 6 pin header on the MinnowBoard Max serves as the serial port output:

• '''Connect the other end (USB Type A ) to the USB port of your computer.'''

[[File:Conection mmax.jpg]]

• '''Note: Pin 1 of the Header is closest to the SATA connector. Pin 1 of the SS-TTL3VT cable is the Black lead wire.'''

[[File:Connection pin.jpg]]

If you are running Linux in a virtual machine be sure that the virtual machine USB connection
is active.

Run the dmseg command from a terminal to determine which tty is created (typically
ttyUSB0).

Look for the FT230x Basic UART.

Find the line that says '''FTDI USB Serial Device Converter now attached to ttyUSBX''',
where X is the assigned number.

[[File:Dmesg.jpg]]

== '''To start screen for MinnnowBoard Max serial communication purposes''' ==

1. Make sure to have root user permission and execute the command:
screen /dev/ttyUSBX 115200

2. Replace the X of USBX with the actual assigned tty number found during the previous step.
The 115200 indicates the baud rate for the serial data transfer.

[[File:Video serial.jpg]]

--[[User:Juan Ramos|Juan Ramos]] ([[User talk:Juan Ramos|talk]]) 11:03, 31 October 2016 (PDT)

MinnowMax board Serial video connection guide

2016-10-31T18:02:21Z

Juan Ramos: /* https://wiki.yoctoproject.org/wiki/skins/common/images/button_bold.pngTwo-Way Serial Communication with MinnnowBoard Max in Linux */

MinnowMax board Serial video connection guide

2016-10-31T18:01:14Z

Juan Ramos: Created page with "==https://wiki.yoctoproject.org/wiki/skins/common/images/button_bold.png'''Two-Way Serial Communication with MinnnowBoard Max in Linux'''== This tutorial explains how to s..."

==https://wiki.yoctoproject.org/wiki/skins/common/images/button_bold.png'''Two-Way Serial Communication with MinnnowBoard Max in Linux'''==

This tutorial explains how to set up two-way serial communication between a MinnnowBoard Max and
a host computer running a Linux operating system. These instructions are based upon Ubuntu Linux
and the serial terminal application ‘screen’, but other Linux environments and serial terminal
applications with comparable functionality are also available to perform the same tasks.

== Connection between Host and Target ==

[[File:Minnowmax serial connection.jpg]]

== Serial Cable to USB ==

1. You must have the appropriate USB 6 pin header cable to connect to the MinnowBoard Max. This
is a USB to 3.3V TTL Header. You can purchase on the web by searching for the following part
number: SS-TTL3VT . The cost is approximately $20 USD.

[[File:MMax Serial cable.jpg]]

== To install screen ==

2. With root user permissions run the Advanced Packaging Tool to download and install the screen by
running the following command from a terminal:

'''sudo apt-get install screen'''

[[File:Install screen.jpg]]

3. The 6 pin header on the MinnowBoard Max serves as the serial port output:

• '''Connect the other end (USB Type A ) to the USB port of your computer.'''

[[File:Conection mmax.jpg]]

• '''Note: Pin 1 of the Header is closest to the SATA connector. Pin 1 of the SS-TTL3VT cable is the Black lead wire.'''

[[File:Connection pin.jpg]]

If you are running Linux in a virtual machine be sure that the virtual machine USB connection
is active.

Run the dmseg command from a terminal to determine which tty is created (typically
ttyUSB0).

Look for the FT230x Basic UART.

Find the line that says '''FTDI USB Serial Device Converter now attached to ttyUSBX''',
where X is the assigned number.

[[File:Dmesg.jpg]]

== '''To start screen for MinnnowBoard Max serial communication purposes''' ==

1. Make sure to have root user permission and execute the command:
screen /dev/ttyUSBX 115200

2. Replace the X of USBX with the actual assigned tty number found during the previous step.
The 115200 indicates the baud rate for the serial data transfer.

[[File:Video serial.jpg]]

File:Video serial.jpg

2016-10-31T17:37:07Z

Juan Ramos:

File:Dmesg.jpg

2016-10-31T17:35:46Z

Juan Ramos:

File:Connection pin.jpg

2016-10-31T17:31:19Z

Juan Ramos:

File:Conection mmax.jpg

2016-10-31T17:26:16Z

Juan Ramos:

File:Install screen.jpg

2016-10-31T17:25:23Z

Juan Ramos:

File:MMax Serial cable.jpg

2016-10-31T17:18:09Z

Juan Ramos:

File:Minnowmax serial connection.jpg

2016-10-31T17:16:00Z

Juan Ramos:

Yocto QEMU UNFS test procedure

2016-10-21T18:55:58Z

Juan Ramos: /* Steps to run the NFS test case for all qemu machines */

{{DISPLAYTITLE:Yocto QEMU UNFS test case procedure}}

==Steps to run the NFS test case for all qemu machines==

[[Prerequisites:]]

1. Have a clone of poky
<pre>$ git clone git://git.yoctoproject.org/poky</pre>

2. Checkout the correct hash.
<pre>$ git checkout and/or $ git log</pre>

3. Download the "kernel" file (<ZIMAGE>.bin) and the image compressed file (<IMAGE NAME>.tar.bz2) from autobilder link.

[[Steps:]]

1. Open a terminal and place in poky/ directory.
<pre>$ cd $PATH/poky</pre>

2. Source the environment:
<pre>$ source oe-init-build-env build</pre>
<pre>$ MACHINE=<MACHINE_TESTED> on conf/local.conf </pre>

4. Place the downloaded kernel (<ZIMAGE>.bin) and the <IMAGE NAME>.tar.bz2 file after "build" directory, something like "/home/<YOURUSER>/poky/build/tmp/deploy/images/qemu<MACHINE>/"

'''Note 1:''' First you need to create manually those directories in your system.
a) In poky directory create tmp directory (<code>~/poky/build$ mkdir tmp</code>); b) Then access to tpm (<code>$ cd tmp </code>); c) Create deploy directory (<code>$ mkdir deploy </code>); d) Access to deploy directory (<code>$ cd deploy </code>); e) Create images directory (<code>$ mkdir images </code>); f) Access to images directory (<code> $ cd images </code>); g) create your qemu folder, for example if you are testing qemux86 (<code>$ mkdir qemux86</code> ); h) Access your qemu folder, for instance to qemux86 directory (<code> $ cd qemux86 </code>)

'''Note 2:''' you can avoid to download and copy here the files and directly download in this path, typing in this path the following command:
<pre>$ wget /<WEB_ADRESS_OF_THE_KERNEL_IMAGE>/<ZIMAGE>.bin</pre>
<pre>$ wget /<WEB_ADRESS_OF_THE_IMAGE>/<IMAGE NAME>.tar.bz2 </pre>

5. Go to build directory:
<pre>$ cd /home/<YOURUSER>/poky/build</pre>

6. Extract the SDK, typing in a terminal the following command:
<pre>$ runqemu-extract-sdk tpm/deploy/images/qemux<MACHINE>/<IMAGE NAME>.tar.bz2 rootfs</pre>

'''Note 3:''' "rootfs" is referring to a directory going to be created, you can choose any name as you want.

'''Note 4:''' is it possible that the system will ask you to bitbake the system first. If so, then type in the terminal <code>$ bitbake meta-ide-support</code> (This process would take a while). Then type again in a terminal: <code>$ runqemu-extract-sdk tpm/deploy/images/qemux<MACHINE>/<IMAGE NAME>.tar.bz2 rootfs </code>

7. Start the qemu machine with NFS:
<pre>$ runqemu nfs tmp/deploy/images/qemux<MACHINE>/<ZIMAGE>.bin rootfs</pre>
qemu machine should be launch after this command.

'''Note 5:'''if you get the error:
================================================================================================================
Error: neither rpcbind nor portmap appear to be running
Please install and start one of these services first
================================================================================================================
for recent Ubuntu hosts, run:
sudo apt-get install rpcbind
Then add OPTIONS="-i -w" to /etc/default/rpcbind and run
sudo service portmap restart
and run again step 7.

8. Finally, from qemu open a terminal and type
<pre>$ poweroff</pre>
to exit.

Contributing to any of the yoctoproject.org repositories, including qa-tools, can be achieved with the [[Poky Contributions]] guidelines.