Posts by mgsalinero

Pintus, for bare metal applications with IMX6 you have other open source boards like imx6rex
http://www.imx6rex.com/

http://www.imx6rex.com/I hope this help u

Hi, thanks for your response.

However, we don't use the Ubuntu SD card for production. We're using a buildroots and a yocto for 2 projects. But for the 3rd we use the SD card with ubuntu to check if we can use the board for it.

If you say that you cant provide that Ubuntu image I'll use a yocto full compilation.
Thx

Hi,

Since I had the ARMStone A9 board (before 2.0 kernel) I'm using the default SD card for testing and development.

However, when I installed Linux Kernel 2.1 release, I insert my SD card into the board and run it, it stop with the message "mountall event failed". It doesnt works. But, If I back to the older versión of Kernel, it works fine.

My main question is: Exists (in dl zone), any image of the default Ubuntu Linaro)? if not, How can I build a root fs like that Ubuntu? Do you have a defconfig like buildroots/yocto?

Thanks a lot
Have a nice day

Umm, I think I found the solution.

The problem was that I must have the kernel sources in the upper directory, but the name of the folder what contains the kernel sources must be "linux-fsimx6"

I still compilling... ill report

You can download the source files from download área. In Linux Fisrst Steps Documentation u can see how doit

Hi there,

Im having some problems when I try to compile Buildroots v2.1.

I'm using the standard buildroots configuration: fsimx6_std_defconfig

And when I do "make" it starts to compile the entire system. But, a few, minutes later an error stops the process:

I'm using Fedora virtual machine to compile this with the default crosscompile like Linux First Steps says.
I hope u can help.
Thanks a lot

Oook, I solved this. To run with UBI FS in 10AD processors with the lastes uBoot you need the lastest kernel too.

The problem was (NOTE 1) that I had using 1.2 FS kernel.

And, in NOTE 2, was that I didnt set bootargs correctly.

Hello,
I have an ARM Stone A9 and I'm trying to boot the standard filesystem. I did the following steps:

1) I downloaded the "rootfs_std-fsimx6-V2.0.ubifs" file from download area
2) In the device - mtdpartsarmStoneA9 # mtdparts

device nand0 <gpmi-nand>, # parts = 7
#: name size offset mask_flags
0: NBoot 0x00040000 0x00000000 1
1: UserDef 0x000c0000 0x00040000 0
2: Refresh 0x00040000 0x00100000 1
3: UBoot 0x000c0000 0x00140000 1
4: UBootEnv 0x00040000 0x00200000 1
5: Kernel 0x005c0000 0x00240000 1
6: TargetFS 0x07800000 0x00800000 0

active partition: nand0,0 - (NBoot) 0x00040000 @ 0x00000000

defaults:
mtdids : nand0=gpmi-nand
mtdparts: none

3) nand erase.part TargetFS

NAND erase.part: device 0 offset 0x800000, size 0x7800000
Skipping bad block at 0x00c80000
Skipping bad block at 0x01900000
Erasing at 0x7fe0000 -- 100% complete.
OK

4) Create UBI part: "ubi part TargetFS"

armStoneA9 # ubi part TargetFS
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: empty MTD device detected
UBI: create volume table (copy #1)
UBI: create volume table (copy #2)
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=6"
UBI: MTD device size: 120 MiB
UBI: number of good PEBs: 958
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 945
UBI: total number of reserved PEBs: 13
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 1/0

5) Create volume: "ubi create rootfs"

armStoneA9 # ubi create rootfs
No size specified -> Using max size (119992320)
Creating dynamic volume rootfs of size 119992320

6) Upload FS: 'tftp rootfs_std-fsimx6-V2.0.ubifs'

...
########################################
#################################################################
#################################################################
#
6 MiB/s
done
Bytes transferred = 57266176 (0x369d000)

7) Write to volume: 'ubi write $loadaddr rootfs $filesize'

Writing to volume rootfs ... OK, 57266176 bytes stored

Source: https://www.fs-net.de/assets/d…FSiMX6_FirstSteps_eng.pdf

Now, I set current bootargs:
1) run .rootfs_ubifs
2) run set_bootargs
3) Saveevn

The current "bootargs" are:
bootargs=console=ttymxc1,115200 login_tty=ttymxc1,115200 mtdparts=gpmi-nand:256k(NBoot)ro,768k(UserDef),256k(Refresh)ro,768k(UBoot)ro,256k(UBootEnv)ro,5888K(Kernel)ro,-(TargetFS) rootfstype=ubifs ubi.mtd=TargetFS root=ubi0:rootfs ro
bootcmd=run kernel; bootm

But, when i try to boot using "reset" (i.e.) I recive the following error message:

VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 256 mtdblock0 (driver?)
1f01 768 mtdblock1 (driver?)
1f02 256 mtdblock2 (driver?)
1f03 768 mtdblock3 (driver?)
1f04 256 mtdblock4
(driver?)
1f05 5888 mtdblock5 (driver?)
1f06 122880 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<8013252c>] (unwind_backtrace+0x0/0x13c) from [<806e7ad0>] (panic+0x74/0x19c)
[<806e7ad0>] (panic+0x74/0x19c) from [<80008d1c>] (mount_block_root+0x16c/0x220)
[<80008d1c>] (mount_block_root+0x16c/0x220) from [<80008f50>] (prepare_namespace+0x8c/0x184) ..........

What I could doing wrong? I'm sure that the solution is very simple, but I find it...

Thanks a lot
Best regards.

EDIT 1:
I found this UBI error in the log:
Creating 7 MTD partitions on "gpmi-nand":
0x000000000000-0x000000040000 : "NBoot"
0x000000040000-0x000000100000 : "UserDef"
0x000000100000-0x000000140000 : "Refresh"
0x000000140000-0x000000200000 : "UBoot"
0x000000200000-0x000000240000 : "UBootEnv"
0x000000240000-0x000000800000 : "Kernel"
0x000000800000-0x000008000000 : "TargetFS"
GPMI NAND driver registered. (IMX)
UBI: attaching mtd6 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: empty MTD device detected
UBI: max. sequence number: 0
UBI: create volume table (copy #1)
UBI error: ubi_scan_get_free_peb: no free eraseblocks
UBI error: ubi_init: cannot attach mtd6

NOTE 2:
I've updated to uImage_fsimx6.V2.0 (the default linux Kernel image from FS 2.0) and the log message (referred in NOTE 1) has changed:
7 cmdlinepart partitions found on MTD device gpmi-nand
Creating 7 MTD partitions on "gpmi-nand":
0x000000000000-0x000000040000 : "NBoot"
0x000000040000-0x000000100000 : "UserDef"
0x000000100000-0x000000140000 : "Refresh"
0x000000140000-0x000000200000 : "UBoot"
0x000000200000-0x000000240000 : "UBootEnv"
0x000000240000-0x000000800000 : "Kernel"
0x000000800000-0x000008000000 : "TargetFS"
GPMI NAND driver registered. (IMX)
UBI: attaching mtd6 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 492
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd6

Finaly I think how install NBoot and UBoot.
I still having the problem with NBoot binary file but I downloaded NBoot v7 binary file from download page.

0) I short circuited the Bootselect-Pin
1) Connect ARM Stone with serial debug console + MiniUSB-USB connector.
2) Powerup the ARM Stone board.
3) Run Mfg too
4) Wait for valid device message and I press "Start"

I see the NBoot menu on DCUTerm

4) Then I press "D" (uppercase - Shift + d) and DCUTermi shows "Wating for NBoot", then I go to File/Send binary file. I select the NBoot binary file.
5) When it finish I press "f" (lowercase)
6) Now I press "d" (lowercase) and I select the UBoot binary file in File/Send binary file.
7) I press again "f" (lowercase)
Power off the arm stone and remove the pin 66 and 65 connection.
9) Boot again the armstone.

¡¡¡¡UBoot menu is shown!!!!!!

Yes, dont forget save the variables. Thanks ThoPos.

Hello,
I have the same problem. I have an ARM Stone A9 starter kit.

I ve downloaded MfgTool_imx6q for quad led.
First of all, I recive this error:
Can't find the specified file, Please refer to the log file for detailed information.

In the log file:
ModuleID[2] LevelID[1]: Boot command-- file C:\Users\mgsalinero\Desktop\MfgTool_imx6q\Profiles\MX6Q Bootloader\OS Firmware\nbootIMX6Q_07.bin failed to open.errcode is 2

The problem is that the file in "\Profiles\MX6Q Bootloader\OS Firmware\nbootIMX6Q_07.bin" does not exists. OS Firmware directory contains a file named nbootIMX6Q_09. In this case I renamed the file and the application starts.

However I still failing when upload nboot. This is what I do:
0) I short circuited the Bootselect-Pin
1) Connect ARM Stone with serial debug console + MiniUSB-USB connector.
2) Powerup the ARM Stone board.
3) Run Mfg tool
4) Wait for valid device message and I press "Start"

I see this on DCUTermi:
F&S Nand Loader built Jan 31 2014, 10:08:16
ArmStone Rev 1.30
1024 MB RAM 0 MB FLASH 792 MHz

Please select action
'd' -> Serial download of bootloader
'u' -> USB download Eboot/UBoot
'E' -> Erase flash
'B' -> Show bad blocks
Use NetDCUUsbLoader for USB download

5) Then I press "d" in DCUTermi:
Into the console apears: "starting to download..."

6) Now I press over "File/Transmit binary file" in DCUTermi. I select the NBoot (the same that Mfg Tools brings - nbootIMX6Q_07)
#######################################################################file len=72116
'f' -> Save image to flash

7) Finally I press "f" to save to flash. But I receive the following message:
Unknown file type can NOT write in Nandflash

Im using "Mfg Tool_MultiPanel (Library: 2.1.1)". All downloaded from this document:
https://www.fs-net.de/assets/download/docu/common/en/i.MX6 NBoot Programming.pdf

The document screenshots are deprecated and does not explain correctly and fully all steps.

---------
EDIT:

I downloaded the nbootIMX6Q_07.bin file from the user download page and try again:

This time I received this message: "There is no data for download into Nandflash "

I hope u can help me.
Thanks a lot.

You should add that variable into uboot.

1) Connect PC & ARMStone with serial console.
2) Open a PC serial terminal (Teraterm for example) -> Configure it to open a connection with ARMStone using serial communicacion
3) Run ARMStone
4) Stop the linux kernel boot pressing a key. The uBoot prompt appears.
5) Add your bootargs.

LVSD Interface with sc card boot:
fec_mac=00:05:51:08:18:D2 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait rw video=mxcfb0:dev=lcd,LCD-ET070080,if=RGB666 console=ttymxc1,115200

Where:
fec_mac=00:05:51:08:18:D2 - Device mac (i think is optional)
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait rw - Boot mode (see quick start document)
video=mxcfb0:dev=lcd,LCD-ET070080,if=RGB666 - Video output mode
console=ttymxc1,115200 - Serial debug output console

* You can see the uBoot commands with "help"
* You can print all variables with "printenv"

You must add "video" atribute to "bootargs" variable on uBoot, for example:
video=mxcfb1:dev=lcd,CLAA-WVGA,if=RGB666

Hello,

I have an ARM Stone A9 Starter kit with the touch panel: "aSt-RGBKIT"

I plugged it with the adapter in the board, however, it doesn't work with the "defautl" configuration (Ubuntu). I try to recompile the linux kernel with "Atmel mXT I2C Touchscreen" Input device driver checked but the touch still doesn't working...

May be I need add another driver into the kernel?

Thanks.