Closed InnovativeIdeas closed 4 years ago
hal_gpio.h is right next to main. All the files are necessary to create a complete "standalone" project.
I dont see the definitions for the HAL_GPIOUART ??
thnaks dave
On 17 Nov 2019, at 18:50, Alex Taradov notifications@github.com wrote:
hal_gpio.h is right next to main. All the files are necessary to create a complete "standalone" project.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ataradov/mcu-starter-projects/issues/2?email_source=notifications&email_token=AAT2DBQBTWKFQLXIHDVUBPLQUGG6TA5CNFSM4JOK22ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEITABA#issuecomment-554774532, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT2DBWOLOCKBUGJ2YG6FMLQUGG6TANCNFSM4JOK22ZA.
They are generated by the macro in the hal_gpio.h file. Have a look at this file and you will see that it creates a lot of functions with names generated based on the parameter to the HAL_GPIO() macro.
OK thanks
On 17 Nov 2019, at 20:19, Alex Taradov notifications@github.com wrote:
They are generated by the macro in the hal_gpio.h file. Have a look at this file and you will see that it creates a lot of functions with names generated based on the parameter to the HAL_GPIO() macro.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ataradov/mcu-starter-projects/issues/2?email_source=notifications&email_token=AAT2DBTGQGJXTBTLUY66MBLQUGRNVA5CNFSM4JOK22ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIU4TQ#issuecomment-554782286, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT2DBTWAT7OTT5D3HVEYMLQUGRNVANCNFSM4JOK22ZA.
InnovativeIdeas Ltd
7 GlenBay Poulshone Gorey Co. Wexford Ireland
Mob: +(353)-(0)87-2545650
These files are not standalone for example in the C21 example , where does the " HAL_GPIO " source code reside , what HAL are you assuming the user has