Activity
From 01/11/2013 to 02/09/2013
02/08/2013
- MK 02:43 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Mike,
Thanks for the tip on checking the git commits. I was able to build the Angstrom console image.
Here is how I got there:
@rm -rf setup-scripts/sources/meta-mitydsp@
Changed layers.txt line to this:
@meta-mitydsp,git:/... - MK 11:43 AM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Mike,
Thanks much!
For what its worth, we aren't looking for long term support on this. If we can just get a working Angstrom baseline from CriticalLink, we can manage the layer internally moving forward.
Thanks again,
Michael - MW 11:23 AM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- OK [edit] Michael [sorry]. The Git commit levels for all of the builds are included somewhere in the reference filesystems on our files download tab, as I recall. I don't have them handy at the moment, but yes, that should in theory wo...
- MK 11:19 AM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Mike,
Thanks for looking into this.
Could I solve my problems by referencing the commit where the Angstrom overlay worked in layers.txt?
RE TimeSys - we already have a prototype system and software up and running with Angstro... - MW 08:18 AM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Hi Mike,
I just did an update on the Angstrom git tree and I am getting this error as well. Something has changed on the Angstrom side since I last did the build and clearly there is a problem with our overlay. I will look into it.
...
02/07/2013
- MK 07:07 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Correction:
I ran the bitbake with additional debug *MACHINE=mityarm335x bitbake -v -D -D -D -D console-image*
I run @MACHINE=beaglebone bitbake -v -D -D -D -D console-image@ prior to adding the meta-mitydsp layer as a baseline. ... - MK 06:26 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Mike,
Thanks for your quick reply!
Unfortunately, when I run *MACHINE=mityarm335x bitbake console-image* I still get the errors during the Angstrom parse. I've replicated this on a fresh Ubuntu 12.04 install and on the 10.04 Virtu... - MW 06:52 AM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- I was suggesting to build the mityarm335x machine, or else you won't pick up the u-Boot and Kernel from our git repository that has the needed mods to support the module. What I was suggesting is to build a standard filesystem image, su...
-
03:20 PM
Software Development: RE: Booting StarterWare image from NAND
- Tim,
Yes we do have a plain u-boot from you. So if I understand this correctly the MLO, uboot and boot options
are already in NAND. So by putting our image into NAND (say at where the linix kernal would be) and then
modifying th... - TI 03:10 PM Software Development: RE: Booting StarterWare image from NAND
- John
booting from NAND is really just a change to your uboot environment settings. If you have a stock u-boot from Critical Link, you should see a number of different boot options.
booting from nand would be something like
nand read.i... -
02:48 PM
Software Development: Booting StarterWare image from NAND
- Hi,
We currently have our MityArm based system (MityArm CPU module, custom board)booting
into uboot and then loading out StarterWare based image from the sd card by setting the
bootcmd to:
mmc rescan; fatload mmc 0 80000000 emb...
02/06/2013
- MK 11:08 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- I was able to recover my BeagleBone and BeagleBoard build environments by removing restoring the *EXTRALAYERS ?= ""* entry in conf/bblayers.conf. Yay! I suppose there is something in the MityArm layer that is causing this trouble.
... - MK 10:03 PM Software Development: RE: Critical Link Kernel integration w/ Angstrom/OpenEmbedded
- Hello,
I am also trying to build Angstrom according to the tutorial on the wiki: http://support.criticallink.com/redmine/projects/armc8-platforms/wiki/Installing_Open_Embedded
I've been successful in the past building and Angstrom ...
01/27/2013
- AS 04:40 PM PCB Development: RE: RGMII PHY Electrical Specification
- MityArm (335x) SOM supports two RGMII interfaces and both interfaces support only 3.3V logic levels
01/24/2013
- What is the electrical specication of the RGMII interface from the MityDSP? Is it 3.3 or 2.5V LVCMOS?
01/16/2013
-
03:21 PM
Software Development: RE: DHCP is erratic in uboot
- Just to let you know that if you set the phy register 9 (1000Base-T Control) to 0x0000 (turn off advertisement
for 1000 full/half duplex), then DHCP will work in uboot. I'm still looking into DHCP at gig settings.
John C. -
02:41 PM
Software Development: RE: DHCP is erratic in uboot
- Thanks Tim,
I've been beating my head against a wall for a bit so hopefully there will be something good
there.
John C.
- TI 02:37 PM Software Development: RE: DHCP is erratic in uboot
- John
There is quite a long discussion on the TI e2e site about this very subject. I suspect some of it will be pertinent to your situation.... specifically the parts about the recv phy timings.
http://e2e.ti.com/support/dsp/sitara_arm1... -
02:26 PM
Software Development: DHCP is erratic in uboot
- We are having problem getting DHCP to work consistently on are board that uses the
the Mity AM3359 module (and our KSZ9021RL Phy). Port 0 failing is normal but when
port 1 finishes autoneg, I see the DHCP requests go out on the line an...