linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Krumboeck <krumboeck@universalnet.at>
To: Brennan Ashton <bashton@brennanashton.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	Gediminas Simanskis <gediminas@8devices.com>,
	linux-can@vger.kernel.org
Subject: Re: usb_8dev: firmware and windows library
Date: Sat, 25 Jan 2014 10:08:04 +0100	[thread overview]
Message-ID: <52E37EF4.3090807@universalnet.at> (raw)
In-Reply-To: <CANQdSEHrxThB8KkmTY8UUqbp6kCdcSAt4-Gu0w1jV08gpHEhxw@mail.gmail.com>

I could lend, but the delivery costs would eat my pocket. ;-)

Maybe I could find some time in the next days.
Are you willing to assist by mail?


regards,
Bernd



Am 2014-01-25 09:29, schrieb Brennan Ashton:
> If there is interest and someone can lend me one of these for a bit of
> time I'm sure I could get this ported over to the GCC arm tool chain.
> I have done a few IAR to GCC ports and besides a few tricks they
> usually are not too bad.
>
> --Brennan Ashton
>
> On 1/24/14, Bernd Krumboeck <krumboeck@universalnet.at> wrote:
>> Hi!
>>
>>
>> Source code from firmware v1.5:
>> https://github.com/krumboeck/usb2can_firmware
>>
>>
>> After some experiments I was able to flash the firmware with dfu-util under
>> linux:
>> https://github.com/krumboeck/usb2can_firmware#flash-the-device-linux-experimental
>>
>>
>> Sadly I don't know the way how to build the firmware with a free tools
>> chain.
>>
>>
>> regards,
>> Bernd
>>
>>
>> Am 2014-01-22 15:46, schrieb Marc Kleine-Budde:
>>> On 01/22/2014 01:58 PM, Bernd Krumboeck wrote:
>>>> May I kindly ask you to send me a diff/patch about the changes, so I can
>>>> update the firmware sources on github.
>>>
>>> A complete new set of sources will do, too. Git will create the diff for
>>> you. :)
>>>
>>> Marc
>>>


  reply	other threads:[~2014-01-25  9:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  9:03 usb_8dev: firmware and windows library "Bernd Krumböck"
2013-01-17 16:32 ` Oliver Hartkopp
2013-01-17 20:24 ` Robert Schwebel
2013-01-18 10:43 ` Uwe Bonnes
2014-01-21 11:50 ` Oliver Hartkopp
2014-01-21 11:57   ` Gediminas Simanskis
2014-01-21 12:19     ` bon
2014-01-21 16:03       ` Gediminas Simanskis
2014-01-21 16:07         ` bon
2014-01-22  5:42           ` Gediminas Simanskis
2014-01-22 12:58     ` Bernd Krumboeck
2014-01-22 14:46       ` Marc Kleine-Budde
2014-01-25  7:04         ` Bernd Krumboeck
2014-01-25  8:29           ` Brennan Ashton
2014-01-25  9:08             ` Bernd Krumboeck [this message]
2014-01-25 15:55               ` Brennan Ashton
2014-01-25 16:55                 ` Oliver Hartkopp
     [not found]                   ` <52E4CEA2.5030407@universalnet.at>
2014-01-26  9:22                     ` Gediminas Simanskis
2014-01-26  9:38                       ` Bernd Krumboeck
2014-01-26 10:04                         ` Gediminas Simanskis
2014-01-26 20:56                           ` Bernd Krumboeck
2014-01-25 11:04           ` Oliver Hartkopp
2014-01-25 11:45             ` Oliver Hartkopp
2015-01-30 21:56           ` Oliver Hartkopp
2015-01-30 22:09             ` Bernd Krumboeck
2015-01-31 10:09               ` Oliver Hartkopp

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=52E37EF4.3090807@universalnet.at \
    --to=krumboeck@universalnet.at \
    --cc=bashton@brennanashton.com \
    --cc=gediminas@8devices.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).