Check out the blog post with an updated TclTerm.tcl
https://www.coridium.us/coridium/blog/a ... s-in-linux
Search found 1053 matches
- Tue Dec 27, 2022 7:16 pm
- Forum: Software issues
- Topic: Linux TclTerm baud rate
- Replies: 3
- Views: 135
- Mon Dec 19, 2022 6:16 pm
- Forum: Software issues
- Topic: Linux TclTerm baud rate
- Replies: 3
- Views: 135
Re: Linux TclTerm baud rate
Still don't have a Linux machine up, wsl on windows doesn't run wish (don't know how to configure Xwindows for it) I ordered a power supply for my HP mini, which has Mint on it. Power supply misplaced in the move. You might have to figure out the command line sequence to configure the baud rate for ...
- Thu Nov 24, 2022 6:39 am
- Forum: Software issues
- Topic: BT - Function calling
- Replies: 7
- Views: 6775
Re: CALLing an #included FUNCtion
Would really need more context to answer this. The example you site compiles and runs correctly. There is a difference between a subroutine defined by LABEL1: ... RETURN and one defined by SUB LABEL2 ... ENDSUB The LABEL1: ... RETURN can never have parameters, so CALL LABEL1 () would be illegal And ...
- Tue Nov 22, 2022 12:34 pm
- Forum: Software issues
- Topic: DOWNTO, Help file
- Replies: 1
- Views: 97
Re: DOWNTO, Help file
STEP is an optional keyword in FOR statements, true of all BASICs I have seen. If you have a STEP in the statement the compiler expects a value, and in your case the compiler flags it as an error
If there is no STEP keyword then 1 is assumed.
would be the proper syntax
If there is no STEP keyword then 1 is assumed.
Code: Select all
FOR i = 3 DOWNTO 0
- Sun Oct 30, 2022 10:56 am
- Forum: Software issues
- Topic: simple Interrupt for PROstart
- Replies: 6
- Views: 385
Re: simple Interrupt for PROstart
The details of these interrupts are in the NXP user manual. To change to GPIO0.3 -- INTERRUPT SUB INT_GPIO0 GPIO0_IC = (1 << 3) ' clear interrupt on pin 3 and SUB ON_GPIO0(rise_edge, dothis) ' Setup MUST be done before enabling the interrupt GPIO0_IE = (1 << 3) ' interrupt on GPIO0.3 if rise_edge th...
- Fri Oct 28, 2022 7:01 pm
- Forum: Software issues
- Topic: simple Interrupt for PROstart
- Replies: 6
- Views: 385
Re: simple Interrupt for PROstart
Updated the file to change the label to GPIO0.1 for LPC1114
Also program correctly for rising edge interrupt (default was falling edge).
Also program correctly for rising edge interrupt (default was falling edge).
- Wed Oct 26, 2022 7:44 pm
- Forum: Software issues
- Topic: simple Interrupt for PROstart
- Replies: 6
- Views: 385
Re: simple Interrupt for PROstart
I will add this to the next release.
This uses the BOOT pin (GPIO0.1) which can be toggled by BASICtools. (I should change the label from EINT0 to GPIO0.1)
Source for
This uses the BOOT pin (GPIO0.1) which can be toggled by BASICtools. (I should change the label from EINT0 to GPIO0.1)
Source for
- Sun Oct 23, 2022 12:51 pm
- Forum: Software issues
- Topic: Linux compile, LPC4330
- Replies: 1
- Views: 215
Re: Linux compile, LPC4330
My Linux machines are still in storage, but looks like the issue is a typo in the LPC43xx.bas file
Fixing the first line, fixes it in Windows, most likely in Linux as well. The git has been updated and will roll out in future release.
Corrected file attached here
Fixing the first line, fixes it in Windows, most likely in Linux as well. The git has been updated and will roll out in future release.
Corrected file attached here
- Thu Jun 16, 2022 4:07 pm
- Forum: Your first forum
- Topic: ARMstamp communication problem on WinXP
- Replies: 8
- Views: 1731
Re: ARMstamp communication problem on WinXP
OK let me take that back, lpc_driver_installer did not work, but pointing the Win driver installer to the lpcopen_example_windows_usb_drivers DID work
And I can talk to and load programs on the ARMstamp with that.
Will load up a blog article and link to those files. (too big to include here)
And I can talk to and load programs on the ARMstamp with that.
Will load up a blog article and link to those files. (too big to include here)
- Thu Jun 16, 2022 3:58 pm
- Forum: Your first forum
- Topic: ARMstamp communication problem on WinXP
- Replies: 8
- Views: 1731
Re: ARMstamp communication problem on WinXP
Found a WinXP SP3 laptop from a friend. I tried lpc_driver_installer, it failed for me to install.
I doubt there is an NXP supported driver for VCOM and WinXP, so we can't help you there, but ARMstamps run on Win 7 and beyond, Linux, iOS, and Raspberry Pi.
I doubt there is an NXP supported driver for VCOM and WinXP, so we can't help you there, but ARMstamps run on Win 7 and beyond, Linux, iOS, and Raspberry Pi.