No thank you, I've already given it away.
I am rather sad to see you give up so easily. It was only a day between where for first tired to use Swordfish Basic to comiple an ASM program and giving up.
3v0
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
No thank you, I've already given it away.
I looked at that site. Very pricey. But of course I enjoy throwing money away. I bought the Junebug!!!you could of used pic basic pro and it would all most be like programing a stamp
ADCIN
ASM..ENDASM
BRANCH
BRANCHL
BUTTON
CALL
CLEAR
CLEARWDT
COUNT
DATA
DEBUG
DEBUGIN
DISABLE
DISABLE DEBUG
DISABLE INTERRUPT
DTMFOUT
EEPROM
ENABLE
ENABLE DEBUG
ERASECODE
ENABLE INTERRUPT
END
FOR..NEXT
FREQOUT
GOSUB
GOTO
HIGH
HPWM
HSERIN
HSEROUT
I2CREAD
I2CWRITE
IF..THEN
INPUT
LCDIN
LCDOUT
{LET}
LOOKDOWN
LOOKDOWN2
LOOKUP
LOOKUP2
LOW
NAP
ON DEBUG
ON INTERRUPT
OUTPUT
OWIN
OWOUT
PAUSE
PAUSEUS
PEEK
PEEKCODE
POKE
POKECODE
POT
PULSIN
PULSOUT
PWM
RANDOM
RCTIME
READ
READCODE
RESUME
RETURN
REVERSE
SELECT CASE
SERIN
SERIN2
SEROUT
SEROUT2
SHIFTIN
SHIFTOUT
SLEEP
SOUND
STOP
SWAP
TOGGLE
USBIN
USBINIT
USBOUT
WHILE..WEND
WRITE
WRITECODE
XIN
XOUT
6. Structure of a Compiled Program
6.1. Target Specific Headers
6.2. The Library Files
6.3. PBP Generated Code
6.4. .ASM File Structure
7. Other PICBASIC PRO™ Considerations
7.1. How Fast is Fast Enough?
7.2. Configuration Settings
7.3. RAM Usage
7.4. Reserved Words
7.5. Life After 2K
7.6. 12-bit core considerations
8. Assembly Language Programming
8.1. Two Assemblers - No Waiting
8.2. Programming in Assembly Language
8.3. Placement of In-line Assembly
8.4. Another Assembly Issue
9. Interrupts
9.1. Interrupts in General
9.2. Interrupts in BASIC
9.3. Interrupts in Assembler
10. PICBASIC PRO™ / PicBasic /
Stamp Differences
10.1. Execution Speed
10.2. Digital I/O
10.3. Low Power Instructions
10.4. Missing PC Interface
10.5. No Automatic Variables
10.6. No Nibble Variable Types
10.7 No Dirs
10.8 No Automatic Zeroing of Variables
10.9. Math Operators
10.10. [ ] Versus ( )
10.11. ABS
10.12. DATA, EEPROM, READ and WRITE
10.13. DEBUG
10.14. FOR..NEXT
10.15. GOSUB and RETURN
10.16. I2CREAD and I2CWRITE
10.17. IF..THEN
10.18. MAX and MIN
10.19. SERIN and SEROUT
10.20. SLEEP
I do not speak for Blueroomelectronics.
We may have too many cooks stiring the pot just now. There is no clear cut direction.
People with your level of experiance have learned to program using the Junebug with the help of other forum members. Real programming is best done in the company of others. Esp if the others are more experianced. Sitting down with a book often leads to frustration.
We do not often talk about how long it takes to learn to program. For most people this is not a problem because once they get started it is fun and the time is not a problem.
3v0
I would of never seen it if I had not read the picbasic manual. Swordfish is powerful structured language. You have to write some code with it. But I love it nowI suppose the while wend loop looks strange to anyone who is used to goto but proper programming disiplines will make it much easier to move onto other languages like C. It also makes your code easier to follow.
The do until & while wend looked strange to me too.
That would be nice, but a very simple workaround is to just turn on line numbers. BoostC tells you the line number it thinks the error is at - you scroll to it. Often the error is somewhere else and caused by something else, but the error line number is a good place to start.While I am harping I would like to see the people at boostC fix it so you can click on an error in MPLAB and locate the error in the source.
That would be nice, but a very simple workaround is to just turn on line numbers. BoostC tells you the line number it thinks the error is at - you scroll to it. Often the error is somewhere else and caused by something else, but the error line number is a good place to start.