[Yoshihiro Imamura]

Hello Steve.

I’ve confirmed to be able to retrieve AEP firmware version
using ‘version’ command.

Thank you so much for your quick response !

Best Regards,

[Yoshihiro Imamura]

Hello, Jason.

I’ve confirmed to read device-id (serial number)
in a way you mentioned.

Thanks so much for your support !

[Yoshihiro Imamura]

Jeff,

Thank you for a quick response. Here’s source code of test.c.
It’s created for a test purpose to confirm gdb/gdbserver behavior.

1:
2:#include <stdio.h>
3:
4:
5:int main(void)
6:{
7: int a;
8: int b;
9: int c;
10:
11: a = 10;
12: b = 20;
13: c = a * b;
14:
15: printf(“Hello World (%d).\n”, c);
16:
17: return 0;
18:}

All of optimizing options passed to the gcc and linker are disabled
while compiling, like this.

> gcc -march=armv5te -mtune=xscale -funit-at-a-time -msoft-float -fno-short-enums -ggdb3 -O0 -c test.c -o test.o
> gcc test.o -o target-debug

If target-debug is directly executed without gdb, it works fine.

> ./target-debug
Hello World (200).

So, I have two questions.

1. Is the architecture depend options (-march=armv5te and -mtune=xscale)
are correct ? My target machine is MTCDT-LAT1 and gcc version is 6.3.1.

2. Do I need to build gdbserver from its source code to specify the target ?
I’ve tried to install it from ipk written in the following documentation.

http://www.multitech.net/developer/software/mlinux/mlinux-software-development/debugging-a-cc-application/

However, “opkg update” was not working due to broken link.
So, I have specified another link and execute the following command instead.

> opkg install http://multitech.net/mlinux/feeds/3.3.7/arm926ejste/gdbserver_7.6.2_r0.0_arm926ejste

Thanks,

[Author]

Posts