Unable to communicate over serial port with FRDM-k64F

Solved
tdkit's picture
tdkit
Junior(0)

Hello, I am attempting to connect to the serial port on the k64F for the purposes of reading debugging information (via printf and the debug mode in https://os.mbed.com/teams/Avnet/code/easy-connect-wnc/). 

I am following the instructions here: https://os.mbed.com/platforms/FRDM-K64F/#pc-configuration as well as the statements in https://marketplace.att.com/tutorials/starter-kit-guide .

These instructions state that as I am on macOS, I should see the board under the name /dev/tty.usbmodem* . However, I see no device attached here, despite the fact the program I am loading includes the line "Serial pc(USBTX, USBRX);" The second guide refers me to https://os.mbed.com/handbook/SerialPC , which also states that the device should be under /dev/tty.usbmodem.

 

Does anyone have some recommendations as to why the device may not be showing? I have tried plugging into both of the USB ports on the board but have not had success. When I plug into the USB port on the modem board I see tty.usbmodem1413/15/17, but none of these seem to carry the output from the k64f. tty.usbmodem1413 seems to allow for the issuance of AT commands to the modem, but nothing shows on tty.usbmobem1415/17, even if I am running a program that does nothing but make calls to printf.

tdkit's picture
tdkit
Junior(0)

As a followup, I have tried following the instructions at the following link in order to establish that my programs are actually being loaded to the FRDM-k64f, but when I attempt to run the hello world program, the LED does not blink as expected. Any insight into this issue would be appreciated, as I feel this complicates investigating the primary issue. When I put the binary onto the "bootloader" drive that appears on my desktop, the file is transferred and then the bootloader disappears. After this either cycling power by disconnecting cables or pressing the reset button does not lead to LED1 blinking as expected. I've also posted in the k64F forums regarding this, and will update if I learn anything. https://os.mbed.com/platforms/FRDM-K64F/#flash-a-project-binary

 

LightCollector's picture
LightCollector
Moderator(20)

Hi,  You should see mbed or daplink, not bootloader for the drive name.  You will not be able to program any user applications until the daplink is programmed.  Follow the instructions on the NXP website here:  https://www.nxp.com/products/microcontrollers-and-processors/arm-based-p...

 

Make sure the bootloader is up to date and then program the DAPLink firmware as 2nd step and then you should be able to program the K64F with an application such as the quickstart binary for the Starter Kit.

 

Best regards