[IMAGE] A13(-WIFI) Debian (now Ubuntu) + xfce flashable (Updated: 08 Mar: R18)

[jwischka]

Sorry - I've been out of town. Did you compile the kernel with the wifi driver as not-a-module?

[vinzer]

Hello,

I am sorry to hijack this thread but I have a very similar issue with my current build for A13.

I did lots of tries to build an image and I am completelly stucked at the message in terminal:

Unknown command 'watchdog' - try 'help'

My thread where I wrote all my steps in details is located here: https://www.olimex.com/forum/index.php?topic=2172

Please help with suggestion if you may be aware of this problem roots.

SlyCom - I found that you got a similar issue. Have you ever resolved it ?
Thank you.

[SlyCom]

Hi,

I compiled kernel with turned on watchdog also installed watchdog daemon. unfortunately it still sometimes  hangs at adding swap partition.

P.S.
jwischka, I have not tried yet Linario distribution because of lack of time. Maybe in next week.

[jduro]

Hello,

The R18 is running splendid in my A13-OLinuXino-WIFI and I have managed to connect to my wireless network which is allowing me to install all the necessary packages.

So first of all I want to thank jwischka and all others for all the hard work.

My question is related to the screen resolution.
Currently, the board is connected through the VGA connector to a 24'' TFT LCD monitor with a max. resolution of 1920 x 1080 @ 60 Hz.
The resolution at the moment is 800x600 and this is also the only option shown by xrandr.
Is there a way of increasing the screen resolution?
Would it be possible to select for instance 1024x768?

Regards.

[jwischka]

Hello,

The R18 is running splendid in my A13-OLinuXino-WIFI and I have managed to connect to my wireless network which is allowing me to install all the necessary packages.

So first of all I want to thank jwischka and all others for all the hard work.

My question is related to the screen resolution.
Currently, the board is connected through the VGA connector to a 24'' TFT LCD monitor with a max. resolution of 1920 x 1080 @ 60 Hz.
The resolution at the moment is 800x600 and this is also the only option shown by xrandr.
Is there a way of increasing the screen resolution?
Would it be possible to select for instance 1024x768?

Regards.

I believe Olimex has done some work on this - I think there are a couple of posts on their blog about it, actually. If you need help implementing those, let me know.

[tuso]

Hello,


I have an A13-Olinuxino Rev.E, I have tried to use jwischka's images but I can't boot them correctly.
I've tried the R18, R17 and R10 images and I've allways the same problem with the Kernel start freezing. I've no problem with the Olimex Debian image.

If I put the R18 files into the Olimex image partitions, ubuntu boot after many error messages. But I don't have sudo  and if I make a reboot, it won't boot again.

I don't know if I'm doing something wrong. I just DD the images into the uSD card. Could you advise me?



this the uart ouput with the R18:

U-Boot SPL 2012.10-04268-gf925eea-dirty (Jan 20 2013 - 15:46:58)                 
DRAM: 512MB                                                                       
SUNXI SD/MMC: 0


U-Boot 2012.10-04268-gf925eea-dirty (Jan 20 2013 - 15:46:58) Allwinner Technology

CPU:   SUNXI Family
Board: A13-OLinuXino
I2C:   ready
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
Loading file "uEnv.txt" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
Loading file "boot/uEnv.txt" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
Loading file "boot.scr" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
Loading file "boot/boot.scr" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
reading script.bin

27052 bytes read
reading uImage

3939888 bytes read
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.4.29-jwischka-3.4-video-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3939824 Bytes = 3.8 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

�� 6�Ў
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------

And this with the R10:

U-Boot SPL 2012.10-04274-g1b8e4ed-dirty (Jan 19 2013 - 12:21:00)
DRAM: 512MB
SUNXI SD/MMC: 0


U-Boot 2012.10-04274-g1b8e4ed-dirty (Jan 19 2013 - 12:21:00) Allwinner Technology

