Yes, strangely that happened with mikroe basic, not with picbasic![]()
Yes, strangely that happened with mikroe basic, not with picbasic![]()
But still, MIKROE guys are really nature error. IDE is full of bugs. A little example:
I started up IDE. By default, it opens last saved project. Ok, I close it.
Now I started new project, write some code and compile. Everything is OK.
Now I opened some previously saved project, make some changes, compile and want to flash. BUT, the flasher will flash the .hex image from the new project which I started when launching IDE. And to flash the current active program image, I have, EACH TIME, MANUALLY PROVIDE flasher with the correct hex file.
Is not this silly?
Another bug: "clean up project folder" does not works. While it says "files were deleted", actually, no file being deleted. Also GLCD font creator can't save the file. It says it saved, but no file being saved.
Hi, Curious one
Here is not the place to complain about another product you have difficulties with ...
I saw You were on MkB forum @ 10.15 ( French hour ... ), so you were on the right place THERE to complain .
Your posts there show once more you didn't had opened neither the Pic Datasheet nor the IDE Manual or Help file ...
Once more it's no use to complain your IDE doesn't work by itself ... just make the effort to learn your lesson !!!
said gently ... this kind of thread has NO INTEREST for PicBasicPro Forumers ... as the fault is totally yours.
Learn your lessons and you will be allowed to criticize AFTER lesson learned
Alain
Last edited by Acetronics2; - 1st March 2013 at 09:26.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
I believe, it's my duty, to warn others about the bad product, being falsely advertised as good one.
And the errors I've listed above, has nothing to do with my knowledge of MCUs. It's totally fault of that IDE developers.
At the same time, I'm checking picbasic pro. And also, this IDE seems to be written upside down. Why no ability to configure default path for output .hex files? There are couple of other bugs, too. I'll list them later.
If you feel most things are upside down then you probably live on the Southern hemisphere.
Here's my first code with picbasic pro up and running. It does output variable PWM which I use for led dimming.
Sure, code is written really bad, but, at least it works. I've used included BUTX3 sample as basis:
I believe, first two lines of code are irrelevant for PIC16F628A, but at least it works...Code:CMCON = 7 ' PORTA to digital OPTION_REG = $7f ' Enable PORTB pull-ups TRISB = %11001111 ' Set PORTB.4,5 (LEDs) to output, rest to input A var byte mainloop: PORTB = 0 ' Turn off LEDs ' Check any button pressed to toggle on LED If PORTB.7 = 0 Then ' If 1st button pressed... PORTB.5 = 1 ' Turn on 1st LED A=A+1 if a=255 then a=a-1 HPWM 1,A,1000 Endif If PORTB.6 = 0 Then ' If 2nd button pressed... PORTB.4 = 1 ' Turn on 2nd LED a=A-1 if a=1 then a=a+1 HPWM 1,a,1000 Endif Pause 15 ' Pause 2mS Goto mainloop ' Do it forever End
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Bookmarks