All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gaëtan Carlier" <gcembed@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UDP packet sender
Date: Tue, 23 Jan 2018 15:02:02 +0100	[thread overview]
Message-ID: <90203e9e-4cad-8d22-2822-01f13ae38244@gmail.com> (raw)
In-Reply-To: <CANr=Z=Z9=0TxzCq78DxFRHiDYdYmr-pxuASbAJuRdzuvnJbMwQ@mail.gmail.com>

Joe,
On 01/23/2018 01:54 AM, Joe Hershberger wrote:
> On Mon, Jan 22, 2018 at 5:28 PM, Gaëtan Carlier <gcembed@gmail.com> wrote:
>> Hi Joe,
>>
>> On 01/22/2018 11:46 PM, Joe Hershberger wrote:
>>> Hi Gaëtan,
>>>
>>> On Thu, Jan 18, 2018 at 4:56 AM, Gaëtan Carlier <gcembed@gmail.com> wrote:
>>>> Hi,
>>>> I would like to implement a new command and submit it to the mailing list.
>>>> The command will have the following format:
>>>> udpsend <destination/broadcast ip> <destination port> <source port> <text to send>
>>>>
>>>> udpsend 255.255.255.255 4040 0 hello world
>>>>
>>>> If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))
>>>
>>> I'd like to understand the purpose / use-case for this command? Maybe
>>> there is a more appropriate way to solve the problem you have instead.
>>>
>>
>> I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC.
>> This is for update on site (by customer).
>>
>> This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.
>>
>> Maybe there is already existing command that I can use from a U-Boot script ?
> 
> I think this is commonly done by enabling netconsole and controlling /
> monitoring progress based on console output sent over UDP.

a) I can/want not enable netconsole when the product is on the network of the customer.
b) Once on customer LAN, everything is DHCP.
c) I don't want to increase load of CPU because updating software on customer's computer has to decode all UDP frames sent by U-Boot while 10% of UDP are really needed (several boards can be on the same network).


> 
> Cheers,
> -Joe
> 
>>>> Where do I have to place my code : cmd or net directory ?
>>>> For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...
>>>
>>> That's probably true. cmd/ would be the appropriate place.
>>>
>>> -Joe
>>>
>>
>> Regards,
>> Gaëtan

Regards,
Gaëtan.

  reply	other threads:[~2018-01-23 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 10:56 [U-Boot] UDP packet sender Gaëtan Carlier
2018-01-22  9:33 ` Gaëtan Carlier
2018-01-22 21:28   ` Lukasz Majewski
2018-01-22 22:46 ` Joe Hershberger
2018-01-22 23:28   ` Gaëtan Carlier
2018-01-23  0:54     ` Joe Hershberger
2018-01-23 14:02       ` Gaëtan Carlier [this message]
2018-02-02 19:13         ` Joe Hershberger
2018-02-06  7:57           ` Gaëtan Carlier

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=90203e9e-4cad-8d22-2822-01f13ae38244@gmail.com \
    --to=gcembed@gmail.com \
    --cc=u-boot@lists.denx.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 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.