2014-05-08 1:43 GMT+02:00 Tomek Lorek tlo...@gmail.com:
(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
Hi,
I faced next issue that I've been studying for several hours and have
no idea why flash reads end up with incorrect value:
The function reading the data from flash is:
(gdb) list FlashReadByte
7 #include uart.h
8
9 uint16_t seg_cnt;
10
11 static inline uint8_t
2014-05-04 22:14 GMT+02:00 Tomek Lorek tlo...@gmail.com:
Just checked the flashdump diff right before and after executing the
program - movx #0, @%0::r(flash)) variant messed up the flash
bank A from where I was running the code and it erased 0xc400 instead
of 0x1c400.
Do you have any idea
Hi Tomek,
Try the code snippet below. I am using 20-bit access for some time,
targetting MSP430F2417/F2618
The code is part of my bootloader code. While bootloader is executed all
IRQs are disabled.
I did not have much time to look closer at your code. Hope it helps.
/*
* 20-bit write access
look at the actual code generated
see what the difference in the actual code is
From cPhone
On May 4, 2014, at 1:14 PM, Tomek Lorek tlo...@gmail.com wrote:
2014-05-04 22:04 GMT+02:00 Tomek Lorek tlo...@gmail.com:
1. Possibly the main reason my code did not work was using
__asm__
