Basic Micro Studio - Changes in Beta from Build to build

[kurte]

Hi Guys, I wish I could take full credit for it , but the changes actually started by Dale. Here is the first message talking about it in in the New Manual posting (page 5) on the Basic Micro forum.

Kurt,

Im on the HSERIN, HSEROUT, HSERIN2 and HSEROUT2. Its a mess to say the least. The ARC32 and ATOMPro 40 are to become the dominant platforms for Basic Micro. So I need to make these commands much simpler. We are going to break them. I did a search on Jim’s forums and it seems theres only a handful of people using them. The changes I’m about to make wont break the functionality so all the things you asked Nathan for will remain intact. I just need to make it simpler for the average user.

All the changes will be documented in the new manual and the release text file.

Now I fully admit that after that I suggested, it would sure be nice if there was not HSEROUT and HSEROUT2… So personally I am happy with these changed

[kurte]

This is just an FYI - Nathan had not put in the new format of the hserstat command in the previous postings. I emailed him awhile ago about the new format and thought I should share the information.

@AcidTech

HSERSTAT mode arguments now include the choice of uart 1 or uart 2.

modes 0 to 7 are the same as before but are specifically for uart1. Then 8 to 15 are the same modes but for uart 2.

As HserStat was not in some of the previous manuals, Here is the information I had on it…

The HSERSTAT command lets you check the status and/or clear the hardware serial port buffers. Before using this command you must use the SETHSERIAL command (see page 122) to set the correct baud rate.
Syntax
hserstat funct{,label}
funct is a value from 0 to 6 that determines the function of the hserstat command according to the following list:
Value Function
0 Clear input buffer
1 Clear output buffer
2 Clear both buffers
3 If input data is available go to label
4 If input data is not available go to label
5 If output data is being sent go to label
6 If output data is not being sent go to label
label is an optional argument (use with values 3 – 6) that specifies the destination jump address.

Kurt

[km6vv]

What’s the cut-in release version for ENABLEHSERIAL going away, and the new Hserial 1, etc. to be available?

Thanks!

Alan KM6VV

[kurte]

@KM6VV

What’s the cut-in release version for ENABLEHSERIAL going away, and the new Hserial 1, etc. to be available?

1.0.0.36 which was then changed to 2.0.0.0

Kurt

[km6vv]

That was fast. Thanks!

It’s amazing how many programs I have lost recently due to switching between projects. I had a BBII or the ARC-32 running on my Micromouse 'bot, then I went to work on the 'quad. I’m still not sure which board I was working with (maybe the BasicAtomPro?) but it took quite a while to get rover code working again on the ARC32 with the RoboClaw.

It might have helped if I’d had the PS2 connected; the code stalls just before I was trying to ferret out the right serout vs. hserout statement right after that in Init. Oh well!

My Micromoose should work for a rover (Lantronix project).

I need to take better notes!

Alan KM6VV

[acidtech]

The 2.0 change was because we just added the new library system which will be a fairly major addition. If anyone wants to submit their own projects for the library please send them to [email protected].

The 2.0 release is when teh ENABLEHSERIAL/HSERVO compile time directives have need removed(wont break your code though if you leave them in) and the new HSERIAL syntax is available(whill break your old code, need to change the hserin,hserout and SetHserial commands).

[km6vv]

Just a thought, but what if we had a key word (reserved word) analyzer program (like LINT?) that we could run against a BAS file? Maybe we’d specify the rev and the compiler used, or it could just identify all the reserved words, and comment on which revs/compilers the commands/words could be used by.

Get the picture? I dig up an old file (or even a new one I’m working on), run BM-LINT against it, and it tells me where the “evolving” words are, and identifies which compilers can compile the file. Or maybe which words are “wrong” for the compiler I want to use. Could even suggest the command and it’s proper syntax. Seems like the new studio (only had a short time to try it out last night) does some of that. Clever!

Alan KM6VV

[km6vv]

Since I’m here…

Just changed code in “Rover Roboclaw” program from old format to new for the 2.0 compiler.

Compiles for 'Pro, not for Basic Atom. Compile never ends (although I can get into editor). Must exit Studio and restart.

ENABLEHSERIAL
;SetHSerial H9600,H8DATABITS,HNOPARITY,H1STOPBITS	; pre 2.0
;hserout "Creepy RoboCrawler",cr,lf]  	

SetHSerial1 H9600,H8DATABITS,HNOPARITY,H1STOPBITS	; 2.0 syntax
hserout 1,"Creepy RoboCrawler",cr,lf]  

Alan KM6VV

[kurte]

Hi Alan,

I think I read that for the Nano and maybe the Atom, the only valid thing is the baud rate.

Try:

SetHSerial1 H9600 hserout 1,"Creepy RoboCrawler",cr,lf]
Note: This should work on the Pro as well as all of the others are optional…
Kurt

[km6vv]

Hi Kurt,

Nope!

Still fails to complete the compile, no error messages.

For some reason, I had the BBII with the BasicAtom bolted up on the 'bot, so tried a compile for that. I should probably get more 'PRO and ARC-32’s; but I like the old PIC parts!

Alan KM6VV

@kurte

Hi Alan,

I think I read that for the Nano and maybe the Atom, the only valid thing is the baud rate.

Try:

SetHSerial1 H9600 hserout 1,"Creepy RoboCrawler",cr,lf]
Note: This should work on the Pro as well as all of the others are optional…
Kurt

[fallentine]

@kurte

Hi Alan,

I think I read that for the Nano and maybe the Atom, the only valid thing is the baud rate.

Try:

SetHSerial1 H9600 hserout 1,"Creepy RoboCrawler",cr,lf]
Note: This should work on the Pro as well as all of the others are optional…
Kurt

Correct, the Atom and Nano only need baud rate.

By the way, the nano’s hserial is broken in 2.0.0.0, it’s working for the most part in 2.0.0.1, but i had a bunch of problems with it, that i was unable to narrow down.
2.0.0.2 is out there if you know how to get it, i installed it, but i havent really given it a try yet.

[kurte]

Yep - I only remember half of the post by Nathan on Sep 27th:

Found two things. One my bug and one yours.

SetHSerial1 on Atom/Nano was causing an infinite loop when compiling. Don’t know what happened there. I must have accidental hit ctrl-z after testing but before the release compile and it deleted the one line of code I added to increment past the SetHSerial1 during the preprocessor parsing.

The other problem is your syntax is wrong. Atom/Nano still only have the baudrate argument. None of the other arguments are available on Atom/Nano. Thats why on the AtomPro I made all the extra arguments optional. So your code should be:

…
I’ll make a new release and post it tomorrow.

I don’t think tomorrow happened yet
Kurt

[km6vv]

No real rush, nor any real problem. I hate following releases too close, unless, of course, that’s my job!

I can use other commands, or drop back to a known (old) compiler.

It will be great when we can compile for any of the products with a single compiler! OK, so one won’t get ALL the features on the smaller chips, but that’s live-able.

Funny, I don’t remember reading that post talking about the “infinite loop”.

Thanks!

Alan KM6VV

Edit: If one exits like I had to do for above problem, that MBasic32 stays running (like 50% for the first one). “Bail out” a few times, and you have SEVERAL MBasic32 programs hanging about! (Guess what that does to the operation of your other tasks!

[kurte]

AcidTech/Nathan posted a new release yesterday: 2.0.0.3

Added support for BOE board RS-232 model dev boards. BOE board USB model devboards is supported but requires a module update(removing a diode and replacing a cap with a resistor).
The new reset/boot connection code used in Studio will allow a small cap to be in-series on the reset pin. This will allow you to leave the reset pin connected in some situations you couldn’t before. On some systems the reset pin would be held in reset. The in-series cap will only allow changing signals through.

Fixed new style port/pin variables so they work on all processors.

I am also hoping that the fix for the Atom and Nano Hanging while compiling Hserial stuff is in this build as well…

Kurt

[kurte]

Warning: I believe I am having problems with HSERIAL on Arc32 not outputting at the correct baud rate on this new build…

I will report on BM website and to Nathan…

Kurt

[kurte]

@kurte

Warning: I believe I am having problems with HSERIAL on Arc32 not outputting at the correct baud rate on this new build…
I will report on BM website and to Nathan…

AcidTech/Nathan posted a new release this morning that appears to fix this problem. : 2.0.0.4

He found a problem in his C code where he had something like: if (a=b) instead of if (a==b)…

Kurt

[km6vv]

Yeah, that’ll get 'ya!

Alan KM6VV

@kurte

He found a problem in his C code where he had something like: if (a=b) instead of if (a==b)...

Kurt

[kurte]

Nathan did another release (2.0.0.5) update yesterday that allowed the SSC-32 emulator on the Arc32 to compile…

[kurte]

New build: BasicMicro Studio 2.0.0.6

@Acidtech

Fixed HSerial on Nano/Atom
Changed ASIN/ACOS floating point functions on AtomPro. ASIN/ACOS now have the full range(-1.0 to 1.0) and produce results accurate to .00002(based on testing).

Please post any bug reports in the appropriate forum groups. Thanks.

Kurt

[kurte]

New build: BasicMicro Studio 2.0.0.7

@AcidTech

Updated Serin/out commands to support >115200bps. Tested and working upto 156250bps.

- I rebuilt my Phoenix Arc32/SSC-32 with baud rate to SSC-32 set to i115200 and it works!!!

Kurt