Comment #1 on issue 50 by robhamerling: RAM specification in device files. http://code.google.com/p/jallib/issues/detail?id=50
Report from Kyle: 1. The problem [PICs without shared RAM] will only manifest itself in some multi-byte (if I recall, three or more byte) add and subtract. 2. As long as the compiler knows these [_pic_isr_w and _pic_accum] can be accessed without needing to change the bank bits it doesn't matter exactly how the region is declared. Comment by RobH: 1. For PICs without shared RAM 16F873[A], 16F874[A]: The JalV2 docs wil mention the restriction. Note: These PIC have shared RAM, but not in the sense of JalV2: RAM which is accessible in *all* banks. 2. For PICS with only shared RAM: 12F629,12F675,16F630,16F676: In stead of specifying in the device files all RAM as shared RAM the locations for _pic_isr_w and _pic_accum will be defined as shared and the rest as unshared RAM. This resembles the 'normal' RAM configuration (combination of shared and unshared RAM) best. Will be effectuated as of version 0.0.54 of the Dev2Jal script. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
