AVR C Runtime Library - Patches: patch #6352, Far pointer library
You are not allowed to post comments on this tracker with your current authentication level.
patch #6352: Far pointer library
Submitter: | Carlos Lamas <carloslamas> | ||
Submitted: | Fri 21 Dec 2007 02:40:29 PM UTC | ||
Category: | None | Priority: | 9 - Immediate |
Status: | Ready For Test | Privacy: | Public |
Assigned to: | arcanum | Open/Closed: | Open |
( Jump to the original submission )
Mon 26 Sep 2011 09:29:49 PM UTC, comment #9: |
Jan Waclawek <wek> |
Mon 26 Sep 2011 08:43:32 PM UTC, comment #8:
|
Georg-Johann Lay <gjlayde> |
Wed 03 Aug 2011 09:06:02 PM UTC, comment #7: The _PF functions in the respective binary libraries are broken, and they ever were, since the've been added to avr-libc in 1.7.0.
|
Jan Waclawek <wek> |
Wed 30 Jun 2010 12:50:06 PM UTC, comment #6: The xxx_PF() functions modify the RAMPZ register, but on XMegas with EBI, RAMPZ influences also LD/LDD/ST/STD, making code after using xxx_PF() to access unintended data memory "pages".
|
Jan Waclawek <wek> |
Thu 03 Jun 2010 03:23:06 PM UTC, comment #5: Adding one more function, memcmp_PF().
|
Jan Waclawek <wek> |
Wed 22 Oct 2008 04:50:15 AM UTC, comment #4: Carlos,
|
Eric Weddington <arcanum>![]() ![]() |
Thu 07 Aug 2008 02:20:25 PM UTC, comment #3: Hi there
|
Moritz 'morty' StrĂ¼be <cmorty> |
Thu 03 Jan 2008 12:54:07 AM UTC, comment #2: This is a good point. I've considered this at the time of writing the functions but then I've discarded it considering that the code for pgm_read_xxxx_far() macros in avr/pgmspace.h has also the same problems and EEPROM routines are also affected. RAMPZ modification is documented but I agree that the side effects could be explained more clearly.
|
Carlos Lamas <carloslamas> |
Wed 02 Jan 2008 04:20:32 PM UTC, comment #1: These functions modify RAMPZ register and is non-reenterable. They cannot be used in interrupt handlers and pre-emptive Real Time OS. It should be written in documentation.
|
Anatoly Sokolov <aesok>![]() |
Fri 21 Dec 2007 02:40:29 PM UTC, original submission:
This code is to intended to access the whole flash memory in devices with flash address space bigger than 64KB.
|
Carlos Lamas <carloslamas> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-06-30 | wek | Attached File | - | ![]() |
Added memcpy_PF.zip, #20859 |
2010-06-13 | arcanum | Priority | 5 - Normal | ![]() |
9 - Immediate |
2010-06-13 | arcanum | Status | None | ![]() |
Ready For Test |
Assigned to | None | ![]() |
arcanum | ||
2010-06-03 | wek | Attached File | - | ![]() |
Added memcmp_PF.zip, #20682 |
2007-12-21 | carloslamas | Attached File | - | ![]() |
Added extra pgmspace.zip, #14680 |
You seem to have misunderstood my comment.
Carlos's library is fully adequate for its purpose and has been used for that purpose by several users months or even years before it has been accepted in 1.7.0; the problem is that it is incorrectly compiled within avr-libc.
My comment thus describes an identical problem to https://savannah.nongnu.org/bugs/?32945 (I wasn't aware of at the time when this problem was brought to my attention in the linked avrfreaks thread).
JW