mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Allen Kennedy Jr." <allen@kennedystuff.com>
To: barebox@lists.infradead.org
Subject: Porting to a new board
Date: Wed, 18 Sep 2013 16:44:29 -0500	[thread overview]
Message-ID: <CAO-21LPB36R6Gk1RiWah8-pinu3rsKEcN-DgeQZkT65VNCDiEA@mail.gmail.com> (raw)

Hello,
  I have read the documentation but I believe it to be out of date, as it
does not match up with the source from the git tree.

  To that end, I am trying to add a new board, and I can not figure out how
to do so.  My board uses the mx27 processor, and so I am attempting to
closely mimic one of the other mx27 boards, when following the steps here:
http://barebox.org/documentation/barebox-2011.05.0/dev_board.html

I find the following inconsistencies:
1. include/configs/<boardname>.h  -
the configs directory does not exist.
2. modify arch/<architecture>/Kconfig

   - add your board (MACH_*) to the list
   - add your default text base address for this architecture
   (ARCH_TEXT_BASE)
   - add BOARDINFO with valueable info for your board

None of this exists.

3. modify arch/<architecture>/Makefile:

   - add board-$(MACH_*) = <your board_dir>


This does not exist

And my board will not show up in the menu config.

Also I am finding it difficult to locate where I set things like flash
size, ram size, etc...  u-boot has a much simpler (if not less documented)
layout when it came to boards.  Alas I can not use u-boot, because of the
nand flash limitations, and thus why I am attempting to use barebox.

And finally there seems to be some confusiton both in the code and the
documentation about the difference between a board and a machine.  What is
the difference?

I'm sorry that there is a lot here, but I can not find the proper
documentation to answer these questions.


Also, for those that are curious, or can help me get around this issue.  I
attempting to get this going on a board with an mx27 booted from NAND
flash, so I believe I have to use the PBL option to setup and copy out of
nand to do the real booting.  If there is any advice on this, I would
appreciate it.  I have no other bootloader, only bare metal and a JTAG
device.


thank you.

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

             reply	other threads:[~2013-09-18 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 21:44 Allen Kennedy Jr. [this message]
2013-09-19  7:35 ` Sascha Hauer
2013-09-20 21:02   ` Allen Kennedy Jr.
2013-09-21  7:50     ` Sascha Hauer
2013-09-23 21:47 Allen Kennedy Jr.
2013-09-24  4:24 ` Antony Pavlov
2013-09-24  7:39 ` Sascha Hauer
2013-09-24 15:00   ` Allen Kennedy Jr.
2013-09-24 16:33     ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 17:06       ` Allen Kennedy Jr.

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=CAO-21LPB36R6Gk1RiWah8-pinu3rsKEcN-DgeQZkT65VNCDiEA@mail.gmail.com \
    --to=allen@kennedystuff.com \
    --cc=barebox@lists.infradead.org \
    /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