Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
ARM Cortex / Re: lpc11c14 can bootloader at higher baudrate
« Last post by VanDan on April 23, 2018, 03:16:46 am »
thank you very much for your support and your efforts  :)

regards
22
ARM Cortex / Re: lpc11xc14 can bootloader at higher baudrate
« Last post by Andy Ayre on April 23, 2018, 12:47:00 am »
That's a bug in the command line version - no reason to support anything other than 100kb.
23
ARM Cortex / Re: lpc11xc14 can bootloader at higher baudrate
« Last post by VanDan on April 22, 2018, 06:43:30 am »
hi andy,

thanks for your fast response.

ok. i understand the reason, why it's not possible in the gui version. but in the commandline version it's already possible to increase it to 250 kbaud. why not to 500kb?

regards
24
ARM Cortex / Re: lpc11xc14 can bootloader at higher baudrate
« Last post by Andy Ayre on April 20, 2018, 01:39:22 am »
No, it's not possible to change it. If we provided an option that doesn't work with the factory bootloader then tech support and frustrated users will increase.

Please email us at support at e s academy dot com for options.

Andy
25
ARM Cortex / lpc11xc14 can bootloader at higher baudrate
« Last post by VanDan on April 19, 2018, 11:43:50 pm »
hello,

we need to run the internal can bootloader of a lpc11c24 at 500kbaud. so we wrote a bootloader which behaves the same way as the internal bootloader except running with 500kbaud instead of the default 100kbaud.


is it possible to set the can baudrate to 500kbaud in flash magic gui? i don't find a way, so i tried to do it with fm.exe but this works only until 250kbaud. trying 500 kbaud displays the following error message:

"Connection failed: comms error (baudrate not supported)"

but the peak pcan pci card supports this baudrate.

i used following directives:

CAN(PEAK PCAN PCI, 500, 0x7D, 1000)
DEVICE(LPC11C14/301CAN, 12.000000, 0)
READSIGNATURE

thanks in advance.

kind regards
26
General Discussion / Re: Stall + Not authorized
« Last post by Andy Ayre on April 17, 2018, 01:15:25 am »
The LED blinking at FM start is a good sign. Did it do that as well as give the "not authorized" error?
27
General Discussion / Re: Stall + Not authorized
« Last post by GGD77 on April 16, 2018, 04:39:07 am »
Hi, will try doing it from my desktop at work. Currently my laptop with 10.9 programs and works correctly and I do not want to mess it up.
In any case, all 3 computers have always (independently from FM version) done the sound of USB connected device and all of them at 1st connection after installing/re-installing the driver have detected the "new device" and have installed the software. I even tried to connect the device before starting FM and vice-versa few times I also tried to reboot the computer after the first connection... until now... no joy

About the LED blinking on the device, it was always solid until I started the FM10.9 while the software was starting the LED started to blink and I thought it was a good sign. In fact, the elusive option to program the chip over the LPClink2 was there and allowed me to program the chip.

I tested one .hex from NXP works as detailed in the specs.
Regards
GGD
28
General Discussion / Re: Stall + Not authorized
« Last post by Andy Ayre on April 16, 2018, 03:27:54 am »
Can you please try this:

Install version 11.00.
Open a command window and go to the FM installation folder
Connect the LPC-Link2 with JP1 removed
Run:

  USBManger --list

What happens? What is output? Do you hear any bings/bongs from Windows? Does the LED on the Link2 start flashing?

Thanks, Andy
29
General Discussion / Re: Stall + Not authorized
« Last post by GGD77 on April 16, 2018, 03:22:33 am »
Hi, thanks for prompt reply

yes 3 different PCs give me the "not authorized" error at start-up. One of them (the 1st I tried) also hides the message in the background and I could not see it/read it. It was appearing briefly on the foreground of the opened windows only when I was killing the main FM process from task manager.

Anyway I tried the "roll-back the date trick" does not work.

RE removing JP1
this was the first thing advised in many forums/tutorials for FM including on the NXP documentation I have tried: no joy... and anyway the device was always recognized in device manager at each test.

Last minute update:

Version 10.9 without changing any settings on the LPC-link2 worked... I just did this trial end error uninstalling and re-installing driver+FM for all the versions I could download. the oldest and my last chance just did it... all the others give me the "not authorized" message

Just now I have successfully erased the NHS3152 chip in the evaluation kit I recently purchased. Later will try to flash one of the other example .hex I know can be downloaded from the NXP page.
Regards
GGD
30
General Discussion / Re: Stall + Not authorized
« Last post by Andy Ayre on April 16, 2018, 01:19:06 am »
Close FM
Remove jumper JP1 from the LPC-Link2
Connect the LPC-Link2 to your PC - make sure it is recognized by checking in device manager
Start FM

Currently FM only checks for attached debug hardware on startup.

Do you have three different PCs giving the "not authorized" error?
Pages: 1 2 [3] 4 5 ... 10