[U-Boot] MXC: Performance issue/glitch with reading/writing files from SD card
Hi, Looks like there is a huge performance issue with the sdhc hardware/software driver on the mx31 Earlier on i had adapated the freescale mx sdhc driver and ported it to the mx31 platform for U-boot v1.0. I have modified the driver to put the host as well as the card in 4 bit mode in the initialization sequence. Inspite of that doing a fatload for a file of size of the order of 16MB takes about 10 minutes, which is nowhere near the theoretical speed even in 1 bit mode. I have seen the scope trace(s) and looks like multiple Data pins are being used for data, but seems like it takes forever, Could anyone give me quick clues as to what could be the issue? I haven't done any measure on the linux side yet using dd. Thanks in advance, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] SD high capacity support
Hi all, Has any one written a u-boot sdhc driver which supports high-capcity cards ? I am trying to implement a SD high capacity driver but looks like you need to implement the protocol (SD CMDs ) a bit differently. Based on the specs i am not sure if my changes will be backward compatible to run a regular SD card. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] eSDHC driver on mxc
Hi all, I have basically adapted the linux esdhc driver for the mx35 for uboot. I am using the mmc_init routine in fsl_esdhc driver for the initialization sequence including the IDentification cycle for the card. The issue is that i have a particular card from vendor Kingston which works rock solid withput any problems and after hooking the driver with the FAT32 infrstructure in uboot, i can use file api' just fine on it. But a card from another vendor behaves in a peculiar way. Ifi soft reset my initialization sequence just runs fine and the card is succesfully identified( OCR, voltage validation and RCA get identified succesfully). But out of a hard reset, the card fails initialzation and mmc_init retrurn error. Even while using it in linux, there are occasional issues with the uninitialization/initialization cycle as the initialaztion fails every alternate time. I had the same card working on the mx27 platform using the same approach of porting the linux driver over to uboot(the only difference being this is a polled version rather thatn interrupts and DMA). Please let me know if it could be the issue out of a hard rest with the eSDHC(enhance host controller) misbehaving for this particular card. Adding delay before the Card/host reset/init sequence does not help. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] i2c on mx27
Hi, Has anyone tried playing with the hardware i2c on the mx27 platform using u-boot. I am trying to enable the second controller and use hardware i2c by doing memory writes to the appropiate registers using mw. Looks like i am missing out on some register values. I am unable to toggle the signals on the I2C2_CLK and I2C2_data lines. I have modifed the mux registers and the pad registers and the Clock gating registers appropiately. Any hints? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 3/7] fec_imx27: driver for FEC ethernet controller on i.MX27
On Mon, Nov 16, 2009 at 8:59 PM, Ben Warren biggerbadder...@gmail.com wrote: Hi Alfred, alfred steele wrote: Thanks for your submission! What is the current design on the mxc fec interface's attainment of a MAC address. From the kernel driver it looks like it looks at the IIM(IC identification registers) on the MXC platform(like mx51/35) to look for a programmed mac address and then the set the fec mac to the same . Looks like with the current mxc_fec driver there is not support for the same. I am thinking of a mechanism to hardcode a fake MAC which would subsequently be picked up by the kernel without using the bd_info structure. Any comments/suggestions? -Alfred. I don't know much about this driver, but it appears to be doing things incorrectly. The correct flow is as follows. It is documented in 'doc/README.enetaddr': 1. The driver's initialize() function read from NVRAM if available. MAC address is stuffed into dev-enetaddr. The initialize() function should not try to get the address from the environment, which is where the imx27 driver goes wrong. 2. After all drivers have been initialized, eth_initialize() ( in net/eth.c) reads from the environment. If the value in the environment is valid and the value in dev-enetaddr is valid and both are different, the user is warned. The value in the environment overwrites the value in dev-enetaddr 3. When a network operation is performed, the driver's init() function is called, which is where the address is programmed into the device. As you can see, if the device is never used, step 3 is never exected and the device is never programmed. This is how it's supposed to work, since the U-boot design philosophy dictates that hardware is never touched unless it is used in U-boot. I'm pretty sure hard-coding a fake MAC address would run afoul of this rule. Is there a way to pass the information to kernel using either the dev-enetaddr without programming the IIM module register. Would i have to use bd_info structure or can we do without it.? This problem is specific to the mx27 i guess. -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 3/7] fec_imx27: driver for FEC ethernet controller on i.MX27
Thanks for your submission! What is the current design on the mxc fec interface's attainment of a MAC address. From the kernel driver it looks like it looks at the IIM(IC identification registers) on the MXC platform(like mx51/35) to look for a programmed mac address and then the set the fec mac to the same . Looks like with the current mxc_fec driver there is not support for the same. I am thinking of a mechanism to hardcode a fake MAC which would subsequently be picked up by the kernel without using the bd_info structure. Any comments/suggestions? -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Freescale MXC: NAND UnCorrectable RS-ECC Error
Hi Magnus, Thanks. Are you using U-boot v2 or some other customized U-boot? (gitweb at git.denx.de seems to have some problems at the moment and I don't have the U-boot v2 tree locally) Custom u-boot based on v2. I have ported mxc_nand based on the kernel code(2.6.26) and it uses 2k/4k specific changes and the correct settings for RCSR register based on the page size. -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running u-boot without relocation to RAM?
So is it possible to completly disable the relocation process at startup and run U-Boot with having opcode in PROM and data in RAM? If yes, how could I achieve this? I already tried to remove the corresponding code in the start.S and searched the README for switches, but without success. Did you try the CONFIG_SKIP_RELOCATE_UBOOT ? I am not sure if it serves your purpose here. It depends upon whether or not your start.S uses it at all. -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Debugging NAND boot with BDI3000 on U-boot
Hi, I am a rookie as far as NAND boot debugging is concerned. I have remote gdb working just fine. I wish to single step from the point the macro for nand load starts(assembly code). (nand_load). To do that, i set a instruction breakpoint on BDI3000 using the BI command. looks like the cpu entered debug mode but i get a GDB: read data abort ignored on the BDI command line interface. I am not familiar with that message. Here's a snapshot of what i am getting: TARGET: Reset sequence passed TARGET: resetting target passed TARGET: processing target startup TARGET: processing target startup passed GDB: read data abort ignored Myboardinfo Core number : 0 Core state: debug mode (ARM) Debug entry cause : Vector Catch (PREFETCH ABORT Current PC: 0x598524fc Current CPSR : 0x01d3 (Supervisor) Myboardti Core number : 0 Core state: debug mode (ARM) Debug entry cause : Debug Request Current PC: 0x1001ffcc Current CPSR : 0x01d7 (Abort) Are there any cheat sheets available for NAND boot debugging with U-boot? Thanks in advance for your help! -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Freescale MXC: NAND UnCorrectable RS-ECC Error
Hi All,
I am trying to introduce a Samsung NAND flash part (K9F8G08U0M) to a
Freescale mxc platform. Looks like the device code used in the NAND
read id operation is already a part of the
drivers/mtd/nand/nand_ids.c, looking at line {NAND 1GiB 3,3V 8-bit,
0xD3, 0, 1024, 0, LP_OPTIONS},) Its different in the sense that it
has a page size of 4K but the code specific to 4k page size handling
seems to be there in the code
After booting out of RAM, i am getting UnCorrectable RS-ECC Error
during an initial page read operation.
Am i missing something related to spare area/OOB.
Please let me know the fastest path to or get around or debug this issue.
NAND: UnCorrectable RS-ECC Error
Bad block table found at page 262080, version 0x01
UnCorrectable RS-ECC Error
UnCorrectable RS-ECC Error
Bad block table found at page 262016, version 0x01
UnCorrectable RS-ECC Error
UnCorrectable RS-ECC Error
nand_read_bbt: Bad block at 0x1e08
nand_read_bbt: Bad block at 0x1e0c
nand_read_bbt: Bad block at 0x1e30
nand_read_bbt: Bad block at 0x1e34
nand_read_bbt: Bad block at 0x2334
nand_read_bbt: Bad block at 0x3694
nand_read_bbt: Bad block at 0x3698
nand_read_bbt: Bad block at 0x369c
nand_read_bbt: Bad block at 0x36a0
nand_read_bbt: Bad block at 0x3ad0
nand_read_bbt: Bad block at 0x3ad4
nand_read_bbt: Bad block at 0x3ad8
nand_read_bbt: Bad block at 0x3f70
nand_read_bbt: Bad block at 0x3f74
nand_read_bbt: Bad block at 0x3f80
nand_read_bbt: Bad block at 0x3f84
nand_read_bbt: Bad block at 0x3f88
nand_read_bbt: Bad block at 0x3f90
nand_read_bbt: Bad block at 0x3f9c
nand_read_bbt: Bad block at 0x3fa4
nand_read_bbt: Bad block at 0x3fa8
nand_read_bbt: Bad block at 0x3fac
nand_read_bbt: Bad block at 0x3fb0
nand_read_bbt: Bad block at 0x3fb4
nand_read_bbt: Bad block at 0x3fb8
nand_read_bbt: Bad block at 0x3fc4
nand_read_bbt: Bad block at 0x3fc8
nand_read_bbt: Bad block at 0x3fd0
nand_read_bbt: Bad block at 0x3fd4
nand_read_bbt: Bad block at 0x3fe8
nand_read_bbt: Bad block at 0x3ff0
nand_read_bbt: Bad block at 0x3ff4
nand_read_bbt: Bad block at 0x3ff8
nand_read_bbt: Bad block at 0x3ffc
1024 MiB
My gdb backtrace if it helps at all:
(gdb) bt
#0 mxc_nand_ecc_status (mtd=value optimized out) at mxc_nand.c:272
#1 0x87f0bfb0 in mxc_nand_command (mtd=0x87f29c90, command=0,
column=0, page_addr=0) at mxc_nand.c:924
#2 0x87f08dd0 in nand_do_read_ops (mtd=0x87f29c90, from=value
optimized out, ops=0x87f29e18) at nand_base.c:1197
#3 0x87f09a64 in nand_read (mtd=0x1000, from=13310103653403,
len=2280692324, retlen=0x87e5fef4, buf=0x87e627b8 '�' repeats 200
times...) at nand_base.c:1319
#4 0x87f13d18 in readenv (offset=262144, buf=0x87e627b8 '�' repeats
200 times...) at u-boot/include/nand.h:41
#5 0x87f13d88 in env_relocate_spec () at env_nand.c:349
#6 0x87f13b58 in env_relocate () at env_common.c:264
#7 0x87f01874 in start_armboot () at board.c:357
#8 0x8c18 in ?? ()
Thanks,
Alfred
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Freescale MXC: NAND UnCorrectable RS-ECC Error
Thanks Magnus! Which MXC platform are you using and does it support 4K page size? And does mxc_nand.c support 4K page size? I am using mx35 and the NAND flash controller therein supports 4K page operations as evident from the manual. from the code in mxc_nand.c it looks like it checks for whether or not its a 4K page NAND and assigns a different OOB layout based on that. I am not sure as i havent gathered a full understanding of the ECC/OOB mechanism. How do we define the functions owned by the mxc_nand.c(board specific driver) and the generic driver nand_base.c or is it a layered design? Can you please elaborate on it? -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] NAND UnCorrectable RS-ECC Error on Freescale MXC
Hi All,
I am trying to introduce a Samsung NAND flash part (K9F8G08U0M) to a
Freescale mxc platform. Looks like the device code used in the NAND
read id operation is already a part of the
drivers/mtd/nand/nand_ids.c, looking at line {NAND 1GiB 3,3V 8-bit,
0xD3, 0, 1024, 0, LP_OPTIONS},) Its different in the sense that it
has a page size of 4K but the code specific to 4k page size handling
seems to be there in the code
After booting out of RAM, i am getting UnCorrectable RS-ECC Error
during an initial page read operation.
NAND: UnCorrectable RS-ECC Error
Bad block table found at page 262080, version 0x01
UnCorrectable RS-ECC Error
UnCorrectable RS-ECC Error
Bad block table found at page 262016, version 0x01
UnCorrectable RS-ECC Error
UnCorrectable RS-ECC Error
nand_read_bbt: Bad block at 0x1e08
nand_read_bbt: Bad block at 0x1e0c
nand_read_bbt: Bad block at 0x1e30
nand_read_bbt: Bad block at 0x1e34
nand_read_bbt: Bad block at 0x2334
nand_read_bbt: Bad block at 0x3694
nand_read_bbt: Bad block at 0x3698
nand_read_bbt: Bad block at 0x369c
nand_read_bbt: Bad block at 0x36a0
nand_read_bbt: Bad block at 0x3ad0
nand_read_bbt: Bad block at 0x3ad4
nand_read_bbt: Bad block at 0x3ad8
nand_read_bbt: Bad block at 0x3f70
nand_read_bbt: Bad block at 0x3f74
nand_read_bbt: Bad block at 0x3f80
nand_read_bbt: Bad block at 0x3f84
nand_read_bbt: Bad block at 0x3f88
nand_read_bbt: Bad block at 0x3f90
nand_read_bbt: Bad block at 0x3f9c
nand_read_bbt: Bad block at 0x3fa4
nand_read_bbt: Bad block at 0x3fa8
nand_read_bbt: Bad block at 0x3fac
nand_read_bbt: Bad block at 0x3fb0
nand_read_bbt: Bad block at 0x3fb4
nand_read_bbt: Bad block at 0x3fb8
nand_read_bbt: Bad block at 0x3fc4
nand_read_bbt: Bad block at 0x3fc8
nand_read_bbt: Bad block at 0x3fd0
nand_read_bbt: Bad block at 0x3fd4
nand_read_bbt: Bad block at 0x3fe8
nand_read_bbt: Bad block at 0x3ff0
nand_read_bbt: Bad block at 0x3ff4
nand_read_bbt: Bad block at 0x3ff8
nand_read_bbt: Bad block at 0x3ffc
1024 MiB
Please let me know the fastest path to get around or debug this issue.
Thanks,
Alfred
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot -Modifying boot sequence on a ARM based board
Hi all, What is the general boot sequence for u-boot. IIRC, its the cpu specific start followed by board specfic stuff, then general init stuff (like misc_init_f) and then the common stuff. The reason i am asking this i want to inject my own boot path based on the presence of certain boot peripherals. I want to override the boot_args with my custom-defined bootargs and then execute bootm from a predefined RAM address. I want to know which is the most appropriate place for soing this. I was initilally thinking it would end up in the board specific code(board/boardname.c) but i am a bit confused when i read the main/common code. Please let me your recommendations on this. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Customize U-boot
Hi, I am trying to modify uboot to use the available FAT32 APIs and the mmc driver apis in order to auto magically boot from a SD card if its present in the slot of our board. I know it can be done by statically defining EXTRA_ENVS in the board config file and use the U-boot scripting framwork to do so. But i do not intend to use just the scripts to acheive that. The reason is we need to modify the config everytime the initramdisk and kernel image size changes. i am trying to do it using U-boot api's available like the way U-boot api's are used in common/update.c to boot from mmc/sd only if the card is available, otherwise boot from NAND. Another question here is whether the flash_api like flash_write/ flash_erase only make sense for NOR flash. Are there any similar API's available for the NAND subsystem. Thanks in advance for your help. -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] DDR initialization
Hi all, How do i go about the SDRAM/DDR initialization on my board. IS the function partitoned or is it just done in a single place. I would think that board specifc dram_init is just a generic function. There has to be a specific place where the SDRAM controller is told about the DRR/SDRAM. Is the porting documented somewhere or are there any good example to follow to stick to U-boot conventions. Please enlighten me. Thanks Regards, ALfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Incorrect board init with 256M RAM on MX31
Hi All, When i use 128M in my board configuration and pass the same to he kernel using bd_info , the linux kernel just boots up fine. But when i change the config to put 256M which is the actual physical DDR size on our board, the userspace crashes because of a unhandled page fault via Unable to handle kernel NULL pointer dereference. First off, perhaps the U-boot is not initializing the memory properly. Although i thought, the board specific dram_init does it with the correct config params picked up from the board config file. I change the following in the board specific config: #define CONFIG_NR_DRAM_BANKS2 #define PHYS_SDRAM_1CSD0_BASE #define PHYS_SDRAM_1_SIZE (256 * 1024 * 1024) What else does the uboot need to convey to the kernel. I am using Freescale MX31 board. Any hints/clues? Thanks in advance for your help. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] config_jffs2_nand
Hi All, What does the CONFIG_JFFS2_NAND do? Looks like its being used in common/cmd_jffs2.c for some erase block specific validation. I am not sure on that. Can anyone help explain? Thanks in advance. -Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] NAND issues
That controls whether the jffs2 command supports NAND. Iis it a MUST HAVE if you are using a jffs2 root filesystem? I mean do i have to turn on CONFIG_JFFS2_NAND if i have a jff2 rootfs. Are there any other configuration flags i need to turn on for JFFS2 support? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MX31 SDRAM size
Hi, We are thinking of migrating to a 256M chip on the MX31 3stack based board. WHich all config variables have to be changed apart from SDRAM_SIZE and no of banks(CSD0)? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] NAND issues
Hi All, I have been using the nand erase.e command with favourable results till now. I was enticed by the CONFIG_JFFS2_NAND option in the platform config. When i turn this config option on and use the NAND. write.jffs2 , and use the resulting image, i get abnormal results including a kernel crash. What is the difference between a nand write.jffs2 and the traditional nand write.e command? I haven't been able to dig up on any relevant documention. I haven't grepped through the common source for the NAND subsystem. Are the commands any different , which of the commands is deprecated? i was guessing nand write.e understands bad blocks whereas nand write.jffs2 understands bad blocks as well as jffs2 internals like cleanmarker etc. Which one should i be using? Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] NAND issues
Just realised that i dis reply instead of reply all. We have been using 2009.1 based version.. We have been using nand read.e/write.e. Is that fine? After skimming through the u-boot code, it seems though. Please confirm. Apart from this, what does the CONFIG_JFFS2_NAND do? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U boot booting issues on soft reset
Either U-Boot does not perform a real processor reset on your platform, and/or your system does not really reset all peripherals. The issue of a reboot command sure is just a processor reset , it does not reset the peripherals including the NAND i guess. Could it be a problem with the NAND boot code. Or would it be in lowLevelINit. S for our platform. But if that would have been the case, it should not have gone till the point it starts uncompressing the kernel. as you see in my earlier email. Redboot just works fine with the same sequence of issuing a Linux reboot everytime. Could that be something wrong with the kernel image. Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U boot booting issues on soft reset
Dear Wolfgang Either U-Boot does not perform a real processor reset on your platform, and/or your system does not really reset all peripherals. THe issue of a reboot command sure is just a processor reset , it does not reset the peripherals including the NAND i guess. Could it be a problem with the NAND boot code. Or would it be in lowLevelINit. S for our platform. But if that would have been the case, it should not have gone till the point it starts uncompressing the kernel. as you see in my earlier email. Redboot just works fine with the same sequence of issuing a Linux reboot everytime. Could that be something wrong with the kernel image. -Munro. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U boot booting issues on soft reset
Hi All, When i do a soft reset or issue a reboot command from linux, uboot is unable to boot,getting stuck . Uncompressing Linux. ... done, booting the kernel. But on a power cycle, U-boot seems to be booting kernel just fine without issues . Initially , i thought the U-boot config was not persistent but looks like the U-boot'd doing something weird. What might be the issue? Does anyone have clues/hints? -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot make config errors
Hi all, I have been building/using u-boot for uite some time now. I never had issues with it. Now, I am trying to use a versioning system to store a version of u-boot and then check out a fresh version from the repository on a different workspace and trying to compile it. I get the following errors on running config for that specific platform. u-boot]$ make mx31_config Configuring for mx31 board... rm: cannot remove `asm': Is a directory make: *** [spin2_config] Error 1 I tracked this problem to be in the include directory and i can alleviate this problem by copying the whole include directory from my local known to be working version. But every time i do a build on freshly checked out version, it gives me the same error as above. Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot make config errors
Hi all, I have been building/using u-boot for uite some time now. I never had issues with it. Now, I am trying to use a versioning system to store a version of u-boot and then check out a fresh version from the repository on a different workspace and trying to compile it. I get the following errors on running config for that specific platform. u-boot]$ make mx31_config Configuring for mx31 board... rm: cannot remove `asm': Is a directory make: *** [spin2_config] Error 1 I tracked this problem to be in the include directory and i can alleviate this problem by copying the whole include directory from my local known to be working version. But every time i do a build on freshly checked out version, it gives me the same error as above. To add to that i am having problems doing a distclean too. make distclean rm: cannot remove `include/asm/arch': Is a directory rm: cannot remove `include/asm': Is a directory make: *** [clobber] Error 1 Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 5/7] mxc-mmc: sdhc host driver for MX2 and MX3 proccessor
Hi Ilya, This is a port of Linux driver for SDHC host controller hardware found on Freescale's MX2 and MX3 processors. Uses new generic MMC framework (CONFIG_GENERIC_MMC) and it looks like there are some problems with a framework (at least on LE cpus). Some of these problems are addressed in the following patches. Have you tested this driver interfaces to load a kernel image(uImage) from the SD card? Does it work for you? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] iMX27 PDK board support
We have support for the MX35-3-Stack, you might want to have a look at that code if you are working into that direction. Where can i find the MX35-3-Stack patches? Does it support boot from NAND and does it have the NAND flash driver already? Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] iMX27 PDK board support
Where can i find the MX35-3-Stack patches? Does it support boot from NAND and does it have the NAND flash driver already? Are you talking about this in the GIT? http://git.denx.de/?p=u-boot/u-boot-v2.git;a=tree;f=board;h=1b079f6910333c85920da3331cc93675447695d7;hb=aec91d05374bd4a0babc0d6ad2e4e78252304cd0 Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Driver for SDHC controller on IMX27
Hi Ilya/Fabio, I followed your guidelines for trying to use the MX27 SDHC driver/MMC framework as the base code and make appropiate mods to make it work on the MX31 PDK board but i have been unsuccessful till this point. i had left this task off at a point because of higher priorities. Do you know if there is an existing driver to make SD cards work on uboot. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] AVIC initialization in Uboot for mx31 pdk
Hi Magnus/all, I believe that AVIC has to be initialized for the MX31 PDK for getting any peripheral based interrupt to work. I did not find any instance of it in the latest MX31 PDK patch, or am i missing anything. If we are assuming that this responsibility gets transferred to the kernel, then its fine. Please correct me if i am wrong. If it has to be done in U-boot, what would be an approriate place to do it. Please correct me if i am wrong. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Appropiate place for custom board init
Hi, I have a requirement fro initializing the GPIO pin for interrupt on a custom FPGA on the MX31 board. Where should i add this code in the uboot tree. Thanks in advance! -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MMU init code in uboot for MX31 PDK
Hi Magnus/all, Where does the mmu_init code in the uboot code for mx31 pdk reside? I am looking for things with MMU initialization like setting the actual base, virtual base and the TLB settings. Can anyone throw light on the same?Thanks in advance!! -Munro. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] MMU init code in uboot for MX31 PDK
The MMU is not used in ARM/U-boot, at least not on the i.MX31. I was thinking there has to be a mechnism which defines the phystovirtual mapping table before the kernel starts running in the virtual space and the IO peripherals to access memory space/registers. Redboot does the same, hence i thought u-boot must be doing it somewhere. Please correct me if i am wrong. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Clock frequency on a mx31 board
Hi, The processor clock on the board i am using is to 532Mhz. I want to default it to 400(399) Mhz. I tried tweaking values in include/configs/boardname.h file but with little success. How do i change the frequency to 399 through the uboot code? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Uboot porting Cloning an existing board/processor configuration : Link errors
Hi All, I am trying to clone the configuration of a board already exiting in U-boot in an effort to port u-boot to this board. I changed the following files Makefile - To copy the config rule for the corresponding board. created a directory for the new board in the board directory and copied over all the files in the directory(cp -a). The issue is although the compile works fine, during linking, the linker tries to look for the cloned boardfile name when it searches for the corresponding board library -libboard.a. The following error is thrown: arm-none-linux-gnueabi-ld: cannot find board/freescale/mx31_3stack/libmx31ads.a Here mx31ads is my cloned board not my board. i know this is done by the $BOARD variable but i was unable to quickly track where in the config.mk's/Makefile it still tries to look for the cloned boards library. Any quick hints will be appreciated. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] mmc: it's safe to ignore mmc_send_if_cond() return value
Hi Ilya, Just make sure that you have all needed clocks enabled. Thanks!One thing i forgot mentioning is that when i had adopted your patch on my baseline code, i started getting the infamous 'u64 ' (64 bit) division LINK errors while compiling with EABI rooting out of the clock based calculations.(prescalar and divider etc.) Hence i googled out and found out two patches that fix-arm920t-eabi.patch uboot-eabi-fix-HACK.patch I applied these patches hand edited some files to fix the compilation problem. I know you had some latest patches to use lldiv() instead but how did you get rid of the compile issues without lldiv initially. Are you compiling without EABI? -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] mmc: it's safe to ignore mmc_send_if_cond() return value
Thanks for the much waited reply. I've only tried my patch on i.MX27 board. I mentioned that it may work on MX3's too cause the kernel driver used as a source works on both MX2 and MX3. You need to do some changes for my driver to work on MX3. Check the pins configuration and if you have MCI clock signal enabled. As a quickstart, I am actually trying to look at the mxcmci_probe() for the init stuff. I hope thats the correct approach for finding the initialization stuff. Another For the GPIOs to set the signals right(data/clk/cmd) , i am using the following chunk of code. Also you should use another function to get the clock rate on MX31. Sorry, I can't debug the driver on mx31 now, you should do it yourself. Apologize if i had menat that in my emails, i never meant that you test it on the mx31 board Probably you may also want to discard my generic mmc patches (except for this one) and pull from u-boot-mmc tree instead. Would it matter even if i use the patch? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] mmc: it's safe to ignore mmc_send_if_cond() return value
Looks like accidently somehow pressed the send button. Apologize! Thanks for the much awaited reply. I've only tried my patch on i.MX27 board. I mentioned that it may work on MX3's too cause the kernel driver used as a source works on both MX2 and MX3. You need to do some changes for my driver to work on MX3. Check the pins configuration and if you have MCI clock signal enabled. As a quickstart, I am actually trying to look at the mxcmci_probe() for the init stuff. I hope thats the correct approach for finding the initialization stuff.For the GPIOs to set the signals right(data/clk/cmd) , i need to initialize them. The linux mxc_request_iomux() api seems to be a cumbersome although porting it would need removing the IO_ADDRESS and the spinlock stuff. What approach did you have for porting the iomux.c linux code.As for the clock_enable part and attaining the prescaler and the dividers foer clock generation, how did you do it. I can only see a linux api called clock_enable in the probe() routine for the same. However, i did not see anything similar in your patch. Is it in the generic arm code location in uboot(arm/mx27/)? Another confusion is on the spba_take_ownership() spba_take_ownership(SPBA_SDHC1, SPBA_MASTER_A | SPBA_MASTER_C); What does spba (shared peripheral bus access)do and do i have to play with it for the SDHC. From the manual it doesn't look like so, but is beiong used in the linux board init code. I hope mx27 should be similar. you should use another function to get the clock rate on MX31. Sorry, I can't debug the driver on mx31 now, you should do it yourself. Apologize if i had meant that in my email, i never wanted you test it on the mx31 board . I just need some pointers to accelerate the development. Thanks for your help. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] mmc: it's safe to ignore mmc_send_if_cond() return value
Hi, my English is not perfect really... but I'm actually having hard times trying to understand yours... So I give you my excuses in advance for possible misunderstandings... IMO too, I know i have a horrible English . Trying to improve;) Pls dont hesitate in asking em to rephrase. I believe it's enough to use mx31_gpio_mux() here. You just need to figure out correct arguments. But if you'll port complete iomuxing API from Linux and post it here I think nobody will be unhappy ;) I get it. We don't have clocks API in U-Boot. You need to enable the clock by setting appropriate bit in the clocks control register manually. Why do i have to touch the CCM? IIRC, Can't it be controlled with the STR_STP_CLOCK (bit 0). When i read the CCM using md.l it shows the Clock output set to IPG_CLK already which is an input the internally generated MMC_SD_CLK. Please correct me if am wrong. Hmm... I didn't touch any SPBA setting on mx27... But it may be needed on mx31... Look at the spba_take_ownership() code and if it does somethings with registers try setting registers to the same values from your board code. I have it set in my code, it does not make any difference . I think it makes sense only for interrupt and dma transfers although i am not sure. Another thing i wasn't sure of was as to where is the endianness and bus width for the host controller getting set in the mx27 code? That's all I can tell you: check pins configuration, check if the clocks are enabled and if mx31 has more than one MMC controller check that you are trying to talk to the one with card connector (or just try other choices). Thanks Ilya. Will try. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 05/10] mxc-mmc: sdhc host driver for MX2 and MX3 proccessor
On Wed, May 6, 2009 at 1:30 PM, Ilya Yanok ya...@emcraft.com wrote: This is a port of Linux driver for SDHC host controller hardware found on Freescale's MX2 and MX3 processors. Would this work asis on the MX31 uboot. I tried making the code work on the MX31 with minor mods ( on some registers). Would it work on MX31? I am trying to understand the hardware better. I had some confusion on the internally generated clock. This code seems to borrow heavily from the linux api's. So it i s using the imx_get_perclk2() function as a source of the divder frequency. Will it work on the imx31. U-boot already has the mx31_get_ipg_clk() for extracting the clock. Which one should i use for the SD_MMC_CLOCK? From the data sheet, it seems ipgperclk3() has to be used for the divider. I am not sure though at this point . I am not getting a response from the SD card for the OCR for voltage validation as a part of the card identification cycle. Any help will be appreciated. Thanks, Alfred, ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Unable to debug UBOOT
Looks like you are reinitializing the DDR , when u are already executing from it, you may want to comment out that code, which initializes DDR. To add to that, if you have cloned code for an already existing platform config file, See if the CONFIG_SKIP_RELOCATE_UBOOT and CONFIG_SKIP_LOWLEVEL_INIT flags in your config file(include/configs) are enabled. If these flags are not enabled, you might need to enable them,s o that the early initialization code is skipped. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 05/10] mxc-mmc: sdhc host driver for MX2 and MX3 proccessor
HI Ilya, This is a port of Linux driver for SDHC host controller hardware found on Freescale's MX2 and MX3 processors. Uses new generic MMC framework (CONFIG_GENERIC_MMC) and it looks like there are some problems with a framework (at least on LE cpus). Some of these problems are addressed in the following patches. Would your patch work for the MX31 pdk. Or it will not work as-is is because the IOMUX setup might be different between MX27 and 31. Al though i have verified that the register set for the HController is the same. Can this be used as a base though? Thanks. Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, uImage to. Itried 0x8100 and 0x80008000 and i am still unable to load the kernel off u-boot.? Thanks for all the help! I have got linux booting from u-boot. So it had something to do with one of the device drivers Doing a post mortem on the printk log buffer pointed me to the problem. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot snapshot for commit dfc91c33957c95da34e3888dc87912d5c15a7603
All, How do i get a snapshot of commit dfc91c33957c95da34e3888dc87912d5c15a7603 from the GIT web. I tried clicking on tree after putting the commit no in the text box but the commit tarball i got wasn't the one i intended to. Thanks for your help -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, I tend to load my kernels to 0x8100 and not 0x80008000 but I don't know if that really matters. Other than that I think 'run bootcmd_net' should work. Oops i realized i top posted:( I am re-posting again. i checked in the kernel code rpm/BUILD/linux/arch/arm/mach-mx3/Makefile.boot. which probably expects the uboot load the kernel at address 0x80008000(zreladdr) which is probably the kernel image relocated address zreladdr-y := 0x80008000 params_phys-y := 0x8100 (boot arg location which i verified doing a md on u-boot). initrd_phys-y := 0x8080 Are these the correct params or is there any other place you look at for verifying if the u-boot and kernel match on the values of loadaddr, bootarg location ? Thanks ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Yes, those values are correct. The boot_params address is also in arch/arm/mach-mx3/mx31pdk.c (mx3_3stack.c if you use Freescale's BSP). Where do i get the latest version of Freescale BSP? i know this is not the correct forum...but still Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
(Click on IMX31_PDK_14_LINUX_BSP_R14 ) Thanks Fabio. Do you know what the load address and entry point for creating a uImage are for the mx31 pdk board and where to load the uImage to. Itried 0x8100 and 0x80008000 and i am still unable to load the kernel off u-boot.? Best Regards, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, If U-boot had full NAND support for i.MX31, NAND would be detected somewhere between steps 7 and 8. Thanks for the elaborate explanation. I did not find any detailed documentation for the same in the u-boot readme's. See my explanation above. CONFIG_SKIP* is defined when compiling U-boot, but not when compiling SPL. That explains why i swa the #warning spit out. So you mean the CONFIG_SKIP_LOWLEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT get toggled during compile time only. I am still struggling to get the NAND boot working. I am not even seeing U-boot spit out the first line on the console U-boot version no when i power up subsequently. This is what i did to build and run. i) make mx31_pdk_nand_config ii) make Take U-boot-nand.bin and burn it at physical offset 0x0 of the NAND using Redboot loaded via JTAG. When i reset, i see nothing on the console. I may be missing something which applying the patches then. Remote gdb does not allow me to debug. If i put printfs in _start_armboot in board.c, looks like its not ven entering that function. Has the standard output and the serial console dev been initiliazed before this point i.e start_armboot? Have you got a chance to post the patches to the mainline yet? Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, I need more time to post the patches since I'm taking care of some comments that were posted to Maxim's patches (which I'm using as a base). That's fine. Which linker script gets actually used for the layout in in case of nand_spl. Is it u-boot-nand.lds or u-boot.lds.? Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi
That's fine.
Which linker script gets actually used for the layout in in case of
nand_spl. Is it u-boot-nand.lds or u-boot.lds.?
I am going back to the original intent of this thread, booting off the
linux kernel using TFTP. Here's is a dump of my U-boot env. Does
it look good enough for booting a linux kernel. WHat could be the
reason that the( md of the printk log does not show up the console
=ttymxc0,115200 correctly.
It looks like its. just ttymxc0,1152 as evident from the memory
dump i had sent ealier in this thread.
=printenv
baudrate=115200
netdev=eth0
uboot=u-boot.bin
nfsroot=/tools/rootfs/rootfs-2.6.24
bootargs_base=setenv bootargs console=ttymxc0,115200
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serveri
p}:${nfsroot} rw
bootcmd=run bootcmd_net
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${tftp_server}:
${kernel}; bootm
tftp_server=206.44.18.25
kernel=uImage_spin2
loadaddr=0x80008000
bootdelay=5
filesize=196828
fileaddr=8100
ipaddr=206.44.18.31
serverip=206.44.18.25
loadaddr=0x80008000
bootargs=root=/dev/nfs rw
stdin=serial
stdout=serial
stderr=serial
Thanks.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, Thanks. If it comes that far it looks like a lot is working. Don't know why the rest isn't though. At this point, it should be showing up the processor info. I am using a custom board with a different flash part. Samsung(KR series), and i guess it is part of nand_id table as i have used that to get my other version (patches form internal fresclae git) up and running. But i believe the overall flash detection happens automatically once you have the id in place. Correct me if i am wrong. Are there any specific files to look into from here. Another thing i noticed is that the config file in my build was somehow defining CONFIG_SKIP_LOWLEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT which should not be the case. I put a #warning to identify that. What could be wrong? //#if defined(CONFIG_NAND_U_BOOT) !defined(CONFIG_NAND_SPL) //#warning defined(CONFIG_NAND_U_BOOT) !defined(CONFIG_NAND_SPL) //#define CONFIG_SKIP_LOWLEVEL_INIT //#define CONFIG_SKIP_RELOCATE_UBOOT //#endif Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, The mainline u-boot + my patches from early April does not contain any driver for the i.MX31 NAND flash controller so that can't autodetect any flash part at all. How does it boot out of NAND then? I am getting confused. By detection, i meant the basic init of the NFC and the NFCBUF and the associated initiliazation to pool the SPL off the NAND which further hand over to the uboot. Follow the startup sequence in lib_arm/board.c:start_armboot and place printf at strategic locations (unless you have a debugger which you can single step in). How do i debug after u-boot relocates itself in RAM. I am getting this on using u-boot as the ELF file with arm-elf-gdb. I remember when i had the BDI3000 handy, i was getting a segfault when doing a remote target IP:2001. Please suggest. CONFIG_NAND_SPL is defined in nand_spl/board/freescale/mx31pdk/Makefile when it builds the second phase loader. CONFIG_NAND_SPL is fine but CONFIG_SKIP_LOWLEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT should not be defined in case we are booting out of NAND, right? Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, Thanks! Here's a 'snapshot' function in git-web (http://git.denx.de/?p=u-boot.git;a=tree) which will produce a tarball of the current tree. Before that, i actually managed to git clone to a windows machine(at my home) and export the u-boot tarball to my office linux host where its destined to build. I got quite a few HUNK failures when i applied your patch to that so I hand edited MAKEALL and Makefile and some other to restore parity. But then on doing make mx31_pdk_config, i got the following: $ make mx31ads_config : invalid option make: *** [mx31ads_config] Error 1 So looks like somewhere out there , some file has some weird windows inherited character/s e.g CRLF characters while doing a git cone although i am not sure I am unable to identify the file. Any idea. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Uboot NAND SPL make for MX31
Hi Magnus and all, Should i do a mx31pdk_nand_config instead of the regular mx31pdk_config to get the nand boot working on the PDK board. I can make that out from the lowlevel_init.S code, but i am not completely sure though. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, No, but it seems that the problem is in the patched Makefile since it says mx31ads_config instead of mx31_pdk_config. I tried this on all the RULES as i was getting the same results for the rule mx31_pdk_config. Apologize for for posting the wrong one. This problem got resolved when i useda tarball from the snapshot feature of the GIT instead. So , in order to boot out of NAND, all i need to do is use the image generated out mx31pdk_nand_config instead of the regular mx31_pdk_config. Right? Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, So , in order to boot out of NAND, all i need to do is use the image generated out mx31pdk_nand_config instead of the regular mx31_pdk_config. Right? Another thing which confuses me is the file nand_boot_mx31.c . Is it a symbolik link which points to the genric nand_boot.c or is it a file by itself. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, Thanks again! The nand_spl/nand_boot_mx31.c is a regular file if that's the one you mean. The reason i am asking is I am getting a build error related to this file after i apply your patches. When i do a ll(ls -l) on the file, i get $ll u-boot-head/u-boot/nand_spl/board/freescale/mx31pdk/nand_boot_mx31.c u-boot-head/u-boot/nand_spl/board/freescale/mx31pdk/nand_boot_mx31.c - u-boot-head/u-boot/nand_spl/board/freescale/mx31pdk/nand_boot_mx31.c And there is NO real nand_boot_mx31.c from the patches i picked up from the mail archives. Perhaps i am looking at your older post. Can you point me to the exact location for the basic support and the NAND spl support. As i am writing this email, . i found a new one http://www.mail-archive.com/u-boot@lists.denx.de/msg11732.html. IS that the correct one? Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Dear Magnus, Yes, that's the latest one I've posted (I've done minor updates locally but haven't tested those yet). I guess that's there are two patches for NAND_SPL, one which just adds the SPL framework and the other which creates the mx31pdk_nand.c and changes to start.S. Please correct me if i am wrong. Since the cpu/arm1136/start.S has changed in a major way since April 02, since this is a generic file, i am getting a BIG .rej file for the HUNKS which failed. I can hand edit start.S as i have done for the rest of the HUNK failures which were minor. But is there a way i can get the snapshot as of April2, so that i can apply this patch right away. This would greatly reduce the effort. Or you suggest sticking to the latest and greatest mainline. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Or you suggest sticking to the latest and greatest mainline. Alternatively, will use the .rej to generate the new lot of patches. That seems the best route. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Magnus, I just applied the patch series to the current u-boot tip and the only problem was the top Makefile but that was easy to fix. No warnings from start.S. I was able to build successfully after hand editing some of the hunks in start.S. Even after using the commit snapshot you had referred to. I don't know where he disconnect is. Perhaps i am still not using the latest set of patches. Towards the end of my build , i get cat nand_spl/u-boot-spl-aligned.bin u-boot.bin u-boot-nand.bin #cat nand_spl/u-boot-spl-16k.bin u-boot.bin u-boot-nand.bin But when i tried burning u-boot-nand.bin to the base address and boot , i get only one line printed on the console which is U-Boot 2009.01 (Apr 28 2009 - 15:27:19) Looks like somethings messed up in the NAND detection in the first place. I am using Redboot FIS to burn the u-boot-nand.bin . I know it ignores bad blocks but i had used successfully to burn in the past. I do not know the procedure for using u-boot to burn u-boot. Let me know if you want me to try it. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Uboot mtest hang on mx31
Hi Alessandro, Thanks! #define CONFIG_SYS_MEMTEST_START 0 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0x1 So, is the config file wrong? So, most likely memtest without arguments has never been used on the board. Is it the cause for the hang, then? I thought it could be something wrong with the way i built my u-boot (linker script etc.) which was causing the crash/hang. Regards, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
I think the first step would be to get MX31PDK into mainline U-boot. Are you willing to help on that? Of course, as long as i have it up and running and tested on my hardware. But in order to do that, i would need your help in answering my earlier question. Thanks for your help! -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Dear Magnus,
Thanks for the reply!
And we need to know which U-boot patches you're using to boot the PDK
board.
I am using the internal git tree code supplied to me by freescale. The
tarball is called uboot-imx-imx_v2009.01.tar.gz. I can boot uboot
out of NAND successfully using that as the code base. I had started
using this even before Magnus had posted the patches and i had to
write a patch for the MMC/SD driver on top of that . To add to that ,
i tried downloading the mainline using GIT but it seems the corporate
firewall/proxy we have blocks it. Due to the shortage of time, i
continued to use the Freescale supplied code. It would be great if you
can supply me the code in a tarball(mainline git) with the patches you
posted if you want me to try it out.
In your original post you use the go command to boot the
kernel,
I use the bootm command now. My sole intention of using go was to
check whether or not zImage( instead of uImage) boots up as a generic
application. I tried verify the bootags in the U-boot environment. I
chacked on the machine id which gets registered with the kernel. They
all seemed to be the expected values.
Coming back to I am not sure about ,was when i tried dumping the
address(0x8100) which supposedly stores the bootargs, i get the
following :
= md 0x8100
8100: c100 c100 c108 c108
8110: c110 c110 c118 c118
8120: 92492492 24924924 0149 736e6f63.$I.$I.$I...cons
8130: 3d656c6f 6d797474 2c306378 32353131ole=ttymxc0,1152
8140: c140 c140 c148 c148@@...h...h...
It looks like the console is not set correctly to 115200, assuming its
in ASCII. Any clues as to what could be gone wrong?
Another quick question is do i have to supply the mem=XX argument
if my CONFIG_SETUP_MEMORY_TAGS is set in include/configs/mx31_pdk.h
BTW, following is an extract from the uboot linker script -u-boot.lds
which i had edited. Please let me know if you think something's wrong
with it.
OUTPUT_ARCH(arm)
ENTRY(reset)
SECTIONS
{
. = 0x;
. = ALIGN(4);
.text :
{
/* WARNING - the following is hand-optimized to fit within*/
/* the sector layout of our flash chips! XXX FIXME XXX */
* (.text.head)/* arm reset handler */
* (.text.init)/* lowlevel initial */
* (.text.load)/* nand copy and load */
* (.text.setup)
board/freescale/mx31_3stack/libmx31_3stack.a (.text)
lib_arm/libarm.a (.text)
net/libnet.a (.text)
drivers/mtd/libmtd.a (.text)
. = DEFINED(env_offset) ? env_offset : .;
common/env_embedded.o(.text)
*(.text)
}
. = ALIGN(4);
-Alfred.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Uboot mtest hang on mx31
Hi All. When i do a memtest without any args, it crashes after printing the first line. I know the output may vary depending on the processor and the memmap. I just wanted to knoe is this tha appropiate behaviour for mtest. CPU: Freescale i.MX31 at 531 MHz Board: MX31 3Stack DRAM: 128 MB NAND: Bad block table found at page 65472, version 0x01 Bad block table found at page 65408, version 0x01 nand_read_bbt: Bad block at 0x01b0 nand_read_bbt: Bad block at 0x02ae nand_read_bbt: Bad block at 0x02c6 nand_read_bbt: Bad block at 0x052a nand_read_bbt: Bad block at 0x052c 128 MiB In:serial Out: serial Err: serial Hit any key to stop autoboot: 0 = = mtest Pattern Writing... The serial console just freezes here, meaning an evident crash After reboot, when i do and md for the base address 0x0, i get the following, which proabbly is the uboot image itself in RAM. So i am guessing, the memtest tries modifying the U-boot in memory and hence the crash. i am not sure though Please correct me if i am wrong. Here's the message log. CPU: Freescale i.MX31 at 531 MHz Board: MX31 3Stack DRAM: 128 MB NAND: Bad block table found at page 65472, version 0x01 Bad block table found at page 65408, version 0x01 nand_read_bbt: Bad block at 0x01b0 nand_read_bbt: Bad block at 0x02ae nand_read_bbt: Bad block at 0x02c6 nand_read_bbt: Bad block at 0x052a nand_read_bbt: Bad block at 0x052c 128 MiB In:serial Out: serial Err: serial Hit any key to stop autoboot: 0 =md 0 : e59ff00c e59ff018 e59ff018 e59ff018 0010: e59ff018 b800 e59ff014 e59ff014 0020: 0090 1fd0 1fd4 1fd8 0030: 1fdc 1fe0 1fe4 0040: 79706f43 68676972 63282074 30322029Copyright (c) 20 0050: 4d203430 726f746f 20616c6f 2e636e4904 Motorola Inc. 0060: 6c6c4120 67697220 20737468 65736572 All rights rese 0070: 64657672 002e rved 0080: 02b4 04e0 0524 $... 0090: e321f0d3 e59fd008 e59f0008 e12fff10..!.../. 00a0: ea01 1fd0 00e0 e321f0d3..!. 00b0: e59fd014 e59f0014 e3a0106c e5c01000l... 00c0: e59f000c e12fff10 eaf7 1fd0../. 00d0: 1fffc800 02b4 00e0: e59f2064 e59f005c e59f1054 e3c22003d ..\...T .. 00f0: e0823000 e153 34912004 34802004.0P.. .4. .4 Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi Fabio, Are the load address and other params same for PDK and the ADS board. I intend to do the same as what you intended to aith sucess. I saw your post her : http://www.nabble.com/Loading-a-kernel-on-MX31ADS-using-U-boot-td16642427.html Please let me know how were able to sucessfully load the kernel. My bootup sequence too hangs after Uncompressing kernel...done booting the kernel. Thanks. On Fri, Apr 24, 2009 at 1:23 PM, Fabio Estevam fabioeste...@yahoo.com wrote: Hi Alfred, --- On Thu, 4/23/09, alfred steele alfred.jaq...@gmail.com wrote: I have attached the printk circular buffer log. smc911x: initializing smc911x: detected NULL controller smc911x: phy initialized smc911x: MAC 92:92:92:bb:bb:bb TFTP from server 206.44.18.25; our IP address is 206.44.18.31 Filename 'zImage_spin2_23march'. Is this really an uImage? The name of the file starts with zImage, so it looks confusing. Can you confirm? How are you generating the uImage? Assuming you are using MX31PDK Freescale BSP, you can do as follows: cd rpm/BUILD/linux make ARCH=arm uImage (You need to have mkimage installed) Which U-boot version are you using? Regards, Fabio Estevam ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot -printk kernel crash dump using md on PDK
Dear Wolfgang, You top post. You full quote. Sincere Apologies. I better watch out before i hit the send button. Best Regards. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot memory dump
Hi, I am using uboot on the MX31 PDk board. I am trying to dump the contents of a status register found at location 50004004. This status register shows the status of the SDHC( SD card host controller) like interrupt , card insertion, card removal etc. According to the MX31 manual, the status register i.e the contents at the corresponding memory location should change on events like card insertion and removal. But the contents aren't changing as expected. I have verified this with Linux and it works. i) Before card insertion = md.l 50004004 50004004: 30004000 0008 0040 ii)After card insertion = md.l 50004004 50004004: 30004000 0008 0040 Could anything be wrong with my u-boot image or the memory initialization(although anything going wrong with the init dosent make sense). Thanks in advance! Thanks, Alfred ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Uboot Remote gdb gives segmentation fault and hangs
Hi, I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been succesfully using this gdb to a great extent. However, when i try my vanilla u-boot image with debug, i get a segfault. $ arm-elf-gdb u-boot GNU gdb 5.3 (eCosCentric) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as --host=i686-pc-linux-gnu --target=arm-elf... (gdb) symbol-file u-boot Load new symbol table from u-boot? (y or n) y Reading symbols from u-boot...done. (gdb) target remote 206.44.17.238:2001 Remote debugging using 206.44.17.238:2001 Segmentation fault AT this point, even the running u-boot on the console hangs/crashes. Could it be something wrong with the uboot binary itslef. If so, any hints as to what could be wrong? I have been using theis arm-elf-gdb sucessfully with Redboot in the past. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Booting uImage on the mx31
Hi, I am using an uImage generated by LTIB . I am not sure how the ideal uImage is generated for the PDK board. I try booting this uimage from RAM and then load it at 80008000. It gets stuck after done, booting the kernel. Please see the bootup messages below. Any hints? I hope with, 0x80008000 as the load address on the MX31, you eliminate the cause of one probable failure, overlay memory with the existing code on RAM e.g. existing u-boot and the compressed kernel image mc911x: MAC 92:92:92:bb:bb:bb TFTP from server 206.44.18.25; our IP address is 206.44.18.31 Filename 'uImage_spin2'. Load address: 0x8080 Loading: # # done Bytes transferred = 1665060 (196824 hex) ## Booting kernel from Legacy Image at 8080 ... Image Name: Linux-2.6.24-140-g68eb4b4 Created: 2009-04-23 3:28:44 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1664996 Bytes = 1.6 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux. ... done, booting the kernel. IT freezes here Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Booting uImage on the mx31
Hi Wolfgang, Thanks for the inputs. So what you are saying that we have eliminated all cases of the bootloader being at fault here except for the mach id mismatch.?? How do i verify the mach id mismatch. Is it the same id i see on a bdinfo dump on uboot. I looked at linux/include/asm/mach-types.h in linux . Is that the correct place to look at? How do i debug this kind of an issue on the BDI since it may fall between the thin line of separation between MMU disabled and reenabled. Can i put a breakpoint on a specific_thing like start_kernel ..or do you mean doing a backtrace from the point it hangs? I am using PDK which actually limits me to change boot switches for booting it from NAND or RAM. On Thu, Apr 23, 2009 at 11:05 AM, Wolfgang Denk w...@denx.de wrote: Dear alfred steele, In message 528f13590904230720n14e87cchb87505c1de085...@mail.gmail.com you wrote: I am using an uImage generated by LTIB . I am not sure how the ideal uImage is generated for the PDK board. ... Starting kernel ... U-Boot's responsibility end's here. Uncompressing Linux. ... done, booting the kernel. IT freezes here Attach a BDI and debug where it's hanging. Eventually just your machine ID is wrong. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Make it right before you make it faster. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Booting uImage on the mx31
Hi Wolfgang, Thanks for the inputs. So what you are saying that we have eliminated all cases of the bootloader being at fault here except for the mach id mismatch.?? How do i verify the mach id mismatch. Is it the same id i see on a bdinfo dump on uboot. I looked at linux/include/asm/mach-types.h in linux . Is that the correct place to look at? From the uboot code and the uboot config bdinfo structure,looks like machine id is set correctly Bdinfo on uboot prompt gives me 5E7 which is 1511 i.e the machine id set in the kernel for the target -MX31 3stack board. What else could be wrong? How do i debug this kind of an issue on the BDI since it may fall between the thin line of separation between MMU disabled and reenabled. Can i put a breakpoint on a specific_thing like start_kernel ..or do you mean doing a backtrace from the point it hangs? I am using PDK which actually limits me to change boot switches for booting it from NAND or RAM. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot -printk kernel crash dump using md on PDK
Hi All, I am using mx31 pdk and uImage generated by LTIB. Basically, my problem is my kernel gets stuck after printing the Done...Booting the kernel. Please the responses below. Upon inspecting the printk log by doing a memory dump of the _buf_log symbol in System.map(i translated it to the physical address before dumping it ). It seems before the console got initialized, the bootup was successful to a certain extent, but i am unable to interpret anything conclusive from the logs. ANy hints as to what might be happening? I am guessing that unexpected RAM regions are getting overwritten after uncompression happens or the sdram hasn't been initialized fully by U-boot. I have attached the printk circular buffer log. smc911x: initializing smc911x: detected NULL controller smc911x: phy initialized smc911x: MAC 92:92:92:bb:bb:bb TFTP from server 206.44.18.25; our IP address is 206.44.18.31 Filename 'zImage_spin2_23march'. Load address: 0x8100 Loading: * # # done Bytes transferred = 1665000 (1967e8 hex) = go 0x8100 ## Starting application at 0x8100 ... Uncompressing Linux. ... done, booting the kernel. PRINTK log == md 80350f68 5000 50 80350f68: 4c3e353c 78756e69 72657620 6e6f69735Linux version 80350f78: 362e3220 2d34322e 2d303431 65383667 2.6.24-140-g68e 80350f88: 34623462 79742820 406f7561 656c7954b4b4 (ty...@tyle 80350f98: 4c575372 694c6261 3278756e 2e4d412erSWLabLinux2.AM. 80350fa8: 50524f43 4952502e 28202956 20636367CORP.PRIV) (gcc 80350fb8: 73726576 206e6f69 2e312e34 23202932version 4.1.2) # 80350fc8: 52502033 504d4545 68542054 704120753 PREEMPT Thu Ap 80350fd8: 33322072 3a353120 323a3131 44432039r 23 15:11:29 CD 80350fe8: 30322054 3c0a3930 50433e34 41203a55T 2009.4CPU: A 80350ff8: 36764d52 6d6f632d 69746170 20656c62RMv6-compatible 80351008: 636f7270 6f737365 345b2072 62373031processor [4107b 80351018: 5d343633 76657220 6f697369 2034206e364] revision 4 80351028: 4d524128 45543676 202c294a 303d7263(ARMv6TEJ), cr=0 80351038: 33356530 0a663738 4d3e343c 696863610e5387f.4Machi 80351048: 203a656e 65657246 6c616373 584d2065ne: Freescale MX 80351058: 4d2f3133 20323358 74532d33 206b636131/MX32 3-Stack 80351068: 72616f42 343c0a64 6d654d3e 2079726fBoard.4Memory 80351078: 696c6f70 203a7963 20434345 61736964policy: ECC disa 80351088: 64656c62 6144202c 63206174 65686361bled, Data cache 80351098: 69727720 61626574 3c0a6b63 6e4f3e37 writeback.7On 803510a8: 646f6e20 20302065 61746f74 6761706c node 0 totalpag 803510b8: 203a7365 36373233 373c0a38 4420203ees: 32768.7 D 803510c8: 7a20414d 3a656e6f 20383420 65676170MA zone: 48 page 803510d8: 73752073 66206465 6d20726f 616d6d65s used for memma 803510e8: 373c0a70 4420203e 7a20414d 3a656e6fp.7 DMA zone: 803510f8: 70203020 73656761 73657220 65767265 0 pages reserve 80351108: 373c0a64 4420203e 7a20414d 3a656e6fd.7 DMA zone: 80351118: 39303620 61702036 2c736567 46494c20 6096 pages, LIF 80351128: 6162204f 3a686374 373c0a30 4e20203eO batch:0.7 N 80351138: 616d726f 6f7a206c 203a656e 20383032ormal zone: 208 80351148: 65676170 73752073 66206465 6d20726fpages used for m 80351158: 616d6d65 373c0a70 4e20203e 616d726femmap.7 Norma 80351168: 6f7a206c 203a656e 31343632 61702036l zone: 26416 pa 80351178: 2c736567 46494c20 6162204f 3a686374ges, LIFO batch: 80351188: 373c0a37 4d20203e 6261766f 7a20656c7.7 Movable z 80351198: 3a656e6f 70203020 73656761 65737520one: 0 pages use 803511a8: 6f662064 656d2072 70616d6d 3e343c0ad for memmap.4 803511b8: 30555043 2044203a 54504956 69727720CPU0: D VIPT wri 803511c8: 622d6574 206b6361 68636163 343c0a65te-back cache.4 803511d8: 5550433e 49203a30 63616320 203a6568CPU0: I cache: 803511e8: 38333631 79622034 2c736574 7373612016384 bytes, ass 803511f8: 6169636f 69766974 34207974 3233202cociativity 4, 32 80351208: 74796220 696c2065 2c73656e 38323120 byte lines, 128 80351218: 74657320 343c0a73 5550433e 44203a30 sets.4CPU0: D 80351228: 63616320 203a6568 38333631 79622034 cache: 16384 by 80351238: 2c736574 73736120 6169636f 69766974tes, associativi 80351248: 34207974 3233202c 74796220 696c2065ty 4, 32 byte li 80351258: 2c73656e 38323120 74657320 343c0a73nes, 128 sets.4 80351268: 6975423e 3120746c 6e6f7a20 73696c65Built 1 zonelis 80351278: 69207374 6f5a206e 6f20656e 72656472ts in Zone order 80351288: 6f6d202c 696c6962 67207974 70756f72, mobility group 80351298: 20676e69 202e6e6f 746f5420 70206c61ing on. Total p 803512a8: 73656761 3233203a 0a323135 4b3e353cages: 32512.5K 803512b8: 656e7265 6f63206c 6e616d6d 696c2064ernel command li 803512c8: 203a656e 6e696f6e 64727469 6e6f6320ne: noinitrd con
[U-Boot] Uboot MMC port
Hi Magnus, The uboot pacth you had supplied earlier for the MX31 PDK does not include the mmc driver. I have asked for a candidate port for me to give a headstart for the sdhc/mmc infrastructure on the MX31 PDK board. In fact, it seems that none of the MX31 based boards support MMC/SDHC. I even tried sending an email to the mmc-git owner but got no reply. I am not sure who to approach on this. Is there a candidate existing in the uboot-git for the mx31 mmc driver. Apologize for using the same thread. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Uboot md crash on PDK
Thanks! But should a crash happen if i am trying to read a non-reserved memory which 0x10 is. Can you tell me how do you choose a address in CSDO RAM to be appropiate for loading uImage and execute it. -Alfred. On Mon, Apr 13, 2009 at 12:24 PM, Magnus Lilja lilja.mag...@gmail.com wrote: 2009/4/13 alfred steele alfred.jaq...@gmail.com: Hi Magnus, For that matter, I can dump memory between 0x and 0x0100 though. However memory dump at 0x10 also fails. Can you point out which pages in the Reference manual point to the same? Chapter 2-1 Memory map. in MCIMX31RM Reference Manual. Regards, Magnus ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Uboot md crash on PDK
Thanks. Apologies for top posting. -Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MMC driver for mx31
Hi, Is there an available driver for MMC/SD for the mx31 pdk board. If not, what would be the closest candidate for porting it over. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Uboot md crash on PDK
Hi Magnus, For that matter, I can dump memory between 0x and 0x0100 though. However memory dump at 0x10 also fails. Can you point out which pages in the Reference manual point to the same? Thanks, Alfred. On Thu, Apr 9, 2009 at 12:53 PM, Magnus Lilja lilja.mag...@gmail.com wrote: Hi 2009/4/9 alfred steele alfred.jaq...@gmail.com: Hi all, I started with trying to tftpload uImage to RAM address 0x1. It was getting stuck. Hence i thought of doing a memory dump on it. md 0x1 It too crashed or got stuck. But when i do a md 0x8001, it works. I checked my linker script to double check on the memory layout. What could have gone wrong when memory dump of specific addresses dont' work. There is no RAM at 0x1 in the PDK/i.MX31, the reference manual states that the memory between 0x0 and 0x404000 is reserved (except for first 0x4000 which is the ROM). /Magnus ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Uboot md crash on PDK
Hi all, I started with trying to tftpload uImage to RAM address 0x1. It was getting stuck. Hence i thought of doing a memory dump on it. md 0x1 It too crashed or got stuck. But when i do a md 0x8001, it works. I checked my linker script to double check on the memory layout. What could have gone wrong when memory dump of specific addresses dont' work. Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot SDHC driver on IMX31 PDK
Hi, Is there a way to access a SD/MMC card from uboot using the FAT32 file system on the mx31 3stack/pdk board. In other words, does it have the minimal SDHC driver support . FAT32, i guess, has been an integral part of the uboot mainline since quite some time. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] generic nand_load.S for mx31
Hi, There is a file cpu/arm1136/mx31/nand_load.S which performs some startup functions for Copy image from flash to SDRAM etc..It does not reinitialize the DDR though. Although i haven't dugged up the details yet, could someone tell me what is the difference between nand_boot.c and nand_load.S or the assembly code is just a helper for the nand_boot api's. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot support on Freescale PDK
Hi Magnus, Thanks for the response:) Until yesterday you were correct. I spent some time updating the published patches to the current u-boot and the status now is that I was able to compile the stuff. Haven't tried it on a PDK board yet but I'm hoping to do that in a couple of days. I will post patches when the stuff is running, the patches will most likely not be ready to be merged as there are previous comments to take care of. Ii had actually embarked myself on modifying the lowlevelinit.S and start.S to create a SPL for uboot although i wasn't sure of finishing it that soo;(. I hope these files apart from the linker script(u-boot.lds) and the config files(config.mk and Makefile) are the ones that need to change for getting NAND boot to work. Please correct me if i don't understand it correctly. I wasn't actually sure why there is a need to create a separate linker script like u-boot_nand.lds. So i hope the patch would be ready in a couple of days. If you want me to try them on the PDK before you actually release it, that would be great. Another thing i noticed while poking around the code is that though MX35 PDK had SDHC(sd card) drivers in it, the MX31 did not. Would it be in a individual GIT , e.g the U-boot mmc git. Thanks, Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Lowlevel init and nand spl Uboot patch for MX31 Phycore NAND boot
Hi: Was going through the patch for uboot posted earlier this year and the related review comments here: http://www.mail-archive.com/u-boot@lists.denx.de/msg01140.html. Looks like the NAND boot for MX31 PDK is not ready yet. I was told that if that the mx31 phycore patch should work just fine for most things on the PDK and hence can be used as a base for a port to the PDK. I am ignorant of the hardware details on MX31 Phycore but when i had a look at the low level init code (lowlevelinit.S) for Phycore and compared it to the existing lowlevelinit.S for the MX31 3stack board, i realized that they are a lot different when it comes to the NAND SPL. I am a newbie to NAND boot. Do i have to rewrite the NAND SPL code for preparing NAND boot images for the 3stack, Or is there a way i can translate some existing code(Maybe redboot code) for the MX31 3stack(PDK). I have modified the top level Makefile to include the sources for getting the SPL code compiled but am stuck at the lowlevelinit.S file. My final intent is to get the uboot boot out of NAND on MX31- 3stack(PDK) although i have managed to get uboot running from RAM on the platform. Thanks in Advance! Alfred. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. It would be great if you can throw some light on it or point me to some relevant documentation. Thanks in advance! On Mon, Mar 30, 2009 at 8:21 PM, alfred steele alfred.jaq...@gmail.com wrote: Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. It would be great if you can throw some light on it or point me to some relevant documentation. Thanks in advance! ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi Scott, Thanks! The only requirement i have currently is to be able to populate the device table with the Samsung K9F1G08R0A because it does not appear in the existing list. This would help the NFC read the part id and the other NAND attributes correctly on the target. Thanks Reagrds, Munro. On Tue, Mar 31, 2009 at 12:20 PM, Scott Wood scottw...@freescale.com wrote: alfred steele wrote: Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c This is the one. However, an individual NAND driver shouldn't have to care; it will be taken care of by the NAND subsystem. ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: Ignore these. They are legacy code that will soon be removed. At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. Most likely it is already in the table. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. Which field in particular are you unsure of? They are described in the definition of nand_flash_dev in include/linux/mtd/nand.h. Is there any reason why your NAND controller driver needs to care about any of this, as opposed to just hooking up to the NAND subsystem? -Scott ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi Scott, Thanks! The only requirement i have currently is to be able to populate the device table with the Samsung K9F1G08R0A because it does not appear in the existing list. This would help the NFC read the part id and the other NAND attributes correctly on the target. Thanks Regards. On Tue, Mar 31, 2009 at 12:20 PM, Scott Wood scottw...@freescale.com wrote: alfred steele wrote: Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c This is the one. However, an individual NAND driver shouldn't have to care; it will be taken care of by the NAND subsystem. ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: Ignore these. They are legacy code that will soon be removed. At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. Most likely it is already in the table. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. Which field in particular are you unsure of? They are described in the definition of nand_flash_dev in include/linux/mtd/nand.h. Is there any reason why your NAND controller driver needs to care about any of this, as opposed to just hooking up to the NAND subsystem? -Scott ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Thanks Again, I am actually confused with the values for chip size which should be the total chip size in MB w.r.t nand_flash_dev structure and pagesize as pagesize seems to be extended bytes alone in the datasheet which i am unable to figure of as of now. The pagesize seems to be different from the exact pagesize as in the data sheet for the other parts in include/linux/mtd/nand_ids.h. Do you know what to look for in the data sheet . On Tue, Mar 31, 2009 at 2:10 PM, alfred steele alfred.jaq...@gmail.com wrote: Hi Scott, Thanks! The only requirement i have currently is to be able to populate the device table with the Samsung K9F1G08R0A because it does not appear in the existing list. This would help the NFC read the part id and the other NAND attributes correctly on the target. Thanks Regards. On Tue, Mar 31, 2009 at 12:20 PM, Scott Wood scottw...@freescale.com wrote: alfred steele wrote: Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c This is the one. However, an individual NAND driver shouldn't have to care; it will be taken care of by the NAND subsystem. ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: Ignore these. They are legacy code that will soon be removed. At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. Most likely it is already in the table. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. Which field in particular are you unsure of? They are described in the definition of nand_flash_dev in include/linux/mtd/nand.h. Is there any reason why your NAND controller driver needs to care about any of this, as opposed to just hooking up to the NAND subsystem? -Scott ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi Magnus, Thanks! Do you remember, off the head, what kind of hardware differences between MX31 and Phycore. I am kind of trying to identify the differences between the two in order to be able to map the patch to the differences. Was the nand_spl directory created for imx31(PDK) NAND specific changes. The reason i am asking is because in the uboot-imx-imx_v2009.01 tarball Freescale has supplied us with, the directory already exists. I am yet to try apply your PDK patch to the same or compare the differences yet. I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. We have been working on Redboot all this while and what's driving us to move to U-boot is the available ability to be able to boot Linux off the SD card on the MX31 platform. Regards, Alfred. On Fri, Mar 27, 2009 at 3:01 PM, Magnus Lilja lilja.mag...@gmail.com wrote: 2009/3/27 alfred steele alfred.jaq...@gmail.com: Thanks Magnus, How difficult or rather much an effort would it need to add NAND boot support and make it work on MX35 or MX31 3stack board. Are there any existing guidelines for accelerating the development or is the generic uboot porting guidelines . For i.MX31 3stack (a.k.a. PDK) there's really not that much porting that needs to be done. mx31 is supported in U-boot so the following is needed: * Update my basic i.MX31 PDK patch to apply on top of the current U-boot git (it's been a while since I updated it) * Add the NAND SPL patch I mentioned in my previous reply (update it with the review comments) * Test and submit the patches The above could be done in a couple of days if your're familiar with i.MX31 and U-boot. Add more time if you're a newcomer to U-boot and/or i.MX31. Since Freescale hasn't published much info on i.MX35 or the 3stack for that I can only guess that it would probably be pretty straight forward to do a NAND SPL for i.MX35 based on the one for i.MX31 (the NAND controller and possibly the SDRAM controller on i.MX35 seems to be different from i.MX31). Regards, Magnus ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi Scott: Thanks! I am also wondering if there is a include file which builds up a table of working NAND devices and thier attributes which tells the U-boot on the parameters about a particular NAND device on the board like Block_size , page_size, device size, pages per block, device id etc. Or This information needs to be kind of hardcoded every time. drivers/mtd/nand/nand_ids.c I have three files which probably make sense to include the new flash part. drivers/mtd/nand/nand_ids.c ./common/cmd_doc.c ./include/linux/mtd/nand_ids.h: At this point, i do not understand the purpose of each and especially how would the structure flash_id be populated from our data sheet for the flash part we use Samsung K9F1G08R0A. I basically do not understand all the elements of the array nand_flash_dev nand_flash_ids[] to be able to populate it correctly. It would be great if you can throw some light on it or point me to some relevant documentation. Thanks in advance! ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] ARM based port for uboot with NAND boot support.
Hi All; Is there an available port for IMX31 3stack with NAND boot. I am looking for a U-boot port for IMX31 stack( which supports NAND boot. The closest matches i know of as of now are as follows: MX-31 ADS MX-31 Phycore Openmoko U-boot (Samsung processor though ARM) - This is the only one on ARM which allows NAND boot. I haven't digged up further so I am not sure at this point which port would be a good enough one as a starting point if no existing port exists. Thanks in Advance! ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Hi All; Is there an available port for IMX31 3stack with NAND boot. I am looking for a U-boot port for IMX31 stack( which supports NAND boot. The closest matches i know of as of now are as follows: MX-31 ADS MX-31 Phycore Openmoko U-boot (Samsung processor though ARM) - This is the only one on ARM which allows NAND boot. I haven't digged up further so I am not sure at this point which port would be a good enough one as a starting point if no existing port exists. Thanks in Advance! -Munro ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Thanks Magnus, How difficult or rather much an effort would it need to add NAND boot support and make it work on MX35 or MX31 3stack board. Are there any existing guidelines for accelerating the development or is the generic uboot porting guidelines . Regards, Alfred On Fri, Mar 27, 2009 at 1:52 PM, Magnus Lilja lilja.mag...@gmail.com wrote: Hi 2009/3/27 alfred steele alfred.jaq...@gmail.com: Hi All; Is there an available port for IMX31 3stack with NAND boot. I am looking for a U-boot port for IMX31 stack( which supports NAND boot. The closest matches i know of as of now are as follows: MX-31 ADS MX-31 Phycore Openmoko U-boot (Samsung processor though ARM) - This is the only one on ARM which allows NAND boot. I haven't digged up further so I am not sure at this point which port would be a good enough one as a starting point if no existing port exists. I would suggest using this patch as a base: http://lists.denx.de/pipermail/u-boot/2009-January/046241.html Use the above and the review comments posted in February as input to your work. It's for the phycore board but it's easy to apply this for the PDK. I've posted some PDK related patches, they should be on the mailing list server. The PDK patches aren't in mainline U-boot yet due to the missing NAND boot support. Regards, Magnus Lilja ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Healthcare Industry Directory
Currently in Practice: Medical Doctors in the United States
Data for the many various medical specialties
Sort by over a dozen different fields
Price for this week only = $398
{}{}{} Order this week and get the additional data below for free {}{}{}
Optometrists
Visiting Nurses RN's
Massage Therapists
Acupuncturists
send email to:: [EMAIL PROTECTED]
valid thru Oct 17 ~~ stop these emails by
looking here please email [EMAIL PROTECTED]
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