CPU:   SUNXI Family
Board: A13-OLinuXino
I2C:   ready
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
Loading file "uEnv.txt" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
Loading file "boot/uEnv.txt" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
Loading file "boot.scr" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
Loading file "boot/boot.scr" from mmc device 0:1
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
ext2load - load binary file from a Ext2 filesystem

Usage:
ext2load <interface> <dev[:part]> [addr] [filename] [bytes]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext2 filesystem
reading script.bin

27052 bytes read
reading uImage

3650120 bytes read
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.4.24-jwischka-3.4-video-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3650056 Bytes = 3.5 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

[JohnS]

Try an Olimex image.  If tht also doesn't work, maybe a bad SD card.

John

[tuso]

Hi JohnS,

I've no problem with the Olimex Debian image. It boots perfectly.

[JohnS]

Did you get the non-working ones as ZIP files?  If yes, some versions of unzip are broken on some Linux versions.  Try using 7z to unzip.

Otherwise I've no idea.

John

[Stephane80]

Hello,
I try to connect an arduino on the A13
but I have a problem
normally I should have a com port like "/dev/ttyACM0"
but on connect I just have this with dmesg:

[  224.260000] usb 2-1.3.3: USB disconnect, device number 7
[ 4630.480000] usb 2-1.3.3: new full-speed USB device number 8 using sw-ehci

and no "/dev/ttyACM*" com port
after many serch on the net
they seem to say to load the module cdc_acm
but

sudo modprobe cdc_acm

return:

FATAL: Module cdc_acm not found.

can you help me please
(tested with r18 )
thanks

[David Goadby]

It is not clear exactly what you are connecting to what. It seems that you are using serial ports to connect the two systems together. This should be an easy task.

There are two A13 serial ports UART0 and UART1) which operate at 3.3v TTL levels usually at a default rate of 115,200 baud. The Arduino Mega (the only one know) has four UARTS but they are 5V TTL not 3.3 and this is a potential problem. The Arduino Due, however, has four serial ports that are 3.3V TTL serial.

So, first sort out your hardware to make sure you are using the same levels else chips might fry! Then check the pin-outs to connect serial out-.in and in<-out to create the link. There are lots of 3.3v <-> 5v level shifters available if that is your problem.

If you are not just connecting the two boards using a TTL serial link then maybe you could expand on what you are actually trying to achieve so we can help you further.

David

[Stephane80]

Hello , thanks for your reply
No , sorry , I want to connect my arduino Mega to my A13
I want to connect it by the USB port
such as on a computer ,
it is for me to connect remotely by vnc to the A13 and program the Arduino

[David Goadby]

So you want the A13 USB port to act the same as a Windows USB port? IIRC it does this by looking like a USB serial bridge to the host. Maybe the serial chip is unknown to the kernel. Presumably this should create the device /dev/ttyACM0 . I think your kernel does not have the drivers for it.

Googling a bit it does seem that the ACM driver is often the cause of problems as it is used on various devices including mobile phones. The ACM is not just a simple serial device like the FTDI but has modem like controls as well.

I did find come source code here: https://gitorious.org/android_kernel_omap/android_kernel_omap/source/06676cfd3a5a946b96ad0b2d69d0a9d4bf88ce13:drivers/usb/class/cdc-acm.c and here:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/cmarinas/linux-aarch64/+/83a4eae9aeed4a69e89e323a105e653ae06e7c1f/drivers/usb/class/cdc-acm.c

As I have an Arduino mega I will try it myself - I like a challenge.

David

[Stephane80]

hello,
thank you for your help
In fact I was thinking of using the Arduino IDE on the A13 to program the arduino mega
like a ubuntu computer
I saw topics on the net about people who program arduino with a raspberry with Arduino IDE
I thought it was easier by USB but if there is other solution I'm interested

[Stephane80]

edit :
I found links like this one to do with the raspberry
for example
http://kll.engineering-news.org/kllfusion01/articles.php?article_id=30
But there were "/dev/ttyACM0" and they selects it in the Arduino IDE