Mehdi Souri | 5 Dec 09:06 2014

install debian pakage on ptxdistmini2440

i newer in ptxdist
i want to know can i use apt-get or ipkg to install *.deb ??

like gphotofs that is a debian pakage ???

Thanks alot

Mehdi Souri Chairman Of Board BineshCo.WebSite :
ravi kanth | 30 Nov 09:24 2014

Not able to build PTX tool


I am trying to build ptxdist tool from the sources. I downloaded them using the command "git clone git://" command. But as per the documentation, to do ./configure, I didn't find any 'configure' file in the directory. Request to please help on this issue.
Best Regards
ian c | 6 Dec 13:46 2014

enable hostap

Dear Experts,

I tried to setup an access point on a development board that runs with OSELAS. I enabled the hostap under
wpa_supplicant and tried to follow the steps for raspberry pi that I found on the internet.

for some reason, i could not find udhcpd.conf in /etc and also hostapd.conf. I believe the way of setting up
wifi access point using OSELAS is different from raspberry pi.

Anybody could help me how to setup the wifi access point?

Best regards,

Carlos Leyva Guerrero | 19 Nov 11:21 2014

Mini2440 - new flash chip - barebox update to last version

Dear Juergen and Sasha, 

I'have included you both given that you (Juergen) is the one working with the ptxdist version for the mini2440 and you (Sasha) are currently developing barebox.

Juergen is aware of a problem we have with the new mini2440 boards due to a change of the nand device because EOL of the previous part. Some adjustments need to be done to the nand controller to disallow partial programming because the new chip doesn't support it (and also have worse timings).

