- Posts: 3
How do I get debug log from the trainer port?
- payne.pan
- Topic Author
- Offline
Less
More
02 Jul 2015 13:03 #34978
by payne.pan
How do I get debug log from the trainer port? was created by payne.pan
It is said that printf goes to the trainer port, I tried to connect Devo7e trainer port with FTDI usb-ttl, set rate as 115200 and only connect GND, TX and RX ( I don't know which is TX or RX, so I exchange them in my test), But nothing happened. later I found Devo7e usb-disk ruined, it is back to normal after I re-format it.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
Less
More
- Posts: 4402
02 Jul 2015 20:53 #35008
by PhracturedBlue
Replied by PhracturedBlue on topic How do I get debug log from the trainer port?
You need to compile with TYPE=dev to enable the printf. On a 7e, that will disable the standard-gui (due to space restrictions)
None of that should have anything to do with corrupting the filesystem though
None of that should have anything to do with corrupting the filesystem though
Please Log in or Create an account to join the conversation.
- payne.pan
- Topic Author
- Offline
Less
More
- Posts: 3
03 Jul 2015 00:34 #35015
by payne.pan
Replied by payne.pan on topic How do I get debug log from the trainer port?
Thanks for the answer.
So I modified lines in syscalls.c as below:
#define dbgprintf(args...) printf(args)
//#define dbgprintf(args...)
then make as "TYPE=dev", update my Tx using the new build dfu file.But I cannot get the log.
I attach the photo for the connection of trainer port and usb-ttl
So I modified lines in syscalls.c as below:
#define dbgprintf(args...) printf(args)
//#define dbgprintf(args...)
then make as "TYPE=dev", update my Tx using the new build dfu file.But I cannot get the log.
I attach the photo for the connection of trainer port and usb-ttl
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
Less
More
- Posts: 4402
03 Jul 2015 11:55 #35052
by PhracturedBlue
Replied by PhracturedBlue on topic How do I get debug log from the trainer port?
did you do a 'make clean' 1st?
you do not need to enable dbgprintf unless you want a LOT of logging. The default wil still print a bunch of intialization when you power it up
Are you running the latest deviation? if not you need to run 'make distclean' 1st (latest deviation from source should recompile everything when you change the value of TYPE)
When in doubt reverse the rx and tx lines. I assume your usb-uart is 3.3V compliant? This should be very easy to make work. I've never used an ftdi, but I see no reason why it would be different than the CP2102 I use
you do not need to enable dbgprintf unless you want a LOT of logging. The default wil still print a bunch of intialization when you power it up
Are you running the latest deviation? if not you need to run 'make distclean' 1st (latest deviation from source should recompile everything when you change the value of TYPE)
When in doubt reverse the rx and tx lines. I assume your usb-uart is 3.3V compliant? This should be very easy to make work. I've never used an ftdi, but I see no reason why it would be different than the CP2102 I use
Please Log in or Create an account to join the conversation.
- payne.pan
- Topic Author
- Offline
Less
More
- Posts: 3
03 Jul 2015 14:52 #35056
by payne.pan
Replied by payne.pan on topic How do I get debug log from the trainer port?
Ya, I found the problem is in the connector I made, some pins on the audio slot is just for fixing, I re-soldered them and make sure it is right. Now I get the log!
Thank you very much for information and analysis.
Thank you very much for information and analysis.
Please Log in or Create an account to join the conversation.
Time to create page: 0.035 seconds
- Home
- Forum
- Development
- Development
- How do I get debug log from the trainer port?