nqBASIC

When you register nqBASIC under Vista or Windows 7 you might get an error message.

"The path to bin/68hc12.ini is denied" or "access denied for 68hc12.ini"

Resolution: You have to be administrator when you are registering nqBASIC, even though you are administrator Vista and Windows 7 is not going to give you full permission to modify certain files under Program Files folder.

You have to go to Program Files/nqBASIC/bin/68hc12.ini file and right click on it and give to that user modify (full) permission on 68hc12.ini file.

After that you can register nqBASIC no problem.

Hi AJ,

That's strange I never seen this error message so far. I have been using XP, Vista and Windows 7 with nqBASIC no problem. Anyway I have some suggestions for you. Quickload.exe is a shortcut software that allows your code to compile and load directly into board in one step.

Please try these two solutions.

1) Please make sure your are using right Com port. Run nqBASIC go to Options/Editor and be sure right COM port is there under QuickLoad Settings (usually Comport 1) Try again Build and Load If you are having same problem please try below solution.

2) Instead of using Build and Load how about use only Build and use uBug12 to load your file to your target. Select Build, if your code compiles then go to Tools menu and select uBug12 A window will open at he below where is the command line ( above Monitor Active)

Type con 1 and press enter (this is your com port if you are using COM port 2 type con 2 It will sat connected Type fbulk and press enter to erase the program in the memory Type fload and press enter,.

Select your s2 file and it will load to your target.

Done Please let me know the result.

My Suggestion to use lower comports (COM2,COM3) sometime you will have problems if you use COM5,COM6, because of USB.

You can change your USB device comport to assign COM2. Before you do that I will suggest to delete nqBASIC totally from your computer manually. (Please save your custom code somewhere else)

1) Go to Start /All programs and nqBASIC and select uninstall nqBASIC ( we had uninstall issue with lower version nqBASIC but it fixed with newer version, however we changed some file names)

2) Go to Start Menu /All Programs and manually delete nqBASIC icons.

3) Go to Program Files and delete nqBASIC folder (you will loose your license information but you can register again)

4) There is a example codes under My Documents/My nqBASIC Projects, please delete this folder( please save any custom code you did somewhere else if you copied them in this folder, we changed some old codes to work properly, I don't want you to leave any old examples there)

Now you can go ahead and install new version again. And Register. Change your USB device virtual Comport

1) Go to My Computer right click, select Properties/Hardware and Device Manager

2) Go to Ports and open the little arrow down, you will see your USB device and assigned Virtual COM port (Your USB device must be connected to your computers USB port to see this, use always same USB port or make sure you are using right COM port)

3) Right Click on USB device and select properties

4) Go to Port Settings and select Advanced ( you will see your Virtual Port number below, assign by your computer)

5) Click drop down arrow and select COM2. If says in use next to it, don't worry go ahead and select. Now you assign COM2 to USB device. Whenever you plug that USB device to your computer it will assign COM2 for that device.

Go ahead and change same COM port under nqBASIC. Go to Options/Editor and change COM port to COM 2

You are done.

Let me know.

Also if you can I would like to see fload error message screen capture.

Hi Aj,

Please copy/paste the text content of the Ubug12 screen and post it here.

"It sounds like it may be an intermittent communication problem."

AJ,

I see the same errors you reported whenever I forget to close my terminal program (TeraTermPro) before doing a Build and Load in nqBASIC.  Also, when I open a project (or create a new one) without setting the COM port number in Options/Editor, I get similar error messages.  Unfortunately, the default comport in nqBASIC is blank, so you have to make sure to set it to something before doing Build and Load.

By the way, you don't need to mess with XON/XOFF, etc.  If you use the Build and Load feature of nqBASIC, the settings are taken care of automatically.

Carl

AJ, I'm glad to hear you've found a way to get back on track! There's one comment I'd like to add, regarding the 'Error: Flash/EEPROM Error' message. The reason you see this message is that the file you are trying to load (NC12demo.s19) includes the serial monitor code in addition to the demo code. Since your module already has the serial monitor code (in a protected block of flash), uBug12 correctly reports the error, because it's unable to program anything into the protected block. And by the time you get that error, uBug12 has already successfully loaded the demo portion of the file, so that's why the demo works correctly. Conclusion: there's nothing wrong with your modules!

By the way, that .s19 file was meant for loading into a blank chip, using a BDM pod-- that's why the serial monitor is included. If you open the .s19 file with NotePad and delete all the monitor's s1 records, the error message will go away. The monitor starts at address 0xF800, so look for the line starting with: S123F800 and delete that line, plus all subsequent lines of s1 records. Be sure to leave the last line of the file intact-- the s9 record is the terminating record, which lets uBug12 know there are no more s1 records to program.

Carl

I have not read thru the above thread in detail, but the following may be pertinant.

Not all USB TO SERIAL ADAPTOR UART's will detect a break ascii code reliably.  I had a similiar problem with communiations with JBUG11 to a 68hc11 system a few years ago, using a laptop and USB TO SERIAL  adapter.  I finally changed the adapter to a different brand, and the problem went away.

From what I remember, the Jbug11 uses a talker to take over control of the MCU, but first the MCU sends a break to the PC host.  The PC host then replies with a $FF then sends the talker.  This break/$ff dialog somehow sets the baud rate correctly for HOST TO MCU communication.  If the USB TO RS232 adapter does not detect a break correctly, this communication does not get established.  

I found a USB-to-RS232 adapter that works. It's from B&B Electronics www.bb-elect.com and is their model 232USB9M-LS. It's pricey at $69, but it works. It is what B&B calls a 'locked port' version which lets you choose which Com port to configure it for during the install; say Com1. Then, regardless of which USB port you plug it in to, it is always set to Com1. Cool!