Activity
From 03/29/2013 to 04/27/2013
04/26/2013
- TI 03:58 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Just a pre-weekend update...
We had to switch from the TI PSP u-boot to the mainline u-boot, which is what has kept me busy these last couple of days.
I just got to the point where I can boot the board... have not been able to check NA... -
10:35 AM
Software Development: RE: MityArm u-booting from SPI flash
- Hey Mike,
Our SPI flash is external (on our base card on SPI bus 0), so there should not be an issue booting from it.
John C. - MW 10:18 AM Software Development: RE: MityArm u-booting from SPI flash
- Just to confirm,
You are using a MityARM-335X, right?
Are you trying to use the on-board SPI, or an external SPI?
If you are tring to use the on-board SPI, the MityARM-335x cannot boot the MLO from it. The TI AM335X ROM bootloa... -
09:13 AM
Software Development: MityArm u-booting from SPI flash
- Hi,
I know we had asked about this previously but was hoping to get a little help with the flags and config file in building
u-boot/MLO for booting from SPI flash. It seemed that looking over the mityarm335x.h file if we undefin...
04/24/2013
- TI 01:16 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike
unfortunately, that was just a secondary issue. Currently there is no support for the 4K page size NAND in any of the TI provided software. There is a patch to the main-line u-boot that I am in the process of back-porting to the TI... - MK 12:03 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Tim,
Thanks. Does this resolve the issue, or do you still need to modify ECC on the MLO? - TI 07:31 AM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike
I discovered this same issue yesterday. The mtdparts in the kernel where set up for the 256MB part and not updated for the 512MB part. With the larger block size of the 512MB part, many of the partitions no longer fall on erase blo... - TC 12:07 AM PCB Development: RE: 1GHz AM335x
- Hi Mark -
The revision "A" silicon from TI refers to silicon revision 2.0. The current revisions use the revision 1.0 silicon from TI. Revision 2.0 silicon was not made available outside of TI. Revision 2.1 silicon is just now becomin...
04/23/2013
- MK 10:53 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Out of idle curiosity, I ran mtdinfo on both boards:
For the 256MB:
mtd1
Name: SPL
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: ... - MW 04:14 PM PCB Development: RE: 1GHz AM335x
- Hi -Mike- Mark (sorry),
Couple of comments.
* The PMIC should support the higher current (specs range from 1A max up to 1.5 A if I read the spec from TI correctly).
* The PCB routing should support 400 MHz, but we would need to te... -
03:49 PM
PCB Development: 1GHz AM335x
- TI added 800 MHz and 1 GHz operating points in the latest data sheet for Rev A or newer AM335x processors along with support for 400 MHz DDR3 memories.
Will the latest revs of the MityARM SOM be able to support these faster frequenc...
04/22/2013
- MK 06:09 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- *formation to u-boot supports.* I mean "format that u-boot supports". Sorry, spell check....
- MK 06:07 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- And also, I'm assuming that the bootloader environment section falls into the same category as u-boot.img. That is, the MLO doesn't rely on this section, and that it just needs to be in a formation to u-boot supports.
- MK 06:02 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike,
OK, this makes sense. Sorry for being a bit slow on the uptake. The issue isn't the flash per-se, its matching the SPL to the TI ROM scheme. Am I getting this right?
I can't speak for other customers, but for us flashing t... - MW 05:34 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- It depends on whether you want to be able to (re)flash a bootable MLO from linux. If the linux kernel does not support BCH16 in the same format (it may be using BCH8, which is OK with this particular part) as the TI ROM bootloader requi...
- MK 05:27 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- _We have to look at the kernel as well to see how it deals with the device._
Does this mean there may be an issue with the kernel as well? - TI 03:46 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike,
booting from MMC first sounds like a good plan to me :)
as for the XIP/wait... if the bootrom is not stalling waiting for the device, then you are all set!
There are no XIP bootable devices on the AM335X module or devkit board, ... - MK 02:58 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Tim,
Thanks. We bit 9 set to zero, we no longer get curious boottime ECC error messages we were getting on the DDR2 board.
Still I cannot boot from NAND on the DDR3 board, even with both 9 set to zero and bits 4-0 to 10011.
A... - TI 02:45 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- The good news is I think we have found the cause of the issue.
When the 335x boot ROM sees the 4K page size in the NAND, it switches to a 16 bit ECC scheme, hence the data written with an 8 bit scheme
is invalid.
The less good news ... - TI 09:14 AM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike
While I chase down the block size issue, other Mike pointed out that you have bit 9 of the SYSBOOT pins as a 1. This tells the boot ROM that the NAND device is doing
error correction. 99.9% sure you don't want this as the NAND de...
04/20/2013
- MK 04:39 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Mike,
Thanks for the quick reply.
For our application, the 256MB flash is not a problem, but our current design relies on the 512DDR3 and the ability to boot from NAND. From what I can tell, 512MB Ram/256MB NAND is not an option... - MW 02:04 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Hi Mike,
We are still chasing this here. The 2K vs. 4K page size issue may not be correct for the 512 MB (it came up in conversation for supporting a 1 GB configuration and I wasn't sure if the 512MB part is 4K or 2K, we are tracking... - MK 01:42 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Tim,
Thanks for the tip.
I'm a bit uneasy hacking the bootloader for hardware that I didn't design and don't have a lot of details on (like schematic, BOM, etc.). Actually, a strong selling point for the mityarm is that I would...
04/19/2013
- TI 04:02 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- A quick update...
I have not had a chance to verify this suspicion, but the current u-boot is configured to use a 2K page size... the 4gb NAND uses a 4K page size...
I am going to try modifying u-boot (its in the config, so you can try...
04/18/2013
- TI 01:06 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- I will be looking in to this very soon and will report back.
cheers
/Tim - MK 12:18 PM Software Development: RE: DDR3 Factory EEPROM Incorrect
- Tim,
Thanks. The system did seem to boot fine from MMC with the MLO/u-boot built from git.
At this point I'm more concerned about programming and booting from NAND on the 512MB board. That doesn't appear to work using the same me... - TI 07:24 AM Software Development: RE: DDR3 Factory EEPROM Incorrect
- Michael
The DDR3 modules require the newer version of u-boot (and MLO). From the output you have listed above, the first (non-working) attempt was using an old MLO.
The old version of MLO does not know how to configure the DDR3 RAM, an...
04/17/2013
- MK 11:10 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- I think I am having the same problem as Kim.
I use similar scripts:
mmc rescan; mw.b 0x82000000 0xFF 0x80000; fatload mmc 0 0x82000000 MLO; nandecc hw 2; nand erase 0x0 0x80000; nand write.i 0x82000000 0x0 $filesize
mmc rescan; mw... - MK 10:25 PM Software Development: RE: DDR3 Factory EEPROM Incorrect
- Just rebuilt u-boot.img out of git, and now my system boots fine.
Still curious about what is in the factory EEPROM and how I can recover if lost. - We received a batch of AM335x boards with 512MB RAM/NAND that appear to have no factory configuration programmed:
@U-Boot SPL 2011.09-00000-g23e81b9-dirty (Feb 24 2012 - 11:15:23)
Texas Instruments Revision detection unimplemented
E...
04/16/2013
- KW 08:36 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- I have programmed both MLO and u-boot with the same results. It appears MLO is not loading & running. Why are the NAND blocks marked bad after flashing MLO and u-boot?
We're mainly have DDR3 (AM3354) CPU modules and ran out of the few... - MW 05:19 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Hi,
Other than the fact that the selected boot mode will try to use the UART first over the NAND (and you aren't programming u-boot, only the MLO -- you'll need to program both into NAND), it's not obvious to me why this is not workin...
04/12/2013
- KW 03:49 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- MW 03:37 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Thanks.
What are your boot jumper settings?
-Mike
- KW 03:34 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Here's my programming steps with NAND OOB info.:
U-Boot# nand bad
Device 0 bad blocks:
00780000
U-Boot# mmc rescan
U-Boot# mw.b 0x82000000 0xFF 0x20000
U-Boot# fatload mmc 0 0x82000000 MLO
reading MLO
39123 bytes read
U-... - MW 03:15 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Could you provide any details on what your FLASH procedure is and what you are seeing when you try to boot?
What bootmode are you configuring for FLASH boot?
This will allow us to reproduce the problem here.
Thanks.
-Mike
- KW 03:12 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Yes, MLO & u-Boot were rebuilt for DDR3 and ran fine on the 3354 w/ DDR3 booting from SD card.
-Kim
- MW 02:45 PM Software Development: RE: Difficulty in flashing MLO and U-Boot to the AM3354 with 512MB NAND
- Errr.... any more details than that???
The MLO and u-Boot images must be updated for the 3354 DDR3 configuration. Are they using the correct version of the MLO and u-Boot?
What is the FLASH procedure [edit] being used?
-Mike
- Customer states that they are having difficulty flashing MLO and U-Boot into the 3354-GX-X38 module. No issues encountered when flashing MLO and U-Boot in the 3359-GX-226 module.
04/11/2013
-
10:57 AM
Software Development: RE: Assigning params from memory in u-boot
- We finally have something that will work, but is not ideal. By using itest we look to see which
of our images is the preferred for booting and then checks the image, and if it is good, unzips
it and jumps. The main issue is that this...
04/10/2013
- JC 03:33 PM Software Development: RE: Assigning params from memory in u-boot
- John C.,
Looks like md might do what you want.
/* Memory Display
*
* Syntax:
* md{.b, .w, .l} {addr} {len}
*/
md.l 80000000 1
80000000: 807fffe0 ....
Unfortunately its output seems rather verbose.
http://sup... - JC 03:21 PM Software Development: RE: Assigning params from memory in u-boot
- John C.
Heres a link to the source code for the itest command.
http://support.criticallink.com/gitweb/?p=u-boot-mityarm-335x.git;a=blob;f=common/cmd_itest.c;h=2a238a43e5d13e56db36665562162eee5e512705;hb=HEAD
It doesn't have any op... -
02:47 PM
Software Development: RE: Assigning params from memory in u-boot
- Tim and Mike,
I found this command that works in testing the contents of memory. Is there any way to get that value into
a param?
if itest.l *80000000 == 80800020; then echo error; fi;
Thanks,
John C. -
08:40 AM
Software Development: RE: Assigning params from memory in u-boot
- Thanks Tim and Mike,
I think that unless it is an easy port of updating/saving the u-boot environment params(like in I need to be
done today), modifying one of the u-boot commands might be the way to go. We also have another l... - TI 08:15 AM Software Development: RE: Assigning params from memory in u-boot
- Not sure if this will do what you really want, but if you load the image from flash (read the max image size into ram, thus avoiding the need to know it beforehand)
you can then run the imi command on it (as it has a u-boot image header... - MW 07:13 AM Software Development: RE: Assigning params from memory in u-boot
- Hi John,
u-Boot doesn't really have much for interpretative type scripting. I don't think you can accomplish this with the stock u-Boot.
Options:
1. You could easily extend the u-Boot crc32 command or add your own to create a e...
04/09/2013
-
10:38 PM
Software Development: RE: Assigning params from memory in u-boot
- Hey Jonathan,
The issue is that we are burning our image into flash from our StarterWare code base. The new
StarterWare image is burned into SPI flash memory location 0x300000 and has a mkimage header. When y... - JC 04:35 PM Software Development: RE: Assigning params from memory in u-boot
- I'm unsure how to do what your looking for. All the references I could find have you set the image size in an environment variable when it is flashed to the spi flash.
Example: http://wiki.atlas-embedded.com/index.php?title=Flashing_Li... -
04:08 PM
Software Development: Assigning params from memory in u-boot
- Hi,
Were are in the final stages of booting our StarterWare image from uboot. Currently we have our compressed image
loaded into SPI flash with a mkimage header attached on the top. I am trying to make a uboot script that will loa...
04/04/2013
-
03:07 PM
Software Development: RE: No unzip in MityArm uboot?
- Thanks Jonathan,
I added #define CONFIG_CMD_UNZIP to the file, rebuilt u-boot and burned it into NAND. So I was able to do the following
from a u-boot prompt and our application runs:
mw.b 0x8C100000 0x00 2E274
sf probe 0:... - JC 12:31 PM Software Development: RE: No unzip in MityArm uboot?
- In the file include/configs/mityarm335x.h you need to insert
_#define CONFIG_CMD_UNZIP_ -
12:10 PM
Software Development: RE: No unzip in MityArm uboot?
- Where is the board header file?
Thanks,
John C. - MW 11:37 AM Software Development: RE: No unzip in MityArm uboot?
- You will probably need to rebuild it and enable the optioncommand by adding a CMD_XXX (CMD_ZIP? would need to check) to the board header file.
Many options / features of u-boot may not be enabled in our default u-boot application in o... -
10:38 AM
Software Development: No unzip in MityArm uboot?
- Hi,
We are running the critical link u-boot version(below) on the MityArm and it appears that there is not a unzip command available. The reason we need it is that the StarterWare image we are running is over 3Mbytes in size and ...