In any case, I am trying to solve it but also to update the barebox to its latest version (2014.11.0). I have already ported the env structure to the new format on barebox. When booting from nor (vivi) and then loading barebox on ram, I have no problems (beside the fact that I haven't implemented the new methods for barebox_update and have temporary solved it by including the update scripts from previous versions). However, when I try to load from the NAND nothing happens, no output in the serial port.

I'm trying to setup a arm debugger+opencd setup to see if I can find out what could be happening but for the time being, I don't have yet the required HW.

Surfing through the code in both releases (the one in last git respository for 2440, barebox 2011.05.0 and the last one available on barebox webpage (2014.11.0) I haven't found any major differences (that could cause this behaviour) besides one specific modification in lowlevel.S that replaces TEXT_BASE for TEXT_BASE - SZ_2M in the nand load routine. Do you now the reason for such a change?

Btw, i forgot to mention that I've also added the required modifications for proper management of 'big (>=128Mb) nands' using the patches from previous version as a base.

Can any of you provide some help regarding this issue? Specifically, have been there any attempts to update barebox to its last version for mini2440? Could any of you provide an inner point of view and some possible explanation for the impossibility to boot from nand?

Thanks in advance, 

Best regards, 

Carlos Leyva


ian c | 17 Nov 11:07 2014

BSP configuration for automount SD partition during boot-up

Hello Experts,

I have this partition on the SD card.
        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192       16383        4096   83  Linux
/dev/mmcblk0p2           16384     3162111     1572864   83  Linux
/dev/mmcblk0p3         3162112     3686399      262144   83  Linux

The /dev/mmcblk0p2 partition is the root partition while /dev/mmcblk0p3 is the spare partition.
Currently, I do manual mounting and formatting the spare partition and then added to fstab.

May I know how to configure the BSP so that the spare partition will automatically mount on first and onward
system boot-up?

Best REgards,


Carlos Leyva Guerrero | 11 Nov 12:37 2014

Problem with new nand flash

Dear Juergen and all, 

I am having problems with a new batch of mini2440 boards I have received from the manufacturer, the chip for NAND in this boards is K9K8G08U0E SCB0. I am able of writing data to the board (i.e. write the bootloader (busybox) and our linux image) but, as soon as i start using the board and filling up the space, more and more problems appear, making the boot time unusable (>10 mins) due to MTD error messages.

Previously, I have been working with boards with chips SAMSUNG 131 K9K8G08UOB PIB0 and K9K8G08OUOD SCB0 with no problem, same image, same bootloader. 

I have been able to locate a note regarding differences in the chips:

Are you aware of this situation? Have been it solved in latest OSELAS releases? If not, could you please give some guidance in the solution of this issue?

I'm stuck with old kernels because we could say the boards are in "production stage" so no big changes should be performed in order to avoid further problems and because in later kernel versions, as far as I remember, new issues arose as Sound not working.

Please let me know if any one can provide some light.

Best regards, 

Carlos Leyva


ian c | 10 Nov 15:34 2014

Upgrading OSELAS python package

Hi All,

The current python in OSELAS is python 2.6.6. I would like to run an application that requires python 2.7.6.
Therefore, I need to upgrade the version. I could not use the version 3.0 since it is unstable for that application.

Could anybody help me on this?

Thank you. 		 	   		  

mind entropy | 7 Nov 18:57 2014

On SDRAM BK76MAP value.


  I am developing a small BSP and I am trying to configure my SDRAM.

  In the barebox configuration of SDRAM the BK76MAP has the value of
001 i.e. 64MB/64MB  (;a=blob;f=arch/arm/boards/friendlyarm-mini2440/config.h;h=347930224e4cee893db77c9142c9550e828748dc;hb=784b352aeeed917f9cf75b3e8fc74aec12a48a01#l117
) see line 117.

   I have a K4S561632N SDRAM (
On the board I see 2 chips. I am assuming these are 2 banks. Should my
BK76MAP be 32MB/32MB? Also how do I get the SCAN parameter (9 bit
columns in the code)?


ian c | 30 Oct 07:46 2014

memory dump utility in Oselas

Dear Experts,

I developed an application to load multiple input xml files. I used linked list to manage these multiple
files. For some reason there is one xml files that eat large chunk of memories. I plan to dump the memory
allocated this xml file for debugging purposes. I am thinking to use dump command utility but I could not
find in Oselas.BSP menuconfig. Just wondering if the dump command is supported on Oselas.BSP. I would
appreciate if someone can point me where to enable this dump utility in menuconfig.

Best Regards,

Dave Festing | 18 Oct 11:21 2014

unable to locate package ipkg

Upgraded from Ubuntu 10.04LTS to Xubuntu 14.04LTS on both my desktop and

I can ptxdist go and ptxdist images on the Desktop but on the netbook,
withptxdist images, I get the following error:

davef <at> davef-AOD255E:~/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0$ ptxdist images
Creating ipkg index
Traceback (most recent call last):
line 7, in <module>
    import ipkg
ImportError: No module named ipkg
make: ***
Error 1

It doesn't seem to make any difference ticking or unticking ipkg in Disk and
File Utilities.  Before I completely re-install ptxdist is there an easier
fix to this problem?

Thank you,

G. B. | 13 Oct 03:08 2014

Stare and compare ... Opus 2

Let's see, Mini6410 and linux-3.14.19.

Thus spoke dmesg:

  ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
  ohci-platform: OHCI generic platform driver
  ohci-s3c2410: OHCI S3C2410 driver
  s3c2410-ohci s3c2410-ohci: OHCI Host Controller
  s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
  s3c2410-ohci s3c2410-ohci: irq 79, io mem 0x74300000
  s3c2410-ohci s3c2410-ohci: init err (00000000 0000)
  s3c2410-ohci s3c2410-ohci: can't start
  s3c2410-ohci s3c2410-ohci: startup error -75
  s3c2410-ohci s3c2410-ohci: USB bus 1 deregistered
  s3c2410-ohci: probe of s3c2410-ohci failed with error -75

Well ... <sigh> ... That's less than optimal.

So, where does this error come from?  Let's see ...


contained within:

   static int ohci_run (struct ohci_hcd *ohci)

around line 674:

   /* some OHCI implementations are finicky about how they init.
    * bogus values here mean not even enumeration could work.
   if ((ohci_readl (ohci, &ohci->regs->fminterval) & 0x3fff0000) == 0
           || !ohci_readl (ohci, &ohci->regs->periodicstart)) {
       if (!(ohci->flags & OHCI_QUIRK_INITRESET)) {
           ohci->flags |= OHCI_QUIRK_INITRESET;
           ohci_dbg (ohci, "enabling initreset quirk\n");
           goto retry;
       spin_unlock_irq (&ohci->lock);
       ohci_err (ohci, "init err (%08x %04x)\n",
           ohci_readl (ohci, &ohci->regs->fminterval),
           ohci_readl (ohci, &ohci->regs->periodicstart));
       return -EOVERFLOW;

So, the message:

   s3c2410-ohci s3c2410-ohci: init err (00000000 0000)

indicates both values:


appear to be zero.  Right.

What does that imply?  I don't know.  Having been chasing more than a 
couple CCF related issues, perhaps this is similar?  Perhaps not ...



it appears that it desires these two clocks:

   clk = devm_clk_get(&dev->dev, "usb-host");
   usb_clk = devm_clk_get(&dev->dev, "usb-bus-host");



corresponding entries are found:

   ALIAS(HCLK_UHOST, "s3c2410-ohci", "usb-host"),
   ALIAS(SCLK_UHOST, "s3c2410-ohci", "usb-bus-host"),

Yet, there are also entries for:

   GATE_BUS(HCLK_UHOST, "hclk_uhost", "hclk", HCLK_GATE, 29),
   GATE_BUS(HCLK_USB, "hclk_usb", "hclk", HCLK_GATE, 20),
   GATE_SCLK(SCLK_UHOST, "sclk_uhost", "dout_uhost", SCLK_GATE, 30),

Hmmm ... I don't think that's it.  Once again, I think I'm going in the 
wrong direction.

Time passes.  Yes.  Wrong direction.  Again.  Several of my experiments 
have ... well, let's just say that it has been interesting.  Clearly, 
I'm missing something.  Does anyone have some relevant insight they are 
willing to share?