Forums

Start application from a board without reset

Started by hamdibouafsoun May 23, 2008
----- Original Message -----
From: "Paul Curtis"
To:
Sent: Friday, May 23, 2008 2:49 PM
Subject: RE: [lpc2000] Start application from a board without reset
> Hi,
>
>> > Hey, you've been evaluating since 10/2007, if you plonk down your
>> cash I'm
>> > sure I'd be much more receptive!
>>
>> Dear Paul,
>> Why don't you have a secured licensing system for your software,
>> instead of fishing on the list for expired license user?
>
> I didn't say this guy is using cracked software--in fact, we have extended
> eight evaluation keys to him. All I said was that I would be much happier
> if he plonked some cash down because he's been evaluating for a long time.
> Clearly, "evaluation" is not the issue here.
>
> Everything get cracked. You know it does. We've been round that question
> before on this list. Simply put: my effort is better spent developing
> software for paying customers than fighting a losing battle against those
> that won't.

The rather expensive PCB software I use is dongleised (HASP dongle), and
that got cracked a few years ago because the license key they used was too
short. The key was made much longer and no-one has managed to crack it,
AFAIK.

I've never really liked dongles, but the HASP one (USB) is very unobtrusive,
doesn't cause users any problems (I run the users group for the software)
and works very well.

Leon

An Engineer's Guide to the LPC2100 Series

----- Original Message -----
From: "Paul Curtis"
To:
Sent: Friday, May 23, 2008 2:49 PM
Subject: RE: [lpc2000] Start application from a board without reset
> Hi,
>
>> > Hey, you've been evaluating since 10/2007, if you plonk down your
>> cash I'm
>> > sure I'd be much more receptive!
>>
>> Dear Paul,
>> Why don't you have a secured licensing system for your software,
>> instead of fishing on the list for expired license user?
>
> I didn't say this guy is using cracked software--in fact, we have extended
> eight evaluation keys to him. All I said was that I would be much happier
> if he plonked some cash down because he's been evaluating for a long time.
> Clearly, "evaluation" is not the issue here.
>
> Everything get cracked. You know it does. We've been round that question
> before on this list. Simply put: my effort is better spent developing
> software for paying customers than fighting a losing battle against those
> that won't.

Rowley is very liberal with their licenses, often donating free licenses to
deserving causes. For instance, I've been helping to develop an ARM-based
medical system (for measuring red blood cell deformation) at a university in
France, and Rowley gave them a license.

Leon
In Keil Vision there is an option to autostart the mainloop after flashing.
It 's located in Project - options for target - debug - Run to main().

No idea about Crosswork though...

Greetz,

Sander Van Schoote, student with a thesis based on a LPC2148.

Paul Curtis schreef:
>
> > I'm using Olimex lpc2294 with rowley Crossworks , i've programmed my
> > application correctly using my JTAG interface ,
> >
> > now i want that my application turned in power up without using reset
> > every time
> >
> > Someone Knows how ?
>
> Hey, you've been evaluating since 10/2007, if you plonk down your cash I'm
> sure I'd be much more receptive!
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
>
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
>
>
> 16:44
>

Hi Leon,

> > Everything get cracked. You know it does. We've been round that
> > question before on this list. Simply put: my effort is better spent
> > developing software for paying customers than fighting a losing battle
> > against those that won't.
>
> The rather expensive PCB software I use is dongleised (HASP dongle),
> and that got cracked a few years ago because the license key they
> used was too short. The key was made much longer and no-one has managed
> to crack it, AFAIK.

You don't need to crack the key, you just need to know where to alter the
executable so the dongle looks like it's present and correct. Short of
making part of the app code execute on a piece of controlled hardware inside
the dongle, you don't have a lot of choice--things *will* be cracked.
Googling "Pulsonix crack" gets you to some hairy (or not-so-hairy) sites
that will deliver you a nice copy of the software.

One way of making CrossWorks secure is to only work with our own hardware,
but that defeats the object: users can't then evaluate our software without
forking out for hardware. So, it won't work. If we only sold expensive
hardware then we could give away our software, like some other companies in
the same game.

> I've never really liked dongles, but the HASP one (USB) is very
> unobtrusive, doesn't cause users any problems (I run the users group for
the
> software) and works very well.

Yeah, and you go away on a trip and forget to take it. Or you need to be
plugged into a network. Or something else. I hate them but some of our
customers demand them. Again, we don't make much of an effort to make our
software a fortress, we're not interested in the customers that are
reluctant to pay, just the ones that want to manage their licenses and
usage.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

* STARTUP_FROM_RESET
*
* If defined, the program will startup from
power-on/reset. If not defined
* the program will just loop endlessly from
power-on/reset.
*
* This definition is not defined by default on this
target because the
* debugger is unable to reset this target and
maintain control of it over the
* JTAG interface. The advantage of doing this is
that it allows the debugger
* to reset the CPU and run programs from a known
reset CPU state on each run.
* It also acts as a safety net if you accidently
download a program in FLASH
* that crashes and prevents the debugger from
taking control over JTAG
* rendering the target unusable over JTAG. The
obvious disadvantage of doing
* this is that your application will not startup
without the debugger.
*
* We advise that on this target you keep
STARTUP_FROM_RESET undefined whilst
* you are developing and only define
STARTUP_FROM_RESET when development is
* complete.