Hi all
I am currently looking into what's going on inside the iBurst UTD. It seems that some form of advanced utility software exists built into the UTC/UTD. What I have managed to discover thus far:
* iBurst UTD is an ARM7 processor based product (www.arm.com)
* Has a powerful MMU
* Radio closely resembles a tri-band cellphone
From cursory inspection into the hex code, it appears an extensive debug and test interface exists. The test interface even has a built in help feature (I found references to it as well as lots and lots of explanatory text)
Flash bootloader
Memory test
Memory peek and poke
EEPROM read / write
malloc
kernel management
tcp/ip services
ethernet drivers
radio tx power control, channel programming, encryption, signal measurement, BER/FER, timeslot, etc...
USB management
and much more...
Since there is info to configure the UART I presume that this interface is accesible either via JTAG or a second serial port on the PC board. Being able to access USB endpoints implies that you cannot use the USB bus to do debugging as any changes made will cause the USB to drop and disconnect you from the UTD API... I am investigating.
I am currently looking into what's going on inside the iBurst UTD. It seems that some form of advanced utility software exists built into the UTC/UTD. What I have managed to discover thus far:
* iBurst UTD is an ARM7 processor based product (www.arm.com)
* Has a powerful MMU
* Radio closely resembles a tri-band cellphone
From cursory inspection into the hex code, it appears an extensive debug and test interface exists. The test interface even has a built in help feature (I found references to it as well as lots and lots of explanatory text)
Flash bootloader
Memory test
Memory peek and poke
EEPROM read / write
malloc
kernel management
tcp/ip services
ethernet drivers
radio tx power control, channel programming, encryption, signal measurement, BER/FER, timeslot, etc...
USB management
and much more...
Since there is info to configure the UART I presume that this interface is accesible either via JTAG or a second serial port on the PC board. Being able to access USB endpoints implies that you cannot use the USB bus to do debugging as any changes made will cause the USB to drop and disconnect you from the UTD API... I am investigating.