just wondering po.. ano po ba ang pagkakaiba-iba ng hi-tech c, css c, proton c, mikroc when it comes to creating a program for pic?
For the case of mikro c, for the pic 16 series, the compiler does not do this automatically, you have to manually set the bank select bits.
halu.. about this:mikro c po kasi gamit ko for pic16.. uhm, hindi ko lang po sure pero sa iilang program po na nagawa ko, never ko pa po manually s-in-et yung bank select bits. though working naman po yung programs ko.. i wonder kung meron lang talagang versions na hindi pa automatic yung pagseselect ng bank.. i guess yung version na gamit ko, automatic na din..
MikroC can only access banks 0 and 1 automatically. If your program uses 129 bytes or more of RAM, it will need to access banks 2 ( and bank 3). This is the hassle with MikroC, you will get a warning regarding IRP bits (bank select bits) must be manually set. Sometimes a lot of unknown variables specially the ones used by library functions will cause this warning if all the ram locations in bank 0 and bank 1 are used up. Then you are forced to manually locate your own declared ram variables on bank 2 and bank 3 to make room for the ram used by the library function which are automatically set to use banks 0 and banks 1 only. This is the hassle in coding as each time you need to call your function or variables, you must manually set the IRP bank select bits.I started learning on MikroC and when I encountered that limitation I switched to Hitech C. In MikroC, you cannot directly compare ROM and RAM variables ... you have to manually copy rom variables into RAM and do a RAM to RAM comparison.
im using pic16F628A meroon po ba ditong circuit pra sa training board at downloader medyo nhhrpn po kxe ako mag eagle cad
MikroC can only access banks 0 and 1 automatically. If your program uses 129 bytes or more of RAM, it will need to access banks 2 ( and bank 3). This is the hassle with MikroC, you will get a warning regarding IRP bits (bank select bits) must be manually set. Sometimes a lot of unknown variables specially the ones used by library functions will cause this warning if all the ram locations in bank 0 and bank 1 are used up. Then you are forced to manually locate your own declared ram variables on bank 2 and bank 3 to make room for the ram used by the library function which are automatically set to use banks 0 and banks 1 only. This is the hassle in coding as each time you need to call your function or variables, you must manually set the IRP bank select bits.