Doug Abbott | 27 Feb 23:36 2015
Picon

Undefined symbols SOCK_NONBLOCK & SOCK_CLOEXEC

OK, so I tracked down the header files to 
sysroot-arm-v4t-linux-gnueabi/usr/include. sys/socket.h includes 
bits/socket.h, which in turn includes bits/socket_type.h, which does in 
fact declare SOCK_NONBLOCK and SOCK_CLOEXEC. So what am I missing here?

--

-- 
Doug Abbott
Principal Consultant, Intellimetrix
Linux for the Real World
575-590-2788

www.intellimetrix.us

Doug Abbott | 27 Feb 20:15 2015
Picon

Undefined symbols SOCK_NONBLOCK & SOCK_CLOEXEC

Still trying to build the Mini2440 BSP. ptxdist go fails trying to build 
udev-182/src/libudev-monitor.c saying the above symbols are undefined. 
I'm using the pre-built toolchain OSELAS.Toolchain-2014.12.0. Oddly, I 
find very few header files in that tree and I don't find sys/socket.h at 
all. Where is it getting the header files and why aren't those symbols 
declared?

Thanks, Doug

--

-- 
Doug Abbott
Principal Consultant, Intellimetrix
Linux for the Real World
575-590-2788

www.intellimetrix.us

Doug Abbott | 25 Feb 23:22 2015
Picon

Could not download package

I'm trying to build OSELAS.BSP-Pengutronix-Mini2440, but it stops trying to download libusb-1.0.18.tar.bz2 from sourceforge.net. It also tried to download the file from pengutronix.de and also failed. The file does appear to be at sourceforge but not in the same place that ptxdist is looking for it:
http://downloads.sourceforge.net/sourceforge/libusb/libusb-1.0.18.tar.bz2
Am I missing something?

Thanks, Doug -- Doug Abbott Principal Consultant, Intellimetrix Linux for the Real World 575-590-2788 www.intellimetrix.us
Juergen Borleis | 25 Feb 23:21 2015
Picon

Re: kernel driver building

Hi Richard,

Richard ORENGO wrote:
> Recently, have installed PTXDIST on a mini2440.
>
> Need to develop kernel driver. Is there a way to "make module" outside
> ptxdist environment ?

Sure. The kernel's buildsystem is prepared for this use case and PTXdist just 
make use it. The content of "Documentation/kbuild/modules.txt" should help 
you.

Regards
Juergen

Lappies | 25 Feb 22:47 2015
Picon
Picon

Kernel panic after electricity was away.

Hi Folks,

could someone point me please in thr right direction?

My mini2440 was up and running for 3 year no, without any problems.
This morning I waked up and my Alarm clock was blinking, so it mean the electricity was gone this night.

My mini2440 doesn´t start anymore, so I connected it to my Linuxbox and check with picocom what is going on.
It boot up, recognize the SDCARD and then Panic

TCP cubic registered
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-rtc s3c2410-rtc: setting system clock to 2015-02-25 21:25:32 UTC (1424899532)
Waiting for root device /dev/mmcblk0p3...
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz).
s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz).
s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz).
mmc0: new SDHC card at address 8c3b
mmcblk0: mmc0:8c3b SD04G 3.69 GiB (ro)
 mmcblk0: p1 p2 p3
Unable to handle kernel NULL pointer dereference at virtual address 0000016c
pgd = c0004000
[0000016c] *pgd=00000000
Internal error: Oops: 5 [#1]
last sysfs file:
Modules linked in:
CPU: 0    Not tainted  (2.6.39.1 #1)
pc : [<c00b139c>]    lr : [<c00b139c>]    psr: 60000013
sp : c3827e40  ip : c0308f24  fp : 00000083
r10: c02f7d68  r9 : c3826000  r8 : c34021c0
r7 : c3402380  r6 : c34021d0  r5 : 00000000  r4 : ffffffe2
r3 : 00000000  r2 : 00000000  r1 : c34023a4  r0 : c03bf0f8
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: c000717f  Table: 30004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc3826270)
Stack: (0xc3827e40 to 0xc3828000)
7e40: c3402254 c34023a4 00000003 c00b0758 c3827e5c c3407e80 00000000 00000003
7e60: c3827e78 c34021c0 00000083 c02f7d68 00008000 00000083 00000000 00000000
7e80: 00000000 c00b14f4 00008000 c02f7d68 c02f7d68 c008c4b0 00000000 c0124a2c
7ea0: c3938c00 c38077b8 00000000 000080d0 0000000a 0000000a c009fda0 00008000
7ec0: c3806780 c02f7d68 c02f7d68 00000000 c3938c00 c00de6a8 c00e00bc 00008000
7ee0: c3938c20 c008b55c c02f7d68 00008000 00008000 c3806780 c3938c20 c00a10b8
7f00: 00008000 c3938c20 00000000 c3938c00 c02f7d68 c00a1134 00008000 00008000
7f20: 00000020 00000000 c3938c20 c00a17e0 0000000a c00728cc 0000000a 00000000
7f40: c38060a0 c3401780 00000000 c3814000 c0286b73 00008000 c0286b73 00000000
7f60: 00000000 c00a18c8 00000000 00000600 00000004 00000000 c3938c20 c3938c00
7f80: 00000000 c3811000 c001d214 c3811000 00008000 c0008bd4 00000000 c02675dc
7fa0: 00000080 00200200 ffff16a0 c3811000 c02f4588 0b300003 c0286b73 c00237e4
7fc0: c001d224 c001d214 c00237e4 00000013 00000000 c0008f04 fffffffe 20000013
7fe0: ffffff9c c03097a0 c0008344 c0008440 00000000 c00237e4 00000000 08000000
Function entered at [<c00b139c>] from [<c00b14f4>]
Function entered at [<c00b14f4>] from [<c008c4b0>]
Function entered at [<c008c4b0>] from [<c00de6a8>]
Function entered at [<c00de6a8>] from [<c008b55c>]
Function entered at [<c008b55c>] from [<c00a10b8>]
Function entered at [<c00a10b8>] from [<c00a1134>]
Function entered at [<c00a1134>] from [<c00a17e0>]
Function entered at [<c00a17e0>] from [<c00a18c8>]
Function entered at [<c00a18c8>] from [<c0008bd4>]
Function entered at [<c0008bd4>] from [<c0008f04>]
Function entered at [<c0008f04>] from [<c0008440>]
Function entered at [<c0008440>] from [<c00237e4>]
Code: e3a01000 e1a00007 e5a01024 ebfe68ec (e595216c)
---[ end trace 747c9e3437494824 ]---
Kernel panic - not syncing: Attempted to kill init!
Function entered at [<c0027024>] from [<c02669f4>]

What is going wrong here.
I have check my Filesystem, boot  ext2 and root ext3.
Boot was Ok and root with a lot of errors.
Deleted my Partition, created them again, create filesystem, copy my Backup to the SDCARD and boot up again.
Still the same Error.

Like I said, the system is up ad running since 2011, so I forgot a lot of the stuff i did to set up everything.
In which direction must I start looking now?

Thx
Rudi
Richard ORENGO | 18 Feb 11:33 2015
Picon

kernel driver building

Hi,

Recently, have installed PTXDIST on a mini2440.

Need to develop kernel driver. Is there a way to “make module” outside ptxdist environment ?

 

Regards,

 

Richard

richard.orengo-GANU6spQydw@public.gmane.org

Guillermo Rodriguez Garcia | 24 Feb 11:01 2015
Picon

[mini2440] supervivi sets wrong RAM size for s3c2440

Hello all,

I have found a problem caused by the fact that (some variants of)
supervivi seem to configure the wrong RAM size in the s3c2440 SDRAM
controller. Specifically, BANKSIZE (0x4800002c) is configured as
0x00000032 (bank size = 128M), and BANK7 is enabled, so the total "RAM
size" is effectively set to 256M, which is the maximum size supported
by the CPU. However the board only has 64M RAM and uses BANK6 only.

When booting barebox as a second stage bootloader, Barebox will detect
it is running from RAM and will skip initialising the SDRAM controller
[1]. Also the board initialisation code will read the SDRAM registers
to find out how much memory is available [2] and pass this info to the
kernel via ATAGS [3].

The result: If you bring barebox in as a second stage bootloader from
supervivi, then flash the kernel and rootfs to NAND from barebox, and
then try to boot (without a power cycle), the kernel decompression
code will crash. Of course, if there is a power cycle inbetween,
barebox will then init the SDRAM controller properly and all will be
OK.

Question: Does it make sense to patch the mini2440 initialisation code
in [1] so that the SDRAM controller is always initialised, even if
running as a 2nd stage bootloader?

Guillermo

 [1]: http://git.pengutronix.de/?p=barebox.git;a=blob;f=arch/arm/boards/mini2440/lowlevel_init.S;h=41f50cbb450ac21368a1d0de0a86862b4af2e28a;hb=3e19d858760a138cb8cba92a2395036bd70937e3#l19
 [2]: http://git.pengutronix.de/?p=barebox.git;a=blob;f=arch/arm/boards/mini2440/mini2440.c;h=448aa40a0df4335e2db1dac1211d1512b9cce3b8;hb=3e19d858760a138cb8cba92a2395036bd70937e3#l238
 [3]: http://git.pengutronix.de/?p=barebox.git;a=blob;f=arch/arm/boards/mini2440/mini2440.c;h=448aa40a0df4335e2db1dac1211d1512b9cce3b8;hb=3e19d858760a138cb8cba92a2395036bd70937e3#l272

--

-- 
Guillermo Rodriguez Garcia
guille.rodriguez@...

mind entropy | 21 Feb 07:51 2015
Picon

On Flash access timings calculation.

Hi,
  I am trying to understand the flash access timing calculations in
the barebox code and I have some doubts. ( I am a newbie in NAND flash
).

In the code the comment says (in arch/arm/boards/friendlyarm-mini2440/config.h)

/*
 * Flash access timings
 * Tacls  = 0ns (but 20ns data setup time)
 * Twrph0 = 25ns (write) 35ns (read)
 * Twrph1 = 10ns (10ns data hold time)
 * Read cycle time = 50ns
 *
 * Assumed HCLK is 100MHz
 * Tacls = 1 (-> 20ns)
 * Twrph0 = 3 (-> 40ns)
 * Twrph1 = 1 (-> 20ns)
 * Cycle time = 80ns
 */

I have a K9F2G08U0B 256MB NAND flash(
http://115.28.165.193/down/datasheet/Peripheral/NandFlash/K9F2G08x0B.pdf
) . I know the HCLK cycle time is 10ns. (1/100MHz). Could you please
help me out with the calculation of Tacls,Twrph0 and Twph1? What are
the values/timing diagrams I should look in the NAND datasheet related
to this?

Thanks,
Gautam.

Oliver.Graute | 11 Feb 13:32 2015
Picon

Apache2 build fails after Toolchain update

Hello all.

after swicthing from OSELAS.Toolchain-2012.12.0 to OSELAS.Toolchain-2014.12.0 the apache2 build failed according to some linking errors regarding libaprutils and lcrypt.

Some idea what went wrong here? and how can I fix that?

/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/build/libtool --silent --mode=link arm-v5te-linux-gnueabi-gcc -g -O2 -D_REENTRANT -D_GNU_SOURCE -DAP_HAVE_DESIGNATED_INITIALIZER -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/include/apr-0 -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/include -I. -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/os/unix -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/server/mpm/prefork -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/modules/http -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/modules/filters -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/modules/proxy -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/include -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/modules/generators -I/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/modules/dav/main -export-dynamic -L/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib -o httxt2dbm httxt2dbm.lo /media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/srclib/pcre/libpcre.la /media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib/libaprutil-0.la -lexpat /media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib/libapr-0.la -lrt -lm -lcrypt -lnsl -lpthread -ldl
/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib/libaprutil-0.so: undefined reference to `crypt_r'
collect2: error: ld returned 1 exit status
make[3]: *** [httxt2dbm] Error 1
make[3]: *** Waiting for unfinished jobs....
/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib/libaprutil-0.so: undefined reference to `crypt_r'
collect2: error: ld returned 1 exit status
make[3]: *** [htdigest] Error 1
/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/sysroot-target/usr/lib/libaprutil-0.so: undefined reference to `crypt_r'
collect2: error: ld returned 1 exit status
make[3]: *** [ab] Error 1
make[3]: Leaving directory `/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/support'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64/support'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/build-target/httpd-2.0.64'
make: *** [/media/data/bsp/dnt8209ptxdist_new_toolchain/platform-dnt3202/state/apache2.compile] Error 2

Best regards,

Oliver

Attachment (smime.p7s): application/x-pkcs7-signature, 3263 bytes
Juergen Borleis | 31 Jan 11:04 2015
Picon

[ANNOUNCE] Mini2440: 2015.01.0 Release of the Free Board Support Package is now available

                   OSELAS.BSP-Pengutronix-Mini2440
                   -------------------------------

Long time no release...

Pengutronix offers the 2015.01.0 release of its Board Support Package for 
FriendlyARM's popular Mini2440.

It provides all required components to get this embedded target up and
running, and is dedicated for beginners in the embedded world. And for
experienced users it can act as a quick start for their own development
as well.

Please note:
------------

In contrast to previous releases there will be no more TAR archives for
downloading. Instead the GIT repository is where we publish the releases now.

Start with cloning the Mini2440 Board Support Package's repository:

$ git clone http://git-public.pengutronix.de/git-public/OSELAS.BSP-Pengutronix-Mini2440.git

and follow the embedded

  "documentation/OSELAS.BSP-Pengutronix-Mini2440-Quickstart.pdf"

document or start with the same document at:

"http://www.pengutronix.de/oselas/bsp/pengutronix/download/OSELAS.BSP-Pengutronix-Mini2440-Quickstart.pdf".

The intention of this release is not to provide new features, it's just to
provide a recent buildsystem instead, due to older PTXdist releases tend to
fail in more recent host systems and downloading packages from the internet if
the archives are moved or gone.

Updated Features:
-----------------

- PTXdist-2015.01.0
- OSELAS.Toolchain-2014.12.0
  - GCC 4.9.2
  - glibc 2.20
- Kernel 3.16, stable release 7
- Kernel 3.15, stable release 7
- Kernel 3.14, stable release 31
- Kernel 3.13, stable release 11
- Kernel 3.12, stable release 37
- Kernel 3.4, stable release 105
- Kernel 3.2, stable release 66
- kernel 3.0, stable release 101

Feature List:
-------------

- PTXdist based buildsystem for easy setup and build
- more than one predefined configuration
  - one without graphic, for headless usage
  - one with full blown Qt support including two examples how to use it
- recent GCC Toolchain (GCC 4.9.2, libc 2.20)
- Bootloader: 'Barebox' 2011.05.0
  Support for the following list of hardware components
  - serial console
  - network
  - SD card
  - NAND
- Kernel: Support for the following list of hardware components
  - serial console
  - network
  - sound (still broken in recent kernels)
  - LED
  - GPIO
  - AD converter
  - I2C master and I2C EEPROM
  - SPI master
  - Watchdog
  - Keypad
  - USB (host and device)
  - various LC displays (N35/A70/VGA shield/T35/X35/W35i/N43)
  - framebuffer
  - touch
  - SD card
  - NAND
  - Buzzer
- Comprehensive documentation how to prepare and build all software
  components and to deploy the Mini2440.

Please note
-----------

Some additional info can be found here:
http://www.oselas.org/oselas/bsp/pengutronix/index_en.html

Comments and contributions are welcome.

Enjoy!
Your Pengutronix Development Team

dhruv | 27 Jan 18:01 2015
Picon

Unable to launch Xorg

Hi All,
  Please help me with the below snippet error:

(==) Using config file: "/etc/X11/xorg.conf"
xf86TslibControlProc
xf86TslibControlProc
xinit: connection to X server lost

waiting for X server to shut down xf86TslibControlProc
xf86TslibControlProc
xf86TslibUninit
xf86TslibControlProc
(EE) Server terminated successfully (0). Closing log file.

Snippet of /var/log/xorg.conf:
[   137.017] (**) Option "Height" "320"               
[   137.018] (**) Option "Rotate" "0"                                   
[   137.038] (II) XINPUT: Adding extended input device "Touchpad0" (type:
TOUCHSCREEN, id 7)
[   137.038] xf86TslibControlProc                                 
[   137.039] (**) Touchpad0: (accel) keeping acceleration scheme 1
[   137.040] (**) Touchpad0: (accel) acceleration profile 0    
[   137.040] (**) Touchpad0: (accel) acceleration factor: 2.000     
[   137.041] (**) Touchpad0: (accel) acceleration threshold: 4         
[   137.041] xf86TslibControlProc                                      
[   137.101] xf86TslibControlProc                                      
[   137.124] xf86TslibControlProc                            
[   137.125] xf86TslibUninit                                
[   137.126] xf86TslibControlProc                                   
[   137.145] (II) UnloadModule: "tslib"                         
[   137.146] (II) UnloadModule: "kbd"                            
[   137.165] (EE) Server terminated successfully (0). Closing log file.

thanks Michael Olbrich from inputs wrt  "Re: [oselas] xorg problem on BSP 
201206 (w/micro2440) (was: Screen?stays dark AT070TN83 with pengutronix BSP 
2012.06)"

Thanks,
 Dhruv


Gmane