3 replies to this topic

[nakchak]

I am wondering if there is a way to flash multiple netduino's at once, i.e. I would like to be able flash 10 or more devices with a custom firmware and software images at once, to avoid having to flash each device individually, which in production volumes (multiples of 100) would take a long time to do. I assume a customised build of MFDeploy would be needed? as i can see multiple devices enumerated in the drop down list but it seems i can only flash one device at once? Nak.

[Chris Walker]

Hi Nak,

I am wondering if there is a way to flash multiple netduino's at once, i.e. I would like to be able flash 10 or more devices with a custom firmware and software images at once, to avoid having to flash each device individually, which in production volumes (multiples of 100) would take a long time to do.

I assume a customised build of MFDeploy would be needed? as i can see multiple devices enumerated in the drop down list but it seems i can only flash one device at once?

When you plug in a second Netduino, it should show up as "Netduino###_1". If you plug in several Netduinos at once, you should be able to flash several boards simultaneously.

If you're just flashing your app, it should be pretty quick. But parallel is always nicer, I agree

Chris

[CW2]

I am wondering if there is a way to flash multiple netduino's at once, i.e. I would like to be able flash 10 or more devices with a custom firmware and software images at once, to avoid having to flash each device individually, which in production volumes (multiples of 100) would take a long time to do.

I guess if you can connect many Netduinos to one PC, you can launch MFDeploy for each device, with the device identifier passed on command line. Also, you may be able to further automate that by parsing MFDeploy List output and extract USB ports - unfortunately, I cannot check that right now, but I assume the list contains identifiers of attached devices.

Regarding simultaneous 'parallel' flashing, I don't think this is achievable through USB (*), you'd probably need to use the microcontroller's Fast Flash Programming Interface, with suitable adapter, not sure it works when the micro is already soldered on a board. Another option could be to ask the vendor to flash your custom image during manufacturing

EDIT: (*) I mean by physically sharing the USB connection. Customizing MFDeploy to enable selection of multiple devices will be probably done via separate 'flashing' threads, which is basically the same as launching multiple MFDeploy applications (if it is not single-instance only).

[nakchak]

Hey Chris

When i deploy the UI is effectively locked out i would have to run several instances of MFDeploy to flash several devices at once, although that may not be such a bad thing i guess.

Think i shall have a look at the feasibility of producing a parallel flashing app ideally something which can chain SAM-BA into the mix as well, as unfotunatly i need to to flash a customised firmware (and matching bootloader) to enable the SPI CS line to toggle after each ushort is sent, as well as perform some rudimentary error checking of the data i receive from a MAX3100 SPI UART chip i use in the in my application, that said the mod is fast and can reliably drive the chip to establish a 256k baud serial connection even though the protocol i interface to is 9600baud based.

A somewhat unrelated question but what was the rational of disabling the default behaviour of the SPI0 CS line behaviour (which is to toggle the cs after each byte/ushort is sent) of the AT91SAM7X512 used by the netduino's in the stock firmware? As their have been several threads, and Mario's hard ware work around to address the issue of having CS staying at the same level through out the entire transaction. Obviously if you choose to use a pin other than D4 for your CS line you don't get the default behaviour. Just curious as the reasoning behind the decision is all.

Nak.