All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hoefle Marco <Marco.Hoefle@nanotronic.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot device model SPI + SPI Flash
Date: Tue, 27 Oct 2015 12:52:20 +0000	[thread overview]
Message-ID: <abbc0aee3dfc4f61a3cde3daeb3b555c@LysExc01.nanotronic.local> (raw)
In-Reply-To: <562F61EA.5080303@xilinx.com>

Ok renaming it worked and I could extract the petalinux bsp. Thanks for the hint.
The dts I found is very similar to the one we use successfully in the mainline Linux Kernel. There SPI + SPI Flash are working.

However, I think (please correct me if I am wrong) the petalinux u-boot config does not use driver model + dts.
I think the previous method does not work anymore in mainline u-boot as the spi driver has already been ported.
If I do not use these defines:
# define CONFIG_DM
# define CONFIG_DM_SPI
# define CONFIG_OF_SPI

I'l get a compilation error.
So I think it would be a good change to test the u-boot driver model with the Xilinx SPI driver. I am happy to play the guinea pic ;-)

I think currently it is something with the u-boot dts parsing as none of the functions provided by xilinx_spi.c are called.
I attached the currently used u-boot configuration + u-boot dts.





> -----Original Message-----
> From: Michal Simek [mailto:michal.simek at xilinx.com]
> Sent: Dienstag, 27. Oktober 2015 12:37
> To: Hoefle Marco <Marco.Hoefle@nanotronic.ch>; Michal Simek
> <michal.simek@xilinx.com>; Jagan Teki <jteki@openedev.com>
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] u-boot device model SPI + SPI Flash
> 
> On 10/27/2015 12:12 PM, Hoefle Marco wrote:
> >
> >
> >> -----Original Message-----
> >> From: Michal Simek [mailto:michal.simek at xilinx.com]
> >> Sent: Montag, 26. Oktober 2015 14:52
> >> To: Jagan Teki <jteki@openedev.com>; Hoefle Marco
> >> <Marco.Hoefle@nanotronic.ch>; Michal Simek
> <michal.simek@xilinx.com>
> >> Cc: u-boot at lists.denx.de
> >> Subject: Re: [U-Boot] u-boot device model SPI + SPI Flash
> >>
> >> On 10/23/2015 12:20 PM, Jagan Teki wrote:
> >>> On 23 October 2015 at 15:42, Hoefle Marco
> >>> <Marco.Hoefle@nanotronic.ch>
> >> wrote:
> >>>> Maybe somebody has a valid u-boot dts file for a microblaze system
> >>>> with
> >> an SPI core? That would helpful.
> >>>> We want to move from a parallel nor flash to a SPI flash for FPGA
> >>>> config,
> >> u-boot, Linux Kernel and rootfs.
> >>>> The last missing part is u-boot. The kernel dts file is ok and the
> >>>> mtd
> >> partitions are set up correctly.
> >>>
> >>> I even grepped on linux/arch/microblaze couldn't get much info, So
> >>> added Michal he well aware of this may be he can help.
> >>
> >>
> >>
> http://www.xilinx.com/support/download/index.html/content/xilinx/en/d
> >> o wnloadNav/embedded-design-tools/2015-2.html
> >>
> >> ac701 bsp and I expect also Kc705.
> >
> > I downloaded the AC701 bsp file but it is not a valid archive. Do I need to
> use  (and learn how to use) the 3 GB pertalinux tools to build u-boot for
> Microblaze?
> > The u-boot config for the AC701 and the dts file would probably sufficient.
> 
> it is tar.gz just rename it.
> 
> Thanks,
> Michal
 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: microblaze-generic.h
Type: text/x-chdr
Size: 11862 bytes
Desc: microblaze-generic.h
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151027/0ae46e01/attachment.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: microblaze-generic_defconfig
Type: application/octet-stream
Size: 218 bytes
Desc: microblaze-generic_defconfig
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151027/0ae46e01/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: microblaze-generic.dts
Type: audio/vnd.dts
Size: 1288 bytes
Desc: microblaze-generic.dts
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151027/0ae46e01/attachment.bin>

  reply	other threads:[~2015-10-27 12:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 10:55 [U-Boot] u-boot device model SPI + SPI Flash Hoefle Marco
2015-10-21 16:28 ` Jagan Teki
2015-10-21 16:40   ` Hoefle Marco
2015-10-21 16:45     ` Jagan Teki
2015-10-22  6:16       ` Hoefle Marco
2015-10-23 10:12         ` Hoefle Marco
2015-10-23 10:20           ` Jagan Teki
2015-10-26 13:51             ` Michal Simek
2015-10-27 11:12               ` Hoefle Marco
2015-10-27 11:37                 ` Michal Simek
2015-10-27 12:52                   ` Hoefle Marco [this message]
2015-10-27 14:50                     ` Michal Simek
2015-10-27 15:03                       ` Hoefle Marco
2015-10-29  8:22                         ` Michal Simek
2015-11-03  9:08                           ` Hoefle Marco
2015-11-04 12:04                             ` Michal Simek
2015-11-05 14:40                               ` Hoefle Marco
2015-11-05 15:18                                 ` Michal Simek
2015-11-17 10:17                                   ` Hoefle Marco
2015-11-17 10:23                                     ` Michal Simek
2015-11-17 10:30                                       ` Hoefle Marco

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=abbc0aee3dfc4f61a3cde3daeb3b555c@LysExc01.nanotronic.local \
    --to=marco.hoefle@nanotronic.ch \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.