I should be using the sysupgrade image then?

On Wed, Oct 2, 2013 at 12:09 PM, [email protected] <[email protected]>wrote:

> On Wed, Oct 2, 2013 at 3:05 PM, Shawn Lewis <[email protected]> wrote:
> > Progress, thanks! I now have the sysupgrade image, but no factory image.
> I
> > noticed that factory images aren't generated for a few of the other
> ramips
> > boards as well.
>
> Just start the board with the UART connected and pick update the
> system image (choice 2 I think). There is only only image. Make sure
> you have Luci enabled in the build.
>
> If you get tired of entering your IP address. Pick 4.
> printenv
> setenv ipaddr xxxxx
> saveenv
> reset
>
> Messing with choices 8 and 9 on the menu will give you heart burn.
> You can do it but be prepared with a JTAG.
>
> >
> >
> > On Wed, Oct 2, 2013 at 5:24 AM, [email protected] <[email protected]>
> > wrote:
> >>
> >> There are several things broken on the AsiaRF build.
> >> 1) The build system has broken for things with hyphens in the name
> >> 2) The rt5350 ethernet switch will not function unless VLAN tagging is
> >> turned on.
> >>
> >> This patch will get it going again.
> >>
> >> On Wed, Oct 2, 2013 at 12:59 AM, Michel Stempin
> >> <[email protected]> wrote:
> >> > I had a similar issue with another board: it looks like the OpenWrt
> >> > build
> >> > system doesn't like board names containing a dash sign ("-"), try
> >> > renaming
> >> > it.
> >> >
> >> > Le 2 oct. 2013 à 03:30, Shawn Lewis <[email protected]> a écrit :
> >> >
> >> > I'm not getting factory/sysupgrade images for the ramips asiarf
> target.
> >> >
> >> > If I build the default target profile I get all the other ramips
> images.
> >> > If
> >> > I manually select "Asiarf AWM002-EVB" I get vmlinux and other
> precursors
> >> > to
> >> > the actual image, but no flashable factory/sysupgrade images.
> >> >
> >> > Tried from trunk as of yesterday evening PST:
> >> >
> >> > svn://svn.openwrt.org/openwrt/trunk@38267
> >> >
> >> > and
> >> >
> >> > svn://svn.openwrt.org/openwrt/trunk@37561
> >> >
> >> > _______________________________________________
> >> > openwrt-devel mailing list
> >> > [email protected]
> >> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >> >
> >> >
> >> > _______________________________________________
> >> > openwrt-devel mailing list
> >> > [email protected]
> >> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >> >
> >>
> >>
> >>
> >> --
> >> Jon Smirl
> >> [email protected]
> >>
> >> _______________________________________________
> >> openwrt-devel mailing list
> >> [email protected]
> >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >>
> >
> >
> > _______________________________________________
> > openwrt-devel mailing list
> > [email protected]
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >
>
>
>
> --
> Jon Smirl
> [email protected]
> _______________________________________________
> openwrt-devel mailing list
> [email protected]
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to