Jump to content

nic_steph

EstablishedMember
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nic_steph

  • Rank
    Newbrie
  1. Hi Dave and Pavel, More than 15 months ago "it was somewhere in the background". What is going on? Is the boostc compiler for linux still in your mind? Once again, and just to make sure, I am not talking about IDE but only boostc compiler. Thank you for answering. Stephane
  2. Hi, I used doxygen for automatic doc generation. I am faced to the following problem : When defining in my sourceboostc source code : bit set1@PORTA.3 ; /*setting jumper.*/ Doxygen interprets the AT-SIGN (@) as an internal command, and generates unwanted messages. I am wondering if there is a simple way to avoid the AT-SIGN when defining variables at a specific address. Thank's for cooperation Stephane
  3. It usually happens to me (but surely not to you) if I specify the wrong target device. stephane
  4. Hi Dave and Pavel, Any news about boostc compiler for linux ??? I hope it is still in your mind. As Vista shows up, it would be really a good time to switch to linux. Thanks for your great product. Stephane
  5. Hi Pavel, How do you progress porting BoostC under linux ? rgds Stephane
  6. That will be really fantastic (as your product actually). Thank you so much for your work. Stephane
  7. Dave, A first simple try gave goods results with wine and pp.exe. Unfortunatly I get in trouble with the compiler boostc.pic16.exe. It looks like some DLL problems. But it is really hard for me finding out what is going wrong as far as wine does not give any info. The application simply hangs up. Would you please give me the complete files list needed to compile in command line. What are the dll needed? When I try to import, for example, the asm.dll with : wine regsvr32.exe asm.dll I get the following message : sbigler@bt2-04:~/test_boostc> wine regsvr32.exe asm.dll err:module:import_dll Library MFC42.DLL (which is needed by L"Y:\\test_boostc\\asm.dll") not found Dll asm.dll not found I will really appreciate yours advices. Thank you Stephane
  8. Thank's Dave. I will let you know. Bst rgds. Stephane.
  9. Dear all, Has anyone experienced a way to use boostc in a command line format under linux ? Comments are greatly appreciated. Bst rgds. Stephane
  10. Hi, Tricky point because no specified in DS. But you MUST disable USART serial port (bit RCSTA.SPEN) when using SPI. And when you need USART again simply set it back. Stephane
  11. Hi, Trying to document my boostc-code using doxygen, I am faced to the following problem : With the following : #define PORTC 4 #define RC2 2 /** \brief green_led port pin. */ bit green_led@PORTC.RC2 ; Makes doxygen recognize PORTC as the bit variable instead of green_led. But with : /** \brief green_led port pin. */ bit green_led@4.2 ; Makes doxygen recognize green_led as the bit variable, which is the expected result. It seems that the @ sign means something in ansi-c, but I do not know what. Does anyone could advise me on making doxygen recognize the special @ boostc command ? Anyway thank's a lot for this great product. Stephane
  12. Hi, In your interrupt_low() function, the "if(TMR0IF)" is always true. Instead of : void interrupt_low() { if(TMR0IF) { VFD_Data = !VFD_Data; tmr0l = Timer0LVal; tmr0h = Timer0HVal; } } You should better do : bit tmr0if@INTCON.TMR0IF ; void interrupt_low(){ if(tmr0if){ tmr0_interrupt_handling() ; tmr0if = 0 ; } } St├ęphane
  13. void interrupt_low() { //if((intcon & 0x04) && (intcon & 0x10)) //(TMR0IF) check timer0 interrupt if(TMR0IF) { VFD_Data = !VFD_Data; tmr0l = Timer0LVal; CTemp = tmr0l; tmr0h = Timer0HVal; clear_bit(intcon,TMR0IF); } //Timer0 close //PORTB change interrupt close clear_bit(intcon,TMR0IF); intcon.RBIF = 0 ; } Hi, I am not an expert, but in interrupt_low() function you test TMR0IF. As far as the test if(TMR0IF) is always true, I am not sure this is what you expect. You probably should better do : bit tmr0if@INTCON.TMR0IF ; //timer 0 interrupt flag declaration as a bit variable void interrupt_low(void){ if(tmr0if){ your_tmr0_handling_function() ; tmr0if = 0 ; //clear the flag } } Hope this help. St├ęphane
  14. Hi, I try to establish communication between pic18f4550 and SPI compatible memory. When checking with scope, data are corrected written but the reading stucks on "while(bf == 0)". I have probably made something wrong. I would really appreciate any comment about the following SPI routines : uchar SpiWrite(uchar value){ uchar tmp ; sspbuf = value ; while(bf == 0) ; /*wait for transmission completed.*/ tmp = sspbuf ; /*clear bf*/ if(wcol){ /*in case of bus collision.*/ wcol = 0 ; return 0 ; /*-> bus collision problem*/ } else return 1 ; /*writing OK*/ } /*____________________________________________________________________________*/ uchar SpiRead(void){ uchar tmp ; while(bf == 0) ; /*wait for data received*/ tmp = sspbuf ; return tmp ; } Thank you for helping.
×
×
  • Create New...