Hi,

The CONTROL register (and BASEPRI) are mapped in the new GDB server as int types (4 bytes). I thought first that this was not right and that it should be 1 byte.
But it seems that it is 4 bytes (with a lot of reservations in it) but the endianesses of these registers are wrong.

The CONTROL is swapped over 4 bytes and the BasePri has an correct word swap but the word it self is wrong . See output below.

output snippet:



The BasePri gives 0x2800 back, should be 0x28.
The CONTROL gives 0x2000000, should be 0x2.

Regards

Hi, thanks!

For those using EmBlocks (Beta 2.0 or 2.1) and are using the Beta Jlink with the correct Control and Basepri mappings, they need to change the script file for Arm registers (just plain text file).

In the directory share\EmBlocks\debuggers the file arm-gdb-reg.script

Remove the following lines:

search in the function parse_ctrl for the line:
// Correct the endianesses of Segger J-link
value = (value >>24)&0xFF;

search in the function set_ctrl for the line:
// Correct the endianesses of Segger J-link
regval = regval << 24;

search in the function parse_bpri for the line:
// Correct the endianesses of Segger J-link
value = (value >>8 )&0xFF;

search in the function set_bpri for the line:
// Correct the endianesses of Segger J-link
regval = regval << 8;

The debugger register window will now show these registers like before (in the old jlink versions)