Firmware Update

[basicchip]

I have a trial firmware updater built and am looking for guinea pigs. So if you want to upgrade now to the latest which runs at 115Kb rather than 19.2Kb, or just are bored with football. This is setup for a number of freedownloads

http://www.coridium.us/nobs/setup115kb.exe

[olzeke51]

ONE down - more to go
started firmupdate from Vista program menu
selected BASICchip [note all choices were auto-selected]
{{ I had the ARM BASIC board -- with the built usb<->serial
Normal--Coridium Board/dongle & COM4 were auto-selected
'
stated 'done' with no errors
[there was a comment about:
RecordType 05 not yet implemented - ignorred ?]
pipe 12200 bytes loaded
{{I have a screenshot.jpg of all the (feedback) results
'
fired up the BT and it gave me gobble-de-gook,[old baud]
selected the new baud rate and voila!
'
shutdown and restarted with a good connection
Have a good day!!

[olzeke51]

2nd one down -- maybe one more to go -- the datalogger
'
tested the SuperPRO - kernel 8.36a
"CPU = 1756, Flash Map = 1756
pipe 16397 bytes loaded
Warning: data not aligned to 32 bits, padded (length was 400D, now 4010)"
'
loaded BLINKY just fine at the new baud rate
'
thanks for the firmware update
Olzeke51

[olzeke51]

Vista computer, my first big program with SuperPro
Might be an issue:
'
' PRINT "nOW THE ROBOT WILL START IT'S THING BASED UPON ???"
' GOSUB YesNo
'
'
' LOOP 'from the Main label
'
'
Problem: the <STOP> button isn't stopping this GOSUBed FUNCTION
'
FUNCTION YesNo
'**** will need to redo with M0 and keypad for 54102
'waits for a Y/N; no default Y = 1, N = 2
'
while RXD(0) = -1
inkey = RXD(0)
if inkey = 49 then
YN = true
goto lablYN
endif
if inkey = 50 then
YN = false
goto lablYN
endif
PRINT 'Not a 1 (for yes) OR a 2 (for no)'
loop
'
lablYN:
TXD(0) = BEL ' beep
return YN
'
'
END FUNCTION

below is a portion of the screen info
'
-1 \
-1 > **printing the result of RXD(0)*1
-1 /
6004172 **printing the ctrl-g and the TIMER as it now has timed out [debug info]
' *** exited the if/then that called the above RXD(0)*1 function
nOW THE ROBOT WILL START IT'S THING BASED UPON ???
' *** now in a GOSUBed while loop waiting for RXD(0) see snippet above
stopButton *RED letters **clicked on the <STOP> button
Diagnostics.... y/N ***printed the ctrl-g of the above function
' ***and then LOOPed back up to the Main: While loop
' *** and printed the prompt and GOSUBed to the RXD(0)*1 function
8603749 top of the RXD(0)*1 function prints the TIMER value
toggleReset *RED letters - printed by itself
ÿ * usuall this character
'
Welcome to ARMexpress Family BASIC Demo ** part of Main: before the While loop
Diagnostics.... y/N ** start of While loop, printed the prompt and GOSUBed to the RXD(0) function
1002743 ** top of the RXD(0) function prints the TIMER value
-1
-1 **printing the result of RXD(0)
'
the RXD(0)*1 function [AS I labelled it in my comments]
is different but similar to the above snippet
[and is looking for a 1 or 2 or CR]
'
lousy formatting when it gets transferred to this post!!!!

[basicchip]

Use the Code formatting for code, list might be good for screen captures, I've never used it.

As for Vista, you are out there in left field all by yourself. I never had a Vista machine, skipped it to Win7 which was pretty good, converted over to Win10 now, but I still have WIn7 and WIn8 machines for now.

[olzeke51]

okay - I see the Code button
As for Vista, you are out there in left field all by yourself
does that imply that Vista isn't an approved platform??
'
I don't think Vista has a thing to do with the issue that I think I see....
the <STOP> button is generating BOTH a
' Stopbutton and a 'toggelReset'
(and there is a time delay between them to do several lines of Basic code)
'
end result - I can't STOP my program!!!
SuperPro kernel is reported at 8.36a
Gary

[basicchip]

Last I checked, a failsafe STOP can be done by exiting BASICtools and restarting BASICtools.

If you can narrow down what in your program fails to STOP, I'll take a look. But for most things it works fine, mucking with the UART can cause this as you have cut off the communication path from BASICtools.

[olzeke51]

Okay, I think I get your gist..
since I'm looping on RXD(0), the <STOP> being sent by BT is not being
interpreted by the kernel. If it was in a another type of function,
or perhaps a DEBUGIN statement....then it would work.
'
tested it - and it sends both 'stop & reset'
AND the program stopped in the middle of a do-nothing while/loop.
Thanks for your astute observation.
Gary