SW-TM4C: How to make it work as a USB device

I'm sorry, but I didn't know which function to use in the code, so could you tell me which function I should prepare?
(I would like you to mention the function name.)

Hello Kanematu-san,

All code examples and all driver functions are documented, I cannot spend the required time to walk you through an entire example project from start to finish, we spent dozens of hours developing, commenting, and documenting these examples to make them easy to understand. Please take your time to carefully read and review the example projects and documentation, if you are unfamiliar with microcontroller level programming, it is not something you will learn in one day.

Best Regards,

Ralph Jacobi

Hi, thanks for your reply.
First, read the documentation carefully.

Hello, is it correct to understand that usb_structs.c, which is the SW-TM4C usb-related source code, is set on the PC side?

Hello, Thank you for your replying!

I want to confirm!

You said
'PC as part of the enumeration sequence.'

This is the below 6 structures?
1.g_pui8LangDescriptor
2.g_pui8ManufacturerString
3.g_pui8ProductString
4.g_pui8SerialNumberString
5.g_pui8ControlInterfaceString
6.g_pui8ConfigString

You said
'USB structures used for the application that plug into the USB library'

This is the below 4 structures?
1.g_psCDCDevice
2.g_psRxBuffer
3.g_psTxBuffer
4.g_psCompEntries

My thinking is right?

Hello Kanematu-san,

Yes, that is correct.

Best Regards,

Ralph Jacobi

OK, Thank you!

By the way, Please tell me what the meaning is 'plug into the USB library'.

Is it a technical term within the S/W?

I would like to ask, is it correct to assume that the variables defined in TM4C129ENCZAD.h and TM4C129ENCPDT.h are the same as the register numbers listed in the datasheet of the IC I am buying?

Also, looking at the header file, I think the only difference is that TM4C129ENCZAD.h has more GPIO ports, but are there any other differences?

Hi, thanks for your reply.

You are probably correct in your understanding that the header file I was talking about is about registers.

By the way, there is no <IC name.h> where each header file of the evaluation board example is included.

Is it necessary to enter the IC name.h when writing to a Virgin state IC by self-made?

Hi, thanks for your reply.

From what I hear you say, it's basically
It means that the program can be written to the IC in Virgin state without using <IC name.h>.
However, <IC name.h> and peripheral.h cannot be used at the same time, right?

Hello Kanematu-san,

Not 100% accurate.

Hiroyuki Kanematu said:

It means that the program can be written to the IC in Virgin state without using <IC name.h>.

Correct.

Hiroyuki Kanematu said:

However, <IC name.h> and peripheral.h cannot be used at the same time, right?

No, it's specific hw_ files in the inc folder that this would apply to. I know for certain <hw_ints.h> and <IC name.h> will clash but I believe there are other situations where that occurs. But that's only for <hw_filename.h> - not for <peripheral.h> like <gpio.h> or <uart.h>.

Best Regards,

Ralph Jacobi

Hello, thank you for your reply.

Hiroyuki Kanematu said:
It means that the program can be written to the IC in Virgin state without using <IC name.h>.
Correct.

I understand.

Hiroyuki Kanematu said:
However, <IC name.h> and peripheral.h cannot be used at the same time, right?
No, it's specific hw_ files in the inc folder that this would apply to. I know for certain <hw_ints.h> and <IC name.h> will clash but I believe there are other situations where that occurs. But that's only for <hw_filename.h> - not for <peripheral.h> like <gpio.h> or <uart.h>.

This means that there are header files that can be used together depending on the type.

Hello Kanematu-san,

Hiroyuki Kanematu said:

This means that there are header files that can be used together depending on the type.

Yes from a few tests I made briefly there are overlap in compatible files. It looks the biggest point is to avoid is using both a <IC name.h> and <hw_ints.h> together. I don't have the time to test all combination to find others that may not work together.

Best Regards,

Ralph Jacobi

OK, Thank you for your replying!