On Fri, 04 Oct 2013 14:10:18 -0400
Rich Webb <webb.ra@example.net> wrote:

> Works fine. I don't believe that the "Demonstrator" license permits
> redistribution but the protocol is well documented in the app notes
> and you have a known-working app to check against.

If you run Linux (or it may be buildable in Windows as well; I haven&rsquo;t
ever tried), recent versions of dfu-util support the STM32F4 series&rsquo;
USB bootloader.
-- 
Christopher Head

On Sun, 6 Oct 2013 11:36:26 +0000 (UTC)
Uwe Bonnes <bon@hertz.ikp.physik.tu-darmstadt.de> wrote:

> David Brown <david.brown@removethis.hesbynett.no> wrote:
> 
> > I'll look into the LPC families.
> 
> Have also a look at the STM32. They all have USART Bootloader in ROM,
> many parts also DFU bootloader. On F2/3/4 and L1, you can also reach
> the bootloader without setting the  boot pins by using SYSCFG_MEMRMP
> and doing a core-reset (no system reset!).
> 
> Bye
> 

STM32F4 series also bootloads over CAN, as well as USB and serial. And
yes, you can both jump into the bootloader yourself from application
code as well as setting a level on a pin while powering up to get into
the bootloader unconditionally.
-- 
Christopher Head

Grant Edwards <invalid@invalid.invalid> writes:

> I didn't phrase my posting well.  I've found that Gentoo has ebuilds
> for pretty much all the software I need to use.

I guess I have to agree with that. Android development stuff from Google
and Steam from Valve is just installable the same way as anything
else.

> Maybe things in binary-distribution land have improved, but my recent
> brief expeditions into Ubuntu and RH/CentOS territory haven't given
> any indication that's the case.

Maybe you would like Sabayon instead in the binary-distribution land?
Gentoo based but software is prebuilt. Can still use emerge for stuff
that isn't.

On 2013-10-04 18:03, David Brown wrote:
> Does anyone have recommendations for Cortex M3/M4 microcontrollers with
> a bootloader in ROM?  We use a number of Freescale Kinetis devices, but
> there is no ROM bootloader - programming is through either JTAG or the
> EZ-Port (basically treating the chip like an SPI flash device).  We have
> an application where a UART-based bootloader would be very useful, and
> having it in ROM would save a lot of effort and production time (like
> the TI msp430 microcontrollers).  There are vast numbers of M3/M4
> devices available - I am looking for recommendations for ones with a
> simple and clear bootloader protocol.
>
> Thanks,
>
> David
>
I think you find that the Atmel Cortex part can be programmed using the 
USB device port using SAM-BA.

BR
Ulf Samuelsson

Roberto Waltman <usenet@rwaltman.com> writes:

> Cross posting to sci.electronics.design
>
> What linux distros do techies like?

I have Debian in my home desktop and NAS, Sabayon in my personal
laptop. I picked Sabayon for the laptop to get new stuff quickly since
it's a rolling distribution. So small weekly updates instead of a huge
one twice a year like Fedora or never like Mint...

For chip design work (at work) I've usually used RHEL or CentOS since
that's what the tools officially support.

On Tue, 08 Oct 2013 09:32:46 -0400, Roberto Waltman <usenet@rwaltman.com>
wrote:

>Cross posting to sci.electronics.design
>
>What linux distros do techies like?
>
>R.
>
>
>Roberto Waltman wrote:
>>David Brown  wrote:
>>> ... I use Linux for most of my work and play. 
>>
>>Just curious - Which Linux distribution do you use?
>>
>>I used Ubuntu for several years, but I'm not sure I want to follow
>>Canonical in whatever path they want to take it.
>>
>>Thinking of switching to Scientific Linux (Fedora) when I get back to
>>"work and play." (Crunchbang Linux is also in the run.)

I have used openSuse for quite a while.  If you want better EDA tools
fedora may be best.  *buntu make me uncomfortable about security.  Maybe
it is time to try Debian or a derivative again.  I prefer package
(dependency) manager style Linuxes currently, though i can and will at
need install from source.

?-)

On a sunny day (Fri, 11 Oct 2013 10:20:22 -0400) it happened Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote in
<52580926.1060500@electrooptical.net>:

>On 10/11/2013 05:08 AM, Jan Panteltje wrote:
>> On a sunny day (Thu, 10 Oct 2013 23:36:01 -0400) it happened Phil Hobbs
>> <pcdhSpamMeSenseless@electrooptical.net> wrote in
>> <52577221.403@electrooptical.net>:
>>
>>> That's interesting.  You and I seem to be having an interated failure to
>>> communicate on some of the other issues, though.  It's hard enough
>>> future-proofing one's computing installations without having the tools
>>> decide that they won't cooperate.
>>>
>>> Cheers
>>>
>>> Phil Hobbs
>>
>> mm is anybody stopping you from writing a version of fdisk that does stick
>> to your concept of how partitions should be divided?
>>
>> Linux has always been, at least for me, 'if it does not exist write it'.
>> or sometimes 'I cannot be bothered to learn this ..i*t' so I will write my own app.
>>
>> Old Dutch saying (and I am sure it is universal):
>> One should not look a given horse in the mouth.
>>
>> And 'I want Linux to be compatible with Microsoft <whatever>' is NOT on MY list of priorities.
>>
>> As to 'future proof', not one new kernel I tried had the same bugs as the previous ones.
>> And the driver API changes, video4linux, the DVB driver, OSS , Alsa, etc etc,
>> changes every year or moon phase or sunspot,
>> have not figured out when exactly ..
>> Meaning you have to rewrite your apps every time in many cases,
>> including all scripts (command line flags change...).
>> Now YOU did chose Linux, so get used to it.
>>
>> All that, mind you, I ONLY run Linux, except for an old win98 but that seems to not understand
>> the new graphics card, so its screen is now so messed up... should delete it..
>> but has my scanner driver....
>> Not that I use the scanner, I use the camera...
>> Anyways future proof what year did you have in mind?
>> In the computer world 6 month is already an unknown,
>> 6 years ? 60? Maybe we all have a chip implant by then, and only need to _think_ to partition our brains.
>>
>
>In other words, if one has any complaints about Linux, it's proof 
>positive that one is a lazy asshole.  And here I thought that the 
>communication failure was accidental.

