From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ve0-x233.google.com ([2607:f8b0:400c:c01::233]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1W19vG-0003jd-54 for barebox@lists.infradead.org; Thu, 09 Jan 2014 07:20:58 +0000 Received: by mail-ve0-f179.google.com with SMTP id jw12so2105028veb.38 for ; Wed, 08 Jan 2014 23:20:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20131219080917.GW24559@pengutronix.de> References: <20131212080359.GE24559@pengutronix.de> <20131212195806.GL24559@pengutronix.de> <20131219080917.GW24559@pengutronix.de> Date: Thu, 9 Jan 2014 02:20:33 -0500 Message-ID: From: Michael Burkey List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Porting barebox (devicetree) to Variscite iMX6 SOM To: Sascha Hauer Cc: barebox@lists.infradead.org A few more comments & questions regarding getting the Variscite SOM up and working (and it's pretty close to fully working at this point): First off, what works: 1) Booting from NAND, SD, etc to barebox 2) Nand programming under barebox 3) GPIO 4) I2C 5) USB 6) RS232 etc. Basically, things are working pretty well....up to the point of starting the Linux Kernel. Whenever I try to do a "bootm" of pretty much any image type, I run into issues. I *think* I have everything setup properly on the Linux command line in the way of bootargs (but I'm still checking a couple of things). It doesn't matter whether I am launching the kernel from a partition (NAND), USB, memory, etc. The result is the same regardless. It *does* decode the kernel header properly, display the version, the correct load address, etc -- so that's not the issue. One thing is that I am using an older kernel that is not setup for devicetree -- which is hopefully not a major problem. Basically, everything is specified "the old way" in the kernel platform/board files (and it works fine from u-boot). And, at least for now, moving to a newer kernel isn't an option. Under barebox, I either get a "launching kernel with devicetree" and then it hangs, or, if I do an "oftree -f" and then do a bootm, I get an "unable to dereference NULL pointer" and a restart. Any quick guesses, suggestions as to what I may be doing wrong? Is there a proper way to tell barebox (when started with devicetree) to NOT try to send the devicetree on to the kernel? Also, for the moment, I am using Kobs-NG under Linux to actually program barebox itself into NAND. Once there, it works fine and I can use barebox itself to program the other NAND partitions. Is adding support for writing out the FCB/DBBT to the first NAND blocks anywhere in the current (near-term) to do list for barebox? I noticed that it looked like you had something similar to this already in barebox for a couple of the other, earlier iMX cores. Lastly, once I do get this semi-final issue fixed, what is the best way to submit the code for the Variscite SOM to the main barebox tree for everyone else to have access to? Thanks again! Michael Burkey _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox