Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by c58_4311

  1. dear brie, I think sourceboost people have become too slow. Have they lost the interest in this sourceboost project?
  2. There seams to be some problem in latest version (6.85) of boostbasic when passing string variables in procedures: 'code 0 sub print(a as string) ... ... ... end sub When we assign any string value to the 'a' variable, like print("hello") The value passed to variable 'a' get corrupted. but if we modify the above code into following, we get correct results 'code 1 sub print(a as string) ... ... ... end sub dim x as string(10) x = "hello" print(x) The Code 0 and Code 1, both worked correctly in the perevious version (6.84) of boostbasic.
  3. Good. Waiting for the new release. Boostbasic makes it all simple to control those PIC's.
  4. dear TOM, Please see if you can recieve and send the characters via USART without using interrupt. You can follow he example code written in boostbasic.
  5. Its better to follow the boostbasic example codes for USART routines.
  6. I am taking this post off as the sourceboost people are too busy to give a response to the query! I am sorry.
  7. Dear Pavel, I am sorry that I am going out of the topic here, But I have found that on the web page : http://www.sourceboost.com/CommonDownload/VersionLog.html, the release date of the SourceBoost V6.70 has been shown as 13-March-2006, rather it should be the year 2007.
  8. Dear Dave, As the beta version of the boost basic is expiring today, I have some questions regarding this: 1) Is the sourceboost team going to extend the beta version? 2) If not then when the full version of boostbasic will be available? 3) And what will be the price of this boostbasic? Thanks
  9. The Baud rate calculator is perfect. You have to select the appropriate values from the dropdown box.
  10. Dear Dave, I want to use the 16f5x devices particularly 16F59, but the device is not listed in the source boost. So, how to use these microcontrollers with the boost basic compiler? Thanks
  11. This is just because you are calling the same multiply function in two different threads. Firstly in interrupt thread and secondly in the main() thread.
  12. HA! HA!, yes Dave you have gone too deep but it seems to me that sdujolo has flown too high into the sky never to return to this forum to look at the answers to his queries!
  13. dear sdu... I think that first of all EE_LimitOFF1TempStart+i and EE_LimitOFF1Temp + i do not mean the same thing. Check that.
  14. Ryan, you check this: _INTOSC_OSC_CLKOUT //can be used if you want the RB6 as CLOCK OUT pin _INTOSC_OSC_NOCLKOUT //can be used if you want RB6 as normal I/O pin complete pragma statement that can be used is as follow #pragma DATA _CONFIG, _INTOSC_OSC_NOCLKOUT & _WDT_OFF & _PWRTE_ON & _BODEN_OFF & _CP_OFF Moreover the inbuilt oscillator has two clock rates, 4Mhz and 37Khz. Therefore the PCON register has to be set accordiong to the required clock: pcon.3 = 1 //for 4 MHz pcon.3 = 0 //for 37 KHz
  15. Dear Dave, It helped me a lot, but there are certain queries of mine that need to be answered: With reference to the above example: 1) Is it possible to change the address of the data? I have seen that when I change the address of the data and call statement from 0x200 to any other address, eg. 0x100, etc. The code fails to read the data. Please explain? Actually I want to add the table at the end of the PIC's program memory. What I did is that, I subtracted 7 from the 0x7ff (the pics limit of program memory). But mere changing the addresses didnt helped! 2) Why we add 3
  16. Dave, I am really in a fix here. The need is urgent. My code is here: dim a as byte 'b here should be a table of any ten bytes. Sub main() for counter = 1 to 10 a = b(counter) * 2 // value of the 'b' should be taken from the table next counter Do while 1 Loop End Sub Please give me the assembler code to include in this programe such that the values of the 'b' are declared in the programe memory and read afterwards. I tried to form the tables and reading them back using call statement. But all failed.
  17. Presently I am using the bit old pic 16F72. I have aded the following line to my code: #pragma DATA 0x00CB, 0x41, ox42, 0x43, 0x44 And at the end of the asm file after compilation I get the following: ORG 0x000000C8 _startup BCF PCLATH,3 BCF PCLATH,4 GOTO main ORG 0x000000CB DW 0x0041 DW 0x0042 DW 0x0043 DW 0x0044 END I see that he data has been saved inside the Program Memory. Now, how to call this data in my program? I dont think that some thing like calling the TABLE can be used here! Please help. Thanks.
  18. Dear Wally Thanks for your reply here and also for the reply you gave me to my personal message. I got an answer to my query from Dave. Dear Dave, I am thankfull to you also for your quick answer. But I want some other help from you: 1) I want the code lines in boostbasic/assambly (optemized for speed), that can be used to retrieve the data by using table or memory reads. Thanks
  19. Dear Dave, following are the point that I want to clear: 1) How we can store a constant value in the ROM area i.e. in the programing area of the pic. 2) How to write a DATA TABLE containing the constant values in the ROM and how to retrieve the stored values back. hint: may be the #pragma DATA command will work? But how? Recent edit: I have seen that the following line of code compiles well in boostbasic: dim A as rom byte //declare A as rom byte dim B(12) as rom byte //declare B as an array stored in an array The problem is that how to give val
  20. it looks to me that torsin is always busy in showing the links or so and that too of his codded lines.... I think that the person is asking the straight question, why the people here give links and all insted of just replying in plain...
  21. hello, The PIC16F84 can only use the software USART. So it is advised that you may follow the boostbasic example of designing the software USART.
  22. Dear..... The first thing you should do is download the datasheet pretaining to the PIC microcontroller you are using from www.microchip.com Read the datasheet carefully to know about the architucture of the PIC. It will help you lot.
  23. dear Most probably you are not setting the configuration bits of the PIC. Please check that.
  • Create New...