Re: Accessing 20-bit memory range - issues with indirect addressing mode

Tomek Lorek <[email protected]>
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.user
Message-ID <CAP62dvC0JqwobyeCzXCUQ6Tp06s-BqXk1NxEwyRZv2ZCahZmRQ@mail.gmail.com> 
2014-05-08 1:43 GMT+02:00 Tomek Lorek <[email protected]>:
> (gdb) print result
> $62 = 85 'U'

Ok, just found that for some reason it is the 0x4400 instead of
0x14400 address being read (despite gdb says the address is 82944d), I
checked the read sequence of several bytes starting from 0x14400 and
it fully matches the content of 0x4400.

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.