PBP projects for R/C models

[Kenjones1935]

scalerobotics:

I was hoping I would find in my MicroCode Studio Target Processor pull down menu a reference to the PIC32 that we are using. Nope! Do they sell an appropriate BASIC compiler?

Ken

[ScaleRobotics]

scalerobotics:

I was hoping I would find in my MicroCode Studio Target Processor pull down menu a reference to the PIC32 that we are using. Nope! Do they sell an appropriate BASIC compiler?

Ken

No, they do not. I think you are limited to C, assembly, or StickOS with the 32 bit devices. I thought you were going to try StickOS though? If so, you really don't need to learn too much about the chip. StickOS does most of background stuff for you.

[rmteo]

AFAIK, no one makes a BASIC compiler for the PIC32 (or any other 32-bit MCU for that matter). Your best bet is to go with C which is pretty the de-facto language (not a lot more difficult to learn/use but far more powerful/flexible/reliable).

[ScaleRobotics]

Your best bet is to go with C which is pretty the de-facto language (not a lot more difficult to learn/use but far more powerful/flexible/reliable).

In my opinion, C would be a lot harder for the middle school students to learn. C isn't very readable if you ask me.

For one you have to teach them
{why all the
}
{darn brackets
}
{are all over the place}

Then why the main code is void, but works.

I think StickOS is a bit easier for them for their first intro to micro controllers. But that may be because I don't understand why the brackets are all over the place.

[Kenjones1935]

The .hex file does not load. It says that MAXIMUM must be greater than or equal to zero. In fact it is -7xx or so. Here's the error printout.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '-749' is not valid for 'Maximum'. 'Maximum' must be greater than or equal to 0.
Parameter name: Maximum
at System.Windows.Forms.ProgressBar.set_Maximum(Int32 value)
at PICkit2V2.FormPICkit2.ResetStatusBar(Int32 maxValue)
at PICkit2V2.PIC32MXFunctions.P32Write(Boolean verifyWrite, Boolean codeProtect)
at PICkit2V2.FormPICkit2.deviceWrite()
at PICkit2V2.FormPICkit2.writeDevice(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[Kenjones1935]

I can read the embedded .hex file using READ from the PICkit2. It appears to be all in place save one byte at the very end, byte 'c5'.

I do not understand why I need to attach a USB cable to the PIC32 card when the UART tool in PICkit2 looks like it is supposed to do the same thing. Do I need to push some of the buttons (PROG, RESET, USER) to get this thing started?

KEn

[ScaleRobotics]

I do not understand why I need to attach a USB cable to the PIC32 card when the UART tool in PICkit2 looks like it is supposed to do the same thing. Do I need to push some of the buttons (PROG, RESET, USER) to get this thing started?

I can get this far here, but I do not have one to program, so I can't go to the next step. Can you get to this point, and then your errors come when you try to program it?



I am not sure if the warning is something to worry about or not. But right now you are having so many other errors, let's now worry about my warning yet.

You might be able to use the PicKit2 as your command-line transport. StickOS does allow either usb or serial command-line transports. If that is working for you, then very well. But it sounds like it is not. I have hooked up to a PIC32 with serial on different hardware. But I have never tried it through a Pickit2. The USB is the preferred method, and might give us a clearer indication if we are on the right track.

What did you try to do just prior to getting all those error messages?
1. Did the Pickit ide automatically select the right pic32 device, or did you select it manally?

2. Then did you hit the write button to get all the errors?

I have a pic32 device, so I will try loading it with the latest firmware as well, and see what happens. I might have to try it tonight, as I am late for work already!

Walter

[Kenjones1935]

scalerobotics,
I pulled out the new PICWhacker and plugged in the USB connector. My PC immediately sang its song and gave me the NEW HARDWARE DETECTED GUI.

Under Other Devices it says "CDC RS232 Emulation Demo". Then it asks for a driver. I have installed the .inf file. What is my next step? Also please note that the USB port powers the blue LED on this Whacker. On the first board only the PICkit2 powered that LED.
Ken