[En-Nut-Discussion] Debugging and ports

[Wiegelmann, Jörg]

Hello folks,

I have some problems with ethernut 3:

1. I got the egnite turtelizer but I can't install it because the original ftdi driver "CDM 2.04.06 WHQL Certified.zip" says: "Hardwareinstallation not possible" German: "Hardwareinstallation nicht möglich" 

2. The Atmel-Sam Ice works (more bad than good) but in some module I can't work with breakpoints. The debugger says "cannot access memory" when it reaches the breakpoint. No stepping is possible. Compiler switches: 

arm-elf-gcc -c -mcpu=arm7tdmi -Os -gdwarf-2 -mthumb-interwork -Wall -Wstrict-prototypes -fverbose-asm -Wa,-ahlms=mymodule.lst  -Iinclude -std=c99 -I../../nutbld/include  -I../../nut/include  mymodule.c -o mymodule.o

Seggertoolconfiguration in eclipse 3.3.1.

target remote localhost:2331

monitor writeu32 0xFFE00000 = 0x1000213D

monitor writeu32 0xFFE00004 = 0x20003E3D

monitor writeu32 0xFFE00020 = 0x00000001

monitor writeu32 0xFFE00000

monitor writeu32 0xFFE00004

monitor speed auto

break main

load

3. I need a lot of ports on ethernut 3. So I want to use P19 for example. I read on http://www.ethernut.de/en/hardware/enut3/ports.html :

Note 8

Pins 56 (P16), 59 (P23), 61 (P19) and 62 (P18) are used as TMS, TDI, TDO and TCK resp. during CPLD programming with the XSVF Executor Utility. Make sure to disconnect them from the CPLD JTAG via JP9, before using them as outputs.

But there is no JP9 in the manual, only JP1, JP4, JP5. I think, that it is probably an error and JP9 is JP5. It is right?

4. Is it possible to compile the NutOs with size optimization, without getting runtime errors or special behaviour? 

Many thanks for answering the questions.

Best regards 

Joerg