From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1XwSJJ-0007UX-BV for ptxdist@pengutronix.de; Thu, 04 Dec 2014 10:02:57 +0100 Received: by mail-wi0-f169.google.com with SMTP id r20so35501617wiv.2 for ; Thu, 04 Dec 2014 01:02:48 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 4 Dec 2014 10:02:47 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: Re: [ptxdist] Compilation for ARM926ej-s --> S3c2451 Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Carlos Leyva Guerrero Cc: "ptxdist@pengutronix.de" 2014-12-03 18:00 GMT+01:00 Carlos Leyva Guerrero : [...] >>> If I provide you the patch and config file I did for the kernel 3.6, >>> would you mind testing if you are able to compile and boot with it? >> >> >> Sure, I can do that, but it will probably be 2-3 weeks before I can try >> it. I have some high priority stuff to take care off before that (this is >> also why I had to put my ongoing work on barebox in standby). >> >> I can also send you my kernelconfig and platformconfig files if you think >> this would be helpful. > > Please send them so I can run some additional checks, see diferences in > kernels that could explain the non-booting issue. Let me dig these (I want to make sure to send the correct files) and I will send them to you. [...] >> I will try this but I dont't think this will work. The NAND locking is not >> accidental -- it is done explicitly by superboot through the "tight lock" >> bit in the S3C2451 NAND controller. So I expect they would also do the same >> in USB mode. > > > I am in contact with the original manufacturer of the boards, and I have > talked with them several time about uboot, I will contact them and will ask > if they in fact block the nand in all modes. Please let me know if you get any feedback on this. >>> Remember to use a good quality mini-usb cables, If you have problems >>> detecting the board, messages like "data not accepted by the board", it is >>> due to bad quality wires. >>> >>> - You have to fuse the bootloader into the SD card or the nand, process >>> similar to the one used to get uboot working in our boards (there are boards >>> in china with uboot working with 2451, and there is some documentation from >>> samsung (I can provide it to you if you want). >>> >>> If first stage bootloader lock nand in any situation, there is no other >>> solution than using the SD fused bootloader option. >> >> >> Yes. This one will work for sure. Actually I am waiting for some boards >> with u-boot preloaded, this will help me proceed without worrying about >> superboot for the time being :) > > > This statement is the most surprising!. Pre-loaded uboot? can I ask which > provider will serve this boards to you (you can answer by private if you > can't share it openly)? I have identify other providers with same chip > (s3c2451) but different boards and unless USA FA distributor AAH ships the > boards with uboot, I have missed a new distributor!. Maybe I was too fast in my reply. The boards I am getting (from Boardcon) are not actually based on the s3c2451; they are based on the s3c2416 instead. However these are very similar (they even use the same chip ID) except for some extra onboard peripherals in the S3C2451. http://armbest.com/Tiny2451_CPU%20Compare.html Guillermo -- ptxdist mailing list ptxdist@pengutronix.de