From: Gary Thomas <gary@mlbassoc.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm] kobs-ng tool?
Date: Thu, 14 Apr 2016 14:42:13 +0200 [thread overview]
Message-ID: <570F9025.6050502@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKr4Mt9rvG=1mwCi=PtK5oyPPEBRAEu25MUpt1nyVfnZZg@mail.gmail.com>
On 2016-04-14 14:39, Otavio Salvador wrote:
> On Thu, Apr 14, 2016 at 3:30 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2016-04-13 16:13, Otavio Salvador wrote:
>>>
>>> On Wed, Apr 13, 2016 at 11:04 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>
>>>> On 2016-04-13 15:38, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> On Wed, Apr 13, 2016 at 8:48 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>>>
>>>>>>
>>>>>> I have a recipe (don't recall where I found it, it was a while ago)
>>>>>> for kobs-ng_3.0.35-4.1.0.bb
>>>>>>
>>>>>> The tool created by this recipe doesn't seem to work with my i.MX6UL
>>>>>> target and indeed the NAND image created does not come close to
>>>>>> matching
>>>>>> what the FreeScale manufacturing tool creates using the same U-Boot
>>>>>> image.
>>>>>>
>>>>>> Does anyone know where I can find a more recent tool (I tried the
>>>>>> cited website and ended up in Russia!)? I really need to get this
>>>>>> working with my i.MX6UL target.
>>>>>
>>>>>
>>>>>
>>>>> imx-kobs ;-)
>>>>
>>>>
>>>>
>>>> Sadly, that's not building for my target.
>>>>
>>>> MACHINE = "imx6ulevk"
>>>> meta = "master:778121ab844af623a215430ba579a5fb3947928b"
>>>> meta-fsl-arm = "master:cec4c47e33979631e85e2c933cea5182da61ad82"
>>>>
>>>> Error log attached. Any ideas?
>>>
>>>
>>> Not on top of my head.
>>>
>>> Maybe someone inside NXP might help?
>>>
>>
>> I generated a patch for this problem but the recipe (and sources)
>> are scant on details. Anyone know where I should send the patch
>> upstream, and/or discuss issues with this tool?
>
> Update the recipe and add the patch; it is likely to be taken for next
> BSP release.
>
Sure, I'll do that.
Is there no way to contact upstream? There are no pointers in the
recipe nor the sources.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-04-14 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 11:48 [meta-fsl-arm] kobs-ng tool? Gary Thomas
2016-04-13 13:38 ` Otavio Salvador
2016-04-13 14:04 ` Gary Thomas
2016-04-13 14:13 ` Otavio Salvador
2016-04-14 6:30 ` Gary Thomas
2016-04-14 12:39 ` Otavio Salvador
2016-04-14 12:42 ` Gary Thomas [this message]
2016-04-13 14:15 ` Gary Thomas
2016-04-14 18:14 ` Lauren Post
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570F9025.6050502@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.