slaanesh
Certified Guru
Does anyone have a GP32 EXT <-> Serial cable they want to sell me? I'm trying to do some debugging with the GP32.
I've tried the USB port - not really sure what's wrong.
Steps:
1). Build my app
2). Included USB version gdb-stub
3). Include the following code when starting up:
	
	
	
		
4). Built app using devkitARM r26.
5). Run app - crashes. Great!
Other preparations:
1). GP32 bios flashed with MultiFWv2
2). Built gdbserv for cygwin (couldn't get it built under Mac OS X, libusb issue.)
3). Installed libusb-win32. Installed the device driver. Built a GP32 .inf file.
4). Tested gdbserv for cygwin - works wonderfully. Fully recognized and waiting for connection.
	
	
	
		
Okay, now I though I was ready.
1). Run app, crashes. Great, GP32 doesn't reboot but sits there, presumable waiting for some GDB action.
2). Start arm-eabi-gdb.exe
3). From arm-eabi-gdb.exe - gdb: file app.elf
Everything loads fine.
4). Start gdbserv. Seems to connect fine, see above log.
5). From arm-eabi-gdb.exe - gdb: target remote localhost:2334
We have some action! But it's not good?
	
	
	
		
:-(
All those "Data send result: [-22] don't look very good...
What's wrong?
Anyway, I thought the UART cable would be better.
So anyone got a GP32 UART cable? It's going to a great cause. The app in question is MAME4ALL GP32.
				
			I've tried the USB port - not really sure what's wrong.
Steps:
1). Build my app
2). Included USB version gdb-stub
3). Include the following code when starting up:
		Code:
	
	#ifdef GP32_GDB
void trap()
{
 __asm__ __volatile__
(" \n"
 " mov    r0, #0x01 \n"
 " ldr    r1, [r0] \n"
 " \n"
 :
 :
 :"r0", "r1");
}
#endif
#ifdef GP32_GDB
        /* GDB Stub debugger */
        OpenUSB();
        InstallISR();
        trap();
#endif4). Built app using devkitARM r26.
5). Run app - crashes. Great!
Other preparations:
1). GP32 bios flashed with MultiFWv2
2). Built gdbserv for cygwin (couldn't get it built under Mac OS X, libusb issue.)
3). Installed libusb-win32. Installed the device driver. Built a GP32 .inf file.
4). Tested gdbserv for cygwin - works wonderfully. Fully recognized and waiting for connection.
		Code:
	
	DEBUG: usb_init()
DEBUG: usb_find_busses()
DEBUG: usb_find_devices()
DEBUG: Vendor eb6 Product 3232
GDB thread is starting...
Opening socket, please wait.
Socket successfully opened.
Socket successfully bound to port 2334.
Started to listen at:2334
Waiting for connection...1). Run app, crashes. Great, GP32 doesn't reboot but sits there, presumable waiting for some GDB action.
2). Start arm-eabi-gdb.exe
3). From arm-eabi-gdb.exe - gdb: file app.elf
Everything loads fine.
4). Start gdbserv. Seems to connect fine, see above log.
5). From arm-eabi-gdb.exe - gdb: target remote localhost:2334
We have some action! But it's not good?
		Code:
	
	Got connection
Waiting for data
Sending data [14] $qSupported#37
Data send result: [-22]
Sending data [14] $qSupported#37
Data send result: [-22]
Sending data [14] $qSupported#37
Data send result: [-22]
Sending data [14] $qSupported#37
Data send result: [-22]
Sending data [5] $?#3f
Data send result: [-22]
Sending data [5] $?#3f
Data send result: [-22]
Sending data [5] $?#3f
Data send result: [-22]
Sending data [5] $?#3f
Data send result: [-22]
Sending data [9] +$Hc-1#09
Data send result: [-22]
Sending data [8] $Hc-1#09
Data send result: [-22]
Sending data [8] $Hc-1#09
Data send result: [-22]
Sending data [8] $Hc-1#09
Data send result: [-22]
Sending data [7] +$qC#b4
Data send result: [-22]
Sending data [6] $qC#b4
Data send result: [-22]
Sending data [6] $qC#b4
Data send result: [-22]
Sending data [6] $qC#b4
Data send result: [-22]
Sending data [13] +$qOffsets#4b
Data send result: [-22]
Sending data [12] $qOffsets#4b
Data send result: [-22]
Sending data [12] $qOffsets#4b
Data send result: [-22]
Sending data [12] $qOffsets#4b
Data send result: [-22]
WARNING: Lost connection, waiting for new connectionAll those "Data send result: [-22] don't look very good...
What's wrong?
Anyway, I thought the UART cable would be better.
So anyone got a GP32 UART cable? It's going to a great cause. The app in question is MAME4ALL GP32.
 
	
 
 
		 
 
		 
 
		 
 
		