Project

General

Profile

Activity

From 03/11/2013 to 04/09/2013

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...
Anonymous
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...
Jonathan Cormier
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...
Anonymous

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:...
Anonymous
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_
Jonathan Cormier
12:10 PM Software Development: RE: No unzip in MityArm uboot?
Where is the board header file?
Thanks,
John C.
Anonymous
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...
Michael Williamson
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 ...
Anonymous

03/26/2013

MW 07:12 PM PCB Development: RE: VBACKUP Current Draw
Mark,
Great catch! This is certainly acceptable, and we'll likely modify either our u-boot code or kernel code to disable these pull-downs. Both pins are tied externally (BOOT1 to VRTC via 10K, Boot0 to ground), so there is no need ...
Michael Williamson
05:54 PM PCB Development: RE: VBACKUP Current Draw
Mike,
I tested the AM3354 DDR3 module here as well and also saw the ~10uA current draw on VBACKUP.
One other thing I tried worked for me in lowering this current. On your module, it appears that you have the PMIC BOOT0 input tied ...
Anonymous
MW 05:25 PM PCB Development: RE: VBACKUP Current Draw
Hi Mark,
For the DDR2 modules, I'm pretty sure you need the -1C revision for the fix. However, the AM3354 DDR3 module should have the RTC fix already applied. I tested the first prototypes here and was able to see 10 uA on them as o...
Michael Williamson
05:07 PM PCB Development: RE: VBACKUP Current Draw
Hi Mike,
Thanks for the quick response. I believe I have modules covered in the errata. Of the three modules I've tested with, one is an 80-000444RC-1-D and the other two are 80-000509RL-1B.
I also have one of the AM3354 DDR3 mod...
Anonymous
MW 04:08 PM PCB Development: RE: VBACKUP Current Draw
Hi Mark,
We need to confirm what revision of module you have (there was Errata on earlier modules where the VBACKUP draw is quite high). Can you please get the 80- number off the module?
Check the "Module Revision History Page":ht...
Michael Williamson
03:54 PM PCB Development: VBACKUP Current Draw
I am attempting to replicate the VBACKUP current draw information you supplied in the Hardware Design section of the wiki. I have a 3359-GX-226-RC module on the MityARM development board. I removed the battery (which was dead by the wa... Anonymous

03/11/2013

MK 09:02 PM Software Development: RE: Yocto in the future?
Mike,
I *think* the kernel source were coming from Critical Link's git repo - this line is in the linux-mityarm-335x_3.1.bb file:
@SRC_URI = "git://support.criticallink.com/home/git/linux-mityarm-335x.git;protocol=git;branch=${BRAN...
Michael Karasoff
MW 08:26 PM Software Development: RE: Yocto in the future?
Right,
If I read you correctly, you will need to modify the Yocto recipe to use our kernel URL and not Yocto's. This is because the Yocto kernel sources (or anyone else's at the moment, until we upstream stuff) does not have a MACHIN...
Michael Williamson
MK 04:45 PM Software Development: RE: Yocto in the future?
Mike,
Thanks again for your quick response.
In Yocto, I've been setting following environment variables in my local.conf:
GCCVERSION = "4.5%"
BINUVERSION = "2.20.1"
I have used pretty much the same BSP in Yocto as for Angstrom...
Michael Karasoff
MW 07:28 AM Software Development: RE: Yocto in the future?
I don't know why the SDK toolchain isn't working. Are you sure that the .config file was not altered, specifically, the MACHINE type? That would definitely cause problems. Are you using the kernel and u-boot code from our site, or fro... Michael Williamson
MK 07:08 PM PCB Development: Any Experience with VSC8641 PHY?
We are building a system with extended low temperature range (below 0C) and see that the VSC8601 PHY only goes to 0C.
Vitesse also has an 8641 part with extended temperature range, which appears to be quite similar to the VSC8601, exc...
Michael Karasoff
 

Also available in: Atom