mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: gianluca <gianlucarenzi@eurekelettronica.it>
Cc: barebox@lists.infradead.org
Subject: Re: New Board i.MX6 Dual Lite based
Date: Fri, 9 Jun 2017 09:32:16 +0200	[thread overview]
Message-ID: <20170609073216.qzamyscudr4gu333@pengutronix.de> (raw)
In-Reply-To: <8b1cafb3-8e87-8ce8-e4e1-42d28f82d1b0@eurekelettronica.it>

On Fri, Jun 09, 2017 at 09:25:56AM +0200, gianluca wrote:
> > > > 		
> > > > imx-esdhc 2194000.usdhc: registered as 2194000.usdhc
> > > > imx-esdhc 2198000.usdhc: registered as 2198000.usdhc
> > > > imx-esdhc 219c000.usdhc: registered as 219c000.usdhc
> > > > imx-ipuv3 2400000.ipu: IPUv3H probed
> > > > netconsole: registered as netconsole-1
> > > > malloc space: 0x2ff7b920 -> 0x4fef723f (size 511.5 MiB)
> > > > environment load /dev/env0: No such file or directory
> > > > Maybe you have to create the partition.
> > > > running /env/bin/init...
> > > > Running boot from uSD/MMC or USB...
> > > > mmc2: detected SD card version 2.0
> > > > mmc2: registered mmc2
> > > > ext4 ext40: EXT2 rev 1, inode_size 128
> > 
> > mmc2 is detected and registered because you are booting from it, but
> > mmc3 is not. Try 'detect mmc3' or 'detect -a' on the command line.
> > 
> 
> It was missing a mmc3.probe=1 in the init scripts. Now both are recognized
> correctly.

Try 'mount mmc3.0' without any further arguments. No need to probe
manually then.

Also my usual three words: Use bootloader spec. No need to write any
init or boot scripts then. barebox will just work without any further
configuration.

> 
> Now I am trying to extend the I2C Lines outside the board for a oscilloscope
> and/or a Saleae Logic Bus Analyzer. As soon as I find the solution or not I
> will keep you informed.
> 
> Anyway in the config there is both GPIO BASED I2C DRIVER and Platform iMX
> Driver. I tried to disable the GPIO Based but it does not work.

The GPIO I2C driver is only used when it's there's a GPIO I2C device
registered in the device tree.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2017-06-09  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 15:06 gianluca
2017-06-09  6:15 ` Sascha Hauer
2017-06-09  7:25   ` gianluca
2017-06-09  7:31     ` gianluca
2017-06-09  7:32     ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170609073216.qzamyscudr4gu333@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=gianlucarenzi@eurekelettronica.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox