Project

General

Profile

Activity

From 02/10/2013 to 03/11/2013

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

03/08/2013

MK 05:35 PM Software Development: Yocto in the future?
Up until a week or so ago, we were developing MityARM-335x code under Angstrom as a holdover from work done on Beaglebone w/ Angstrom. We built the filesystem, kernel, and uboot using recipes posted on the Critical Link Wiki, and - once... Michael Karasoff
02:39 PM Software Development: RE: MityArm in u-booting from SPI flash
Thanks Tim,
How hard to you think it would be to merge the MityArm changes for u-boot into the latest mainline u-boot?
John C.
Anonymous
TI 02:28 PM Software Development: RE: MityArm in u-booting from SPI flash
John
While the omap l138 based mity SOMs do boot from SPI (NOR) flash, we have not tried to do so on the AM335X based SOMs.
In fact, the current AM335X based SOMs can not boot from on-board flash due to pin mux constraints. You should ...
Tim Iskander
02:12 PM Software Development: MityArm in u-booting from SPI flash
Does Critical Link plan to support booting from spi flash? We would like to begin the process of migrating the booting
over to spi flash and were hoping you guys might have it ready to go already (fingers crossed...) We understand that
...
Anonymous

02/27/2013

MK 07:57 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
I take back the comment about console-image build not working. I can build it just fine, and the issue is most certainly user error on my part.
Michael Karasoff
MK 07:15 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
After the latest angstrom update, building the console-image program no longer works, but the systemd-image works fine.
Also, I still can't figure out how to get the MLO to build. Using the one shipped with the dev kit seems to work ...
Michael Karasoff

02/20/2013

MW 08:54 AM Software Development: RE: Where is the real spi_xfer() function located for MityArm in u-boot?
Cheat:
Look for .o files.
-Mike
Michael Williamson
08:53 AM Software Development: RE: Where is the real spi_xfer() function located for MityArm in u-boot?
Mike,
Thanks for the info. It is difficult to trace which files are included in the build using
the am335x_evm.h file's #defines.
-John Conover
Anonymous
MW 08:36 AM Software Development: RE: Where is the real spi_xfer() function located for MityArm in u-boot?
John,
For the MityARM-335x family, the file is:
drivers/spi/omap3_spi.c
-Mike
Michael Williamson
MW 07:50 AM Software Development: RE: Typo in rs485_test code
Hi Ian,
It depends on the version of the compiler you are using and where it is getting it's kernel headers from.
The TI tools from their 05.03.02.00 SDK, what we used to run the test, have a definition of the their serial_rs485 st...
Michael Williamson

02/19/2013

IM 07:03 PM Software Development: Typo in rs485_test code
Thank you for putting up the great resource at:
http://support.criticallink.com/redmine/projects/armc8-platforms/wiki/Driving_RS-485_transceivers
But there is a typo in rs485_test.tar. I believe "#define gpio_pin padding [1]" should...
Ian Martin
02:06 PM Software Development: Where is the real spi_xfer() function located for MityArm in u-boot?
Hi
I've been unable to build u-boot on my Ubuntu 12.04 or 11.xx Virtual machines so I was wondering which u-boot file contains the spi_xfer() function that is compiled in the MityArm build of u-boot? I've searched looking at file...
Anonymous

02/14/2013

11:06 AM Software Development: RE: Booting StarterWare image from NAND
Tim,
Now it makes sense. I never did get the u-boot to build so I did not know the process of making
the MLO. Now that you say it I remember seeing that command used to build an image with ECC. So if
we had made a plain MLO ...
Anonymous
TI 10:56 AM Software Development: RE: Booting StarterWare image from NAND
John
My understanding (which may be confused!) is that it doesn't matter so much if you use SW or HW ECC, but that you flash the image using the same ECC mode that you use to read it. So if you are using HW ECC when you flash the image ...
Tim Iskander
10:42 AM Software Development: RE: Booting StarterWare image from NAND
Hey Tim,
We have referenced that page before, the problem is that there is no mention of ECC being "Required" for any
MLO image past a certain revision to boot. As with a lot of TI documentation on the 3359, certain things ar...
Anonymous
TI 10:30 AM Software Development: RE: Booting StarterWare image from NAND
John
check out http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User's_Guide
cheers
/Tim
Tim Iskander
10:07 AM Software Development: RE: Booting StarterWare image from NAND
Mike,
Here is our update. We have our board booting from NAND with no changes to the MLO image. We changed the SYSBOOT[9] to ECC
and our system boots with no issues. Is there any TI documentation/notes that would explain exactl...
Anonymous

02/13/2013

09:25 AM Software Development: RE: Booting StarterWare image from NAND
Hey Mike,
Are jumper mode is 00100b so it is serial first, MMC and then NAND. Experimenting with your board we got your board to
boot from NAND but we had to remove the header from the MLO image (first 0x200 bytes.) We also ...
Anonymous

02/12/2013

MW 05:42 PM Software Development: RE: Booting StarterWare image from NAND
Hi John,
Have you adjusted your boot-strap jumpers to select a mode the uses NAND? What option have you selected?
The "C"'s you are seeing is the ROM based boot code looking to be booted from the UART. This means (if the UART is ...
Michael Williamson
05:05 PM Software Development: RE: Booting StarterWare image from NAND
Are we supposed to have a specific MLO for booting from NAND. We have seen it mentioned
that older versions would not boot in NAND, but we have pulled the latest. Do we
need a different one?
Thanks,
John Conover
Anonymous
11:32 AM Software Development: RE: Booting StarterWare image from NAND
Just the "C"'s you see at the bottom of the serial log. Anonymous
JC 11:30 AM Software Development: RE: Booting StarterWare image from NAND
When you say it doesn't make it into MLO does anything get printed to the console after power up? Jonathan Cormier
11:26 AM Software Development: RE: Booting StarterWare image from NAND
Hey Tim,
I'm still having issues getting the system to boot from NAND. I've pulled
the latest MLO and uboot images from your site and run the commands below. This should
be the MLO and uboot images into NAND, but when we b...
Anonymous

02/11/2013

12:38 PM Software Development: RE: Booting StarterWare image from NAND
Tim,
I'm in the process of putting our image into NAND and noticed that when I
save the ENV variables it prints out:
Environment size: 1704/65532 bytes
U-Boot# save
Saving Environment to NAND...
Erasing Nand...
Erasing at ...
Anonymous
 

Also available in: Atom