www.coridium.us/forum

What version of BASICtools are you running? In the Help-> About?

I can't to look it now, but i'm using the lastest versión, donwloaded from you web. (date of EXE is 11-jan-18)

That should be BASICtools version 6.00. I have updated to version 6.01, only real change is to force 115 Kbaud when selecting ComXX or USBSER device.

I can't duplicate the com not available except when swapping cards or the similar on my Win7. Can you tell me what sequence you go through to see that?

Assuming you can get the same driver installed as I have (pictured a few posts ago). Then I have a new setupBASIC to install that adds some debug information, so I can see where the com avail error is happening. That BASICtools version is 6.02d

That version we can also experiment with by just changing the small TclTerm.tcl file rather than having to reinstall everything.

basicchip wrote: ↑

Mon Jan 22, 2018 6:56 pm

I found an NXP LPClink2 board, and it also uses a USB_SER connection. NXP published a driver update utility for this and I have loaded that to our site. I would only use this for Win7.
https://coridium.us/files/lpc_driver_setup.exe

Hooray - that driver worked for me with Win-7 (32) Home Premium Service Pack 1
I am running BASICtools 6.02d

that leads on to two things.

I have been trying to get Blinky to flash an LED - failure, it is as if the port is not set to output,
not with IO(LED_PIN) =
or output(LED_PIN)

using
#define LED_PIN 15
output(LED_PIN)
WHILE X<10
print X
X=X+1
print"hello"
IO(LED_PIN) = X and 1 ' IO() sets pin direction and state
print in(LED_PIN)
WAIT(300)
LOOP

the value read in alternates between -1 and 0 but the pin only stays high.
That is the same for LED_PIN set to any from 15 down to 1
....
hello
-1
7
hello
0
8
hello
-1
9
hello
0
However if set to 0, the value read in stays at 0 and as before the pin remains high.
....
hello
0
7
hello
0
8
hello
0
9
hello
0

So what needs to be done to flash an LED?


The other thing is what is this error message supposed to mean?
Error: cannot find channel named ""
BASICtools then can't load any files and the only way to carry on I have found is to close BASICtools and then restart it.

basicchip wrote: ↑

Tue Jan 23, 2018 6:39 am

Can you tell me what sequence you go through to see that?

At start, all time. Drivers are correct, Windows say "LPC USB VCom Port (COM13)", BasicTools , new 6.02 versión, say "stop button", then "toggle reset", and "ser-open2, but error "Com13 not available..."

robots42 wrote: ↑

Tue Jan 23, 2018 4:04 pm

Error: cannot find channel named ""

Same for me.

in the menu I choose "options / serial port / refresh", at this moment, it is shown:
ser-open
ser-close
ser-open
ser-close
stopButton
toggleReset
stopButton
toggleReset

Then, push "RUN", and this is shown:
Analyzing C:/Users/joseba/DOCUME~1/Coridium/Examples/BLINKY.bas
get addresses

and "Error:cannot find channel named" appears

Using TclTerm, and push in "connect" menú:

child killed: segmentation violation
child killed: segmentation violation
while executing
"exec idLPC $::comport"
(menu invoke)

Hello @jepalza,
where did you get this version of BasicTools??

Hooray - that driver worked for me with Win-7 (32) Home Premium Service Pack 1
I am running BASICtools 6.02d

I just downloaded this morning and only got [6.00]
TIA - Olzeke

olzeke51 wrote: ↑

Tue Jan 23, 2018 6:37 pm

Hello @jepalza,
where did you get this version of BasicTools??

Hooray - that driver worked for me with Win-7 (32) Home Premium Service Pack 1
I am running BASICtools 6.02d

I just downloaded this morning and only got [6.00]
TIA - Olzeke

That's not me, it's "robots42", but it does not matter.
Version 6.02D is taken from here:
https://www.coridium.us/coridium/shop/s ... /s01-basic

basicchip, In addition to the LPC11U37, I also have three teensy (3.0, 3.1 and 3.6) and the 3.1 I have with the coridium basic "teensy31.hex" (my personality file). Well, in the "old" version of BasicTools v5.55 where I started programming the teensy 3.1, it works fine, but in the new 6.02D, it tells me the error "Teensy USB serial at Com14 no longer available".
However, in the old Basictools v5.55, the LPC does not work.

I am glad the NXP lpclink driver installer fixed your drivers, I forgot there were 32 bit Win 7 machines out there. Actually my laptop that died a couple months back ran that.

that leads on to two things.

I answered the pinout question at

viewtopic.php?f=2&t=1113