* Re: Boot from SD fail after 2013.02 [not found] <1366188021.710900767@f16.mail.ru> @ 2013-04-17 10:01 ` Sascha Hauer 2013-04-17 11:40 ` Re[2]: " Alexander Shiyan 0 siblings, 1 reply; 10+ messages in thread From: Sascha Hauer @ 2013-04-17 10:01 UTC (permalink / raw) To: Alexander Shiyan; +Cc: barebox On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > Hello. > > I found strange problem with boot from SD after 2013.02 release. > Using a git-bisect I found problem start point, so: > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > Author: Sascha Hauer <s.hauer@pengutronix.de> > Date: Fri Jan 25 23:39:20 2013 +0100 > > ARM: Setup stack at end of SDRAM > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > Exploring this commit does not helps me to have any idea how it > depends on SD-boot. > My target is ARM imx51 ConnectCore board. > Also I test it with freescale_mx51_babbage_defconfig since some > stuff is compatible with ConnectCore board. > Can anyone confirm this issue or have a solution? Without this patch applied, can you post the output of the 'iomem' command and confirm that the SDRAM size is detected correctly? 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: Boot from SD fail after 2013.02 2013-04-17 10:01 ` Boot from SD fail after 2013.02 Sascha Hauer @ 2013-04-17 11:40 ` Alexander Shiyan 2013-04-17 12:02 ` Sascha Hauer 0 siblings, 1 reply; 10+ messages in thread From: Alexander Shiyan @ 2013-04-17 11:40 UTC (permalink / raw) To: Sascha Hauer; +Cc: barebox > On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > > Hello. > > > > I found strange problem with boot from SD after 2013.02 release. > > Using a git-bisect I found problem start point, so: > > > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > > Author: Sascha Hauer <s.hauer@pengutronix.de> > > Date: Fri Jan 25 23:39:20 2013 +0100 > > > > ARM: Setup stack at end of SDRAM > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > Exploring this commit does not helps me to have any idea how it > > depends on SD-boot. > > My target is ARM imx51 ConnectCore board. > > Also I test it with freescale_mx51_babbage_defconfig since some > > stuff is compatible with ConnectCore board. > > Can anyone confirm this issue or have a solution? > > Without this patch applied, can you post the output of the 'iomem' > command and confirm that the SDRAM size is detected correctly? Memory size is correct, 256M. At this time I cannot run "iomem" since I am restore the faulty part as a result of my games. --- _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot from SD fail after 2013.02 2013-04-17 11:40 ` Re[2]: " Alexander Shiyan @ 2013-04-17 12:02 ` Sascha Hauer 2013-04-17 12:19 ` Re[2]: " Alexander Shiyan 0 siblings, 1 reply; 10+ messages in thread From: Sascha Hauer @ 2013-04-17 12:02 UTC (permalink / raw) To: Alexander Shiyan; +Cc: barebox On Wed, Apr 17, 2013 at 03:40:29PM +0400, Alexander Shiyan wrote: > > On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > > > Hello. > > > > > > I found strange problem with boot from SD after 2013.02 release. > > > Using a git-bisect I found problem start point, so: > > > > > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > > > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > > > Author: Sascha Hauer <s.hauer@pengutronix.de> > > > Date: Fri Jan 25 23:39:20 2013 +0100 > > > > > > ARM: Setup stack at end of SDRAM > > > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > > > > Exploring this commit does not helps me to have any idea how it > > > depends on SD-boot. > > > My target is ARM imx51 ConnectCore board. > > > Also I test it with freescale_mx51_babbage_defconfig since some > > > stuff is compatible with ConnectCore board. > > > Can anyone confirm this issue or have a solution? > > > > Without this patch applied, can you post the output of the 'iomem' > > command and confirm that the SDRAM size is detected correctly? > > Memory size is correct, 256M. At this time I cannot run "iomem" since > I am restore the faulty part as a result of my games. Does barebox still work 2nd stage or is this a 1st stage only problem? 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: Boot from SD fail after 2013.02 2013-04-17 12:02 ` Sascha Hauer @ 2013-04-17 12:19 ` Alexander Shiyan 2013-04-17 12:22 ` Sascha Hauer 0 siblings, 1 reply; 10+ messages in thread From: Alexander Shiyan @ 2013-04-17 12:19 UTC (permalink / raw) To: Sascha Hauer; +Cc: barebox > On Wed, Apr 17, 2013 at 03:40:29PM +0400, Alexander Shiyan wrote: > > > On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > > > > Hello. > > > > > > > > I found strange problem with boot from SD after 2013.02 release. > > > > Using a git-bisect I found problem start point, so: > > > > > > > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > > > > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > > > > Author: Sascha Hauer <s.hauer@pengutronix.de> > > > > Date: Fri Jan 25 23:39:20 2013 +0100 > > > > > > > > ARM: Setup stack at end of SDRAM > > > > > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > > > > > > > Exploring this commit does not helps me to have any idea how it > > > > depends on SD-boot. > > > > My target is ARM imx51 ConnectCore board. > > > > Also I test it with freescale_mx51_babbage_defconfig since some > > > > stuff is compatible with ConnectCore board. > > > > Can anyone confirm this issue or have a solution? > > > > > > Without this patch applied, can you post the output of the 'iomem' > > > command and confirm that the SDRAM size is detected correctly? > > > > Memory size is correct, 256M. At this time I cannot run "iomem" since > > I am restore the faulty part as a result of my games. > > Does barebox still work 2nd stage or is this a 1st stage only problem? PBL is not used in my config now and I think this is a lowlevel stuff because serial is not inited and I cannot see any message. I any case I cannot test more now due broken hardware. I return to test this after repair. Thanks! --- _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot from SD fail after 2013.02 2013-04-17 12:19 ` Re[2]: " Alexander Shiyan @ 2013-04-17 12:22 ` Sascha Hauer 2013-04-18 11:06 ` Re[2]: " Alexander Shiyan 0 siblings, 1 reply; 10+ messages in thread From: Sascha Hauer @ 2013-04-17 12:22 UTC (permalink / raw) To: Alexander Shiyan; +Cc: barebox On Wed, Apr 17, 2013 at 04:19:32PM +0400, Alexander Shiyan wrote: > > On Wed, Apr 17, 2013 at 03:40:29PM +0400, Alexander Shiyan wrote: > > > > On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > > > > > Hello. > > > > > > > > > > I found strange problem with boot from SD after 2013.02 release. > > > > > Using a git-bisect I found problem start point, so: > > > > > > > > > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > > > > > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > > > > > Author: Sascha Hauer <s.hauer@pengutronix.de> > > > > > Date: Fri Jan 25 23:39:20 2013 +0100 > > > > > > > > > > ARM: Setup stack at end of SDRAM > > > > > > > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > > > > > > > > > > Exploring this commit does not helps me to have any idea how it > > > > > depends on SD-boot. > > > > > My target is ARM imx51 ConnectCore board. > > > > > Also I test it with freescale_mx51_babbage_defconfig since some > > > > > stuff is compatible with ConnectCore board. > > > > > Can anyone confirm this issue or have a solution? > > > > > > > > Without this patch applied, can you post the output of the 'iomem' > > > > command and confirm that the SDRAM size is detected correctly? > > > > > > Memory size is correct, 256M. At this time I cannot run "iomem" since > > > I am restore the faulty part as a result of my games. > > > > Does barebox still work 2nd stage or is this a 1st stage only problem? > > PBL is not used in my config now and I think this is a lowlevel stuff > because serial is not inited and I cannot see any message. I was not asking about pbl, but only if you can start barebox from a running barebox. > I any case I cannot test more now due broken hardware. I return to > test this after repair. Thanks! ok. 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: Boot from SD fail after 2013.02 2013-04-17 12:22 ` Sascha Hauer @ 2013-04-18 11:06 ` Alexander Shiyan 2013-04-18 11:59 ` Sascha Hauer 0 siblings, 1 reply; 10+ messages in thread From: Alexander Shiyan @ 2013-04-18 11:06 UTC (permalink / raw) To: Sascha Hauer; +Cc: barebox > > > > > On Wed, Apr 17, 2013 at 12:40:21PM +0400, Alexander Shiyan wrote: > > > > > > Hello. > > > > > > > > > > > > I found strange problem with boot from SD after 2013.02 release. > > > > > > Using a git-bisect I found problem start point, so: > > > > > > > > > > > > 8e19ee94ab7aea50635845de31daef1b593e1205 is the first bad commit > > > > > > commit 8e19ee94ab7aea50635845de31daef1b593e1205 > > > > > > Author: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > Date: Fri Jan 25 23:39:20 2013 +0100 > > > > > > > > > > > > ARM: Setup stack at end of SDRAM > > > > > > > > > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> > > > > > > > > > > > > > > > > > > Exploring this commit does not helps me to have any idea how it > > > > > > depends on SD-boot. > > > > > > My target is ARM imx51 ConnectCore board. > > > > > > Also I test it with freescale_mx51_babbage_defconfig since some > > > > > > stuff is compatible with ConnectCore board. > > > > > > Can anyone confirm this issue or have a solution? > > > > > > > > > > Without this patch applied, can you post the output of the 'iomem' > > > > > command and confirm that the SDRAM size is detected correctly? > > > > > > > > Memory size is correct, 256M. At this time I cannot run "iomem" since > > > > I am restore the faulty part as a result of my games. > > > > > > Does barebox still work 2nd stage or is this a 1st stage only problem? > > > > PBL is not used in my config now and I think this is a lowlevel stuff > > because serial is not inited and I cannot see any message. > > I was not asking about pbl, but only if you can start barebox from a > running barebox. > > > I any case I cannot test more now due broken hardware. I return to > > test this after repair. Thanks! So. OK, I temporary patch my board and it working now. Please forget about correct memory size, it is not true. Size is incorrect. Both banks are enabled and size detected as 512M. I think this size is programmed by flash_header: { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, }, { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, }, After program NAND and start from NAND, size is still wrong... So, what we can do it this case for proper operation? Disable second bank? Define minimal size? Can you suggest a solution? barebox@ConnectCore i.MX51:/ iomem 0x00000000 - 0xffffffff (size 0x00000000) iomem 0x70004000 - 0x70004fff (size 0x00001000) imx-esdhc0 0x7000c000 - 0x7000cfff (size 0x00001000) imx21-uart2 0x70010000 - 0x70010fff (size 0x00001000) imx_spi0 0x70020000 - 0x70020fff (size 0x00001000) imx-esdhc2 0x73f84000 - 0x73f84fff (size 0x00001000) imx31-gpio0 0x73f88000 - 0x73f88fff (size 0x00001000) imx31-gpio1 0x73f8c000 - 0x73f8cfff (size 0x00001000) imx31-gpio2 0x73f90000 - 0x73f90fff (size 0x00001000) imx31-gpio3 0x73f98000 - 0x73f98fff (size 0x00001000) imx21-wdt0 0x73fa0000 - 0x73fa0fff (size 0x00001000) imx31-gpt0 0x73fa8000 - 0x73fa8fff (size 0x00001000) imx-iomuxv30 0x73fbc000 - 0x73fbcfff (size 0x00001000) imx21-uart0 0x73fc0000 - 0x73fc0fff (size 0x00001000) imx21-uart1 0x73fd4000 - 0x73fd4fff (size 0x00001000) imx51-ccm0 0x83f98000 - 0x83f98fff (size 0x00001000) imx_iim0 0x83fc4000 - 0x83fc4fff (size 0x00001000) i2c-fsl1 0x83fd9000 - 0x83fd9fff (size 0x00001000) imx51-esdctl0 0x83fdb000 - 0x83fdbfff (size 0x00001000) imx_nand0 0x90000000 - 0xafffffff (size 0x20000000) ram0 0x95ef8000 - 0x95efffff (size 0x00008000) stack 0x95f00000 - 0x97efffff (size 0x02000000) malloc space 0x97f02000 - 0x97f33c07 (size 0x00031c08) barebox 0x97f37df0 - 0x97f3e9df (size 0x00006bf0) bss 0xcfff0000 - 0xcfff0fff (size 0x00001000) imx_nand0 --- _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot from SD fail after 2013.02 2013-04-18 11:06 ` Re[2]: " Alexander Shiyan @ 2013-04-18 11:59 ` Sascha Hauer 2013-04-18 17:02 ` Re[2]: " Alexander Shiyan 0 siblings, 1 reply; 10+ messages in thread From: Sascha Hauer @ 2013-04-18 11:59 UTC (permalink / raw) To: Alexander Shiyan; +Cc: barebox On Thu, Apr 18, 2013 at 03:06:26PM +0400, Alexander Shiyan wrote: > > So. OK, I temporary patch my board and it working now. > Please forget about correct memory size, it is not true. > Size is incorrect. Both banks are enabled and size detected as 512M. > I think this size is programmed by flash_header: > { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, }, > { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, }, > > After program NAND and start from NAND, size is still wrong... > So, what we can do it this case for proper operation? Disable second bank? When writing the autodetection code I assumed that all boards correctly setup the SDRAM controller. Appearently I was wrong. I suggest disabling the second chip select since it's not used on your board. However, I begin doubting that it was the right decision to depend on ram size detection. 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: Boot from SD fail after 2013.02 2013-04-18 11:59 ` Sascha Hauer @ 2013-04-18 17:02 ` Alexander Shiyan 2013-04-18 18:23 ` Sascha Hauer 0 siblings, 1 reply; 10+ messages in thread From: Alexander Shiyan @ 2013-04-18 17:02 UTC (permalink / raw) To: Sascha Hauer; +Cc: barebox > On Thu, Apr 18, 2013 at 03:06:26PM +0400, Alexander Shiyan wrote: > > > > So. OK, I temporary patch my board and it working now. > > Please forget about correct memory size, it is not true. > > Size is incorrect. Both banks are enabled and size detected as 512M. > > I think this size is programmed by flash_header: > > { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, }, > > { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, }, > > > > After program NAND and start from NAND, size is still wrong... > > So, what we can do it this case for proper operation? Disable second bank? > > When writing the autodetection code I assumed that all boards correctly > setup the SDRAM controller. Appearently I was wrong. > > I suggest disabling the second chip select since it's not used on your > board. However, I begin doubting that it was the right decision to > depend on ram size detection. Yes, disabling second bank is helps. So, I repair my second board (same as first, but with real 512M of SDRAM). Works, but of course memory is fixed at 256M. Tomorrow I will test current 2013.04 on this board since probably problem appears only on 256M-version. Currently I think about return fixed table of memory in the board file or get memory size by testing memory. In both cases we need to disable ESDCTL module and now I do not know how make it better rather than simple remove this module from Makefile. Thanks. --- _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot from SD fail after 2013.02 2013-04-18 17:02 ` Re[2]: " Alexander Shiyan @ 2013-04-18 18:23 ` Sascha Hauer 2013-04-19 8:10 ` Re[2]: " Alexander Shiyan 0 siblings, 1 reply; 10+ messages in thread From: Sascha Hauer @ 2013-04-18 18:23 UTC (permalink / raw) To: Alexander Shiyan; +Cc: barebox On Thu, Apr 18, 2013 at 09:02:52PM +0400, Alexander Shiyan wrote: > > On Thu, Apr 18, 2013 at 03:06:26PM +0400, Alexander Shiyan wrote: > > > > > > So. OK, I temporary patch my board and it working now. > > > Please forget about correct memory size, it is not true. > > > Size is incorrect. Both banks are enabled and size detected as 512M. > > > I think this size is programmed by flash_header: > > > { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, }, > > > { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, }, > > > > > > After program NAND and start from NAND, size is still wrong... > > > So, what we can do it this case for proper operation? Disable second bank? > > > > When writing the autodetection code I assumed that all boards correctly > > setup the SDRAM controller. Appearently I was wrong. > > > > I suggest disabling the second chip select since it's not used on your > > board. However, I begin doubting that it was the right decision to > > depend on ram size detection. > > Yes, disabling second bank is helps. > So, I repair my second board (same as first, but with real 512M of SDRAM). > Works, but of course memory is fixed at 256M. Tomorrow I will test current > 2013.04 on this board since probably problem appears only on 256M-version. > Currently I think about return fixed table of memory in the board file or get > memory size by testing memory. In both cases we need to disable ESDCTL > module and now I do not know how make it better rather than simple remove > this module from Makefile. I wonder if it's possible to detect whether there actually is memory on the seconf bank. I remember trying it (probably on some other i.MX), but all I got was a locked up system when I tried to access non present SDRAM. 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: Boot from SD fail after 2013.02 2013-04-18 18:23 ` Sascha Hauer @ 2013-04-19 8:10 ` Alexander Shiyan 0 siblings, 0 replies; 10+ messages in thread From: Alexander Shiyan @ 2013-04-19 8:10 UTC (permalink / raw) To: Sascha Hauer; +Cc: barebox > > > On Thu, Apr 18, 2013 at 03:06:26PM +0400, Alexander Shiyan wrote: > > > > > > > > So. OK, I temporary patch my board and it working now. > > > > Please forget about correct memory size, it is not true. > > > > Size is incorrect. Both banks are enabled and size detected as 512M. > > > > I think this size is programmed by flash_header: > > > > { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, }, > > > > { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, }, > > > > > > > > After program NAND and start from NAND, size is still wrong... > > > > So, what we can do it this case for proper operation? Disable second bank? > > > > > > When writing the autodetection code I assumed that all boards correctly > > > setup the SDRAM controller. Appearently I was wrong. > > > > > > I suggest disabling the second chip select since it's not used on your > > > board. However, I begin doubting that it was the right decision to > > > depend on ram size detection. > > > > Yes, disabling second bank is helps. > > So, I repair my second board (same as first, but with real 512M of SDRAM). > > Works, but of course memory is fixed at 256M. Tomorrow I will test current > > 2013.04 on this board since probably problem appears only on 256M-version. > > Currently I think about return fixed table of memory in the board file or get > > memory size by testing memory. In both cases we need to disable ESDCTL > > module and now I do not know how make it better rather than simple remove > > this module from Makefile. > > I wonder if it's possible to detect whether there actually is memory on > the seconf bank. I remember trying it (probably on some other i.MX), but > all I got was a locked up system when I tried to access non present > SDRAM. OK, here is my today test case with 512M version of module. Barebox form current master tree. Boot from MMC. barebox 2013.04.0-00189-g59dbb4f #2 Fri Apr 19 11:35:57 MSK 2013 Board: ConnectCore i.MX51 detected i.MX51 revision 3.0 Module Variant: i.MX515@600MHz, Wireless, PHY, Ext. Eth, Accel (0x04) Module HW Rev : 04 Module Serial : W121789680 mc13xxx-spi mc13xxx-spi0: Found MC13892 ID: 0x0045d0 [Rev: 2.0a] nand: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit), page size: 2048, OOB size: 64 mdio_bus: miibus0: probed eth0: got preset MAC address: 04:03:47:42:5C:F0 smc911x smc911x1: LAN911x identified, idrev: 0x92210000, generation: 4 mdio_bus: miibus1: probed imx-usb imx-usb0: USB EHCI 1.00 malloc space: 0x95f02000 -> 0x97f01fff (size 32 MiB) imx-esdhc imx-esdhc0: registered as imx-esdhc0 imx-esdhc imx-esdhc2: registered as imx-esdhc2 envfs: wrong magic on /dev/env0 no valid environment found on /dev/env0. Using default environment running /env/bin/init... Hit any key to stop autoboot: 2 barebox@ConnectCore i.MX51:/ echo $bootsource mmc barebox@ConnectCore i.MX51:/ md 0x83fd9000-0x83fd9010 83fd9000: b2a20000 3f3584ab b2a20000 3f3584ab ......5?......5? barebox@ConnectCore i.MX51:/ iomem 0x00000000 - 0xffffffff (size 0x00000000) iomem 0x70004000 - 0x70004fff (size 0x00001000) imx-esdhc0 0x7000c000 - 0x7000cfff (size 0x00001000) imx21-uart2 0x70010000 - 0x70010fff (size 0x00001000) imx_spi0 0x70020000 - 0x70020fff (size 0x00001000) imx-esdhc2 0x73f80000 - 0x73f801ff (size 0x00000200) imx-usb0 0x73f80800 - 0x73f808ff (size 0x00000100) imx51-usb-misc0 0x73f84000 - 0x73f84fff (size 0x00001000) imx31-gpio0 0x73f88000 - 0x73f88fff (size 0x00001000) imx31-gpio1 0x73f8c000 - 0x73f8cfff (size 0x00001000) imx31-gpio2 0x73f90000 - 0x73f90fff (size 0x00001000) imx31-gpio3 0x73f98000 - 0x73f98fff (size 0x00001000) imx21-wdt0 0x73fa0000 - 0x73fa0fff (size 0x00001000) imx31-gpt0 0x73fa8000 - 0x73fa8fff (size 0x00001000) imx-iomuxv30 0x73fbc000 - 0x73fbcfff (size 0x00001000) imx21-uart0 0x73fc0000 - 0x73fc0fff (size 0x00001000) imx21-uart1 0x73fd4000 - 0x73fd4fff (size 0x00001000) imx51-ccm0 0x83f98000 - 0x83f98fff (size 0x00001000) imx_iim0 0x83fc4000 - 0x83fc4fff (size 0x00001000) i2c-fsl1 0x83fd9000 - 0x83fd9fff (size 0x00001000) imx51-esdctl0 0x83fdb000 - 0x83fdbfff (size 0x00001000) imx_nand0 0x83fec000 - 0x83fecfff (size 0x00001000) imx27-fec 0x90000000 - 0xafffffff (size 0x20000000) ram0 0x95f02000 - 0x97f01fff (size 0x02000000) malloc space 0x97f02000 - 0x97f40dac (size 0x0003edad) barebox 0x97f40dad - 0x97f4549f (size 0x000046f3) barebox data 0x97f454a0 - 0x97f4ab3f (size 0x000056a0) bss 0xafff4000 - 0xafff7fff (size 0x00004000) ttb 0xafff8000 - 0xafffffff (size 0x00008000) stack 0xce000000 - 0xce000fff (size 0x00001000) smc911x1 0xcfff0000 - 0xcfff0fff (size 0x00001000) imx_nand0 It looks mostly OK. 512M is readed from ESDCTL, since we directly program these registers from DCD data. Next, I program this binary into NAND and boot. The results is same except bootsource. Even dump ESDCTL registers have same data. So, for resolve my issue with module with 256M (or less) I should know how DCD data is programmed into ESDCTL when we boot from NAND. Early, I think this data is needs for other boot sources only. Is not it? Additionally, how we should get ram size properly from ESDCTL? AFAIK we not have any fuses for memory size (at least on mx51)... Fixme please. Thanks. --- _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-04-19 8:10 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1366188021.710900767@f16.mail.ru>
2013-04-17 10:01 ` Boot from SD fail after 2013.02 Sascha Hauer
2013-04-17 11:40 ` Re[2]: " Alexander Shiyan
2013-04-17 12:02 ` Sascha Hauer
2013-04-17 12:19 ` Re[2]: " Alexander Shiyan
2013-04-17 12:22 ` Sascha Hauer
2013-04-18 11:06 ` Re[2]: " Alexander Shiyan
2013-04-18 11:59 ` Sascha Hauer
2013-04-18 17:02 ` Re[2]: " Alexander Shiyan
2013-04-18 18:23 ` Sascha Hauer
2013-04-19 8:10 ` Re[2]: " Alexander Shiyan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox