Date: Wed, 14 Nov 2018 10:27:48 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Stanislav Galabov <sgalabov@gmail.com> Cc: freebsd-mips@freebsd.org Subject: Re: Building a new version for my WiTi board Message-ID: <47b96cf8-d596-2373-cd7b-bff6cd92843c@digiware.nl> In-Reply-To: <c8d3246e-f367-d3d9-7046-28d881f2946b@digiware.nl> References: <b8b2e91a-afd3-60c5-6ad4-3fbac9011718@digiware.nl> <CAF19XBK_JZ8OPLZuqTH%2BUGAhvB2r90FyeN48qq9z7JaYT0TbYw@mail.gmail.com> <09b2150d-ef55-c032-59c4-4b218a03f186@digiware.nl> <e12386f8-5e52-3adb-e8ee-ea276b3ecfde@digiware.nl> <D593CDCF-2074-452D-8ED2-448E2A49555A@gmail.com> <c8d3246e-f367-d3d9-7046-28d881f2946b@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/11/2018 10:17, Willem Jan Withagen wrote: > On 14/11/2018 08:52, Stanislav Galabov wrote: >> Hi Willem, >> >> Can you try this kernel: >> https://www.dropbox.com/s/t1wevprzlsfegr0/kernel.uboot?dl=0 >> >> What I notice in your build process is that after your objcopy step >> you use kernel instead of kernel.bin in the mkimage step. Try using >> kernel.bin produced in the objcopy step instead as input to mkimage >> and that should work. > > That would be a typo, then. > I think I had the same mistake the previous time I tried to build. > I'll first try to fix my build, and then try your kernel. That was indeed my standard mistake. Last time I did this I ended up attaching a small harddisk, using the system as a regular computer with HD. This WiTi-board I would like to use as a embedded device, and load a firmware image that includes the file system. Is there a (set of) script that will do that. I guess so, given that we now have ARM images in the FreeBSD download. It might even be a option for make? --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47b96cf8-d596-2373-cd7b-bff6cd92843c>