Forum Replies Created
Ok so debugging the NXP ELF file with VisualGDB works so nothing wrong with the debugging part.
But now I’m stuck again, i checked register addresses and they seem to match up. So I’m stuck again.
I’m sorry I am a hobbyist and not an expert in this kind of problem solving. If you have any more pointers please let me know.
Ok as far as I can find out is that it doesn’t like this call in visualGDB
USBD_API->hw->Connect(g_hUsb, 1);This should pull up the resistor on the USB datalines. It looks like visualgdb doesn’t process this call correctly.
* \brief Hardware API functions structure.
* \ingroup USBD_HW
* This module exposes functions which interact directly with USB device controller hardware.
/** \fn void Connect(USBD_HANDLE_T hUsb, uint32_t con)
* Function to make USB device visible/invisible on the USB bus.
* This function is called after the USB initialization. This function uses the soft connect
* feature to make the device visible on the USB bus. This function is called only after the
* application is ready to handle the USB data. The enumeration process is started by the
* host after the device detection. The driver handles the enumeration process according to
* the USB descriptors passed in the USB initialization function.
* \param[in] hUsb Handle to the USB device stack.
* \param[in] con States whether to connect (1) or to disconnect (0).
* \return Nothing.
void (*Connect)(USBD_HANDLE_T hUsb, uint32_t con);
As far as I understand the code this calls a precompiled USB function? In LPCexpresso this is working correctly in visualgdb not.
I use LPCExpresso as an comparison and that uses GCC.
I tried comparing the ELF files, I loaded the LPCExpresso .axf file in visual studio (is this correct).
It looks like it’s completely different and I don’t get too much information from it. Snapshot is in the
As far as I looked in the startup code it seems to be more or less the same. Crystal setup is also exactly the same.
Attachments:You must be logged in to view attached files.