The communication failure was possibly the channel that told you Linux does everything, and you believed it.

BTW if you dont want some scripts to call some routine (program) (say fdisk),
rename the orignal  mv fdisk not_today_fdisk  , make a small script called fdisk that returns OK (exit 0),
and see what happens (if anything).
I do things like that sometimes to 'stay in control', you can make it log to with 'echo'.
Sometimes it helps, and sometimes it does not, modifying the source a bit does the same.
Yes it is hard work, I spend a full day programming asm, it is hard work too, especially if you want zero errors.
Maybe it will erase all your disks, YMMV
;-)



 

On 10/11/2013 05:08 AM, Jan Panteltje wrote:
> On a sunny day (Thu, 10 Oct 2013 23:36:01 -0400) it happened Phil Hobbs
> <pcdhSpamMeSenseless@electrooptical.net> wrote in
> <52577221.403@electrooptical.net>:
>
>> That's interesting.  You and I seem to be having an interated failure to
>> communicate on some of the other issues, though.  It's hard enough
>> future-proofing one's computing installations without having the tools
>> decide that they won't cooperate.
>>
>> Cheers
>>
>> Phil Hobbs
>
> mm is anybody stopping you from writing a version of fdisk that does stick
> to your concept of how partitions should be divided?
>
> Linux has always been, at least for me, 'if it does not exist write it'.
> or sometimes 'I cannot be bothered to learn this ..i*t' so I will write my own app.
>
> Old Dutch saying (and I am sure it is universal):
> One should not look a given horse in the mouth.
>
> And 'I want Linux to be compatible with Microsoft <whatever>' is NOT on MY list of priorities.
>
> As to 'future proof', not one new kernel I tried had the same bugs as the previous ones.
> And the driver API changes, video4linux, the DVB driver, OSS , Alsa, etc etc,
> changes every year or moon phase or sunspot,
> have not figured out when exactly ..
> Meaning you have to rewrite your apps every time in many cases,
> including all scripts (command line flags change...).
> Now YOU did chose Linux, so get used to it.
>
> All that, mind you, I ONLY run Linux, except for an old win98 but that seems to not understand
> the new graphics card, so its screen is now so messed up... should delete it..
> but has my scanner driver....
> Not that I use the scanner, I use the camera...
> Anyways future proof what year did you have in mind?
> In the computer world 6 month is already an unknown,
> 6 years ? 60? Maybe we all have a chip implant by then, and only need to _think_ to partition our brains.
>

In other words, if one has any complaints about Linux, it's proof 
positive that one is a lazy asshole.  And here I thought that the 
communication failure was accidental.

Cheers

Phil Hobbs

-- 
Dr Philip C D Hobbs
Principal Consultant
ElectroOptical Innovations LLC
Optics, Electro-optics, Photonics, Analog Electronics

160 North State Road #203
Briarcliff Manor NY 10510

hobbs at electrooptical dot net
http://electrooptical.net

On a sunny day (Thu, 10 Oct 2013 23:36:01 -0400) it happened Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote in
<52577221.403@electrooptical.net>:

>That's interesting.  You and I seem to be having an interated failure to 
>communicate on some of the other issues, though.  It's hard enough 
>future-proofing one's computing installations without having the tools 
>decide that they won't cooperate.
>
>Cheers
>
>Phil Hobbs

mm is anybody stopping you from writing a version of fdisk that does stick
to your concept of how partitions should be divided?

Linux has always been, at least for me, 'if it does not exist write it'.
or sometimes 'I cannot be bothered to learn this ..i*t' so I will write my own app.

Old Dutch saying (and I am sure it is universal):
One should not look a given horse in the mouth.

And 'I want Linux to be compatible with Microsoft <whatever>' is NOT on MY list of priorities.

As to 'future proof', not one new kernel I tried had the same bugs as the previous ones.
And the driver API changes, video4linux, the DVB driver, OSS , Alsa, etc etc,
changes every year or moon phase or sunspot,
have not figured out when exactly ..
Meaning you have to rewrite your apps every time in many cases,
including all scripts (command line flags change...).
Now YOU did chose Linux, so get used to it.

All that, mind you, I ONLY run Linux, except for an old win98 but that seems to not understand
the new graphics card, so its screen is now so messed up... should delete it..
but has my scanner driver....
Not that I use the scanner, I use the camera...
Anyways future proof what year did you have in mind?
In the computer world 6 month is already an unknown,
6 years ? 60? Maybe we all have a chip implant by then, and only need to _think_ to partition our brains.

David Brown wrote:

>Does anyone have recommendations for Cortex M3/M4 microcontrollers with
>a bootloader in ROM?  We use a number of Freescale Kinetis devices, but

I forgot to mention the Infineon XMC4000, no "recommendation" since I
don't use/know it, but as far as I see, it has a serial bootloader in
ROM.

Oliver
-- 
Oliver Betz, Munich
despammed.com is broken, use Reply-To: