November 2023 - pacsat-dev - mailman.amsat.org

Re: Initial playing with HALCoGen
by Jim McCullers 18 Nov '23

18 Nov '23

Bunch o'pins. Thanks? Seriously, nice work. Jim McCullers WA4CWI All, Here is a revised version of the Pin assignments for the TMS570. Bob On Nov 17, 2023, at 1:02 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: As we said last night, there are probably some HALCoGen things to change to get the s/w running on Blinky, aka Bob's Board. This is not to tell you what, but just to get you started looking at HCG. First, the version I am using is 4.07.01, released 11Dec2018. I think this is the latest. It has a few bugs which they never fixed. But in any case, once you start it up, what you want to do is to got to file/Open Project and open the file (from the PacSat software repository) called PacSat.hcg. There is also a PacSat.gil. I've never been sure what that does, and it only occasionally actually changes. These files are in the top-level folder of the repository named "hcg". When this loads, you will see a huge number of tabs. Along the top are mostly the "peripheral" devices like GIO (aka gpio), SCI (aka UART), SPIs, CANs, ADCs, etc When you pick one of those peripherals, say SPI4, you get a second row of tabs relating to the peripheral. In many cases you don't need to change much but post of the peripherals have a "Port" tab which is generally important. On the left column you generally see each logical connection to the peripheral (lets call them pins). For example SOMI (normally called MISO), SIMO (MOSI), CLK, ENA, and a bunch of SCS (chip select) pins. For each one you select whether you want to use it for the peripheral or if you want to use that pin for the peripheral or as a GPIO. Generally if you are using a SPI, you will need SOMI, SIMO, and CLK. I've never quite known what ENA does. But you don't want to use the SCS pins connected to the peripheral. The driver expects them to be GPIO pins for more flexiblity. On the right block, you can see how the pins are set up: Open gate, which direction, pull up or pull down, etc. And finally now the name of the pin (say SPI4 SIMO). Now go back to the PINMUX "peripheral". Some of those pins like SPI4 SIMO can appear on one of several actual pins on the chip. For example pin 25 can either be HET1_0 or SPI4CLK or a couple other things. Chose the one you want. It's very frustrating trying to find what you are looking for! The check boxes at the top seem to change a bunch of things at the same time, so I try to avoid them :-) To generate the code that does back into the git repo, use "generalte code" under "file". If you look at the generated code you will see stuff all through it that looks like this: /* USER CODE BEGIN (3) */ /* USER CODE END */ If you have to tweak some stuff (and I did) and you can put the code in between those comments, HALCoGen will not change it! Note for example that I actually replaced a lot of some of the SPI routines (see hcgExtras folder). I can explain why at some point when you are interested. But the main point here is that you have to keep the header and C files in sync between your build machine and your HALCoGen machine. If you change ANYTHING on either side, make sure they are the same on both sides. As I may have said, I use DropBox and have HalCoGen read and write its files there. Then I just copy from the dropbox directory to the IDE on the build machine and we are good, and have source control automatically for all the HalCoGen stuff. At some point, I may remember and talk about the HET code that HALCoGen pays some attention to as well :-) I hope this might get you started in looking at it at least. And I should note that you will also need to TMS570 documentation to figure out what the heck HALCoGen is talking about. For example, what is there an MIBSPI1 and an SPI1 both? (I knew at one time but have forgotten!) What are the "data formats" in SPI (clever actually). 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Initial playing with HALCoGen
by Bob Stricklin 18 Nov '23

18 Nov '23

All, Here is a revised version of the Pin assignments for the TMS570. Bob On Nov 17, 2023, at 1:02 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: As we said last night, there are probably some HALCoGen things to change to get the s/w running on Blinky, aka Bob's Board. This is not to tell you what, but just to get you started looking at HCG. First, the version I am using is 4.07.01, released 11Dec2018. I think this is the latest. It has a few bugs which they never fixed. But in any case, once you start it up, what you want to do is to got to file/Open Project and open the file (from the PacSat software repository) called PacSat.hcg. There is also a PacSat.gil. I've never been sure what that does, and it only occasionally actually changes. These files are in the top-level folder of the repository named "hcg". When this loads, you will see a huge number of tabs. Along the top are mostly the "peripheral" devices like GIO (aka gpio), SCI (aka UART), SPIs, CANs, ADCs, etc. When you pick one of those peripherals, say SPI4, you get a second row of tabs relating to the peripheral. In many cases you don't need to change much but post of the peripherals have a "Port" tab which is generally important. On the left column you generally see each logical connection to the peripheral (lets call them pins). For example SOMI (normally called MISO), SIMO (MOSI), CLK, ENA, and a bunch of SCS (chip select) pins. For each one you select whether you want to use it for the peripheral or if you want to use that pin for the peripheral or as a GPIO. Generally if you are using a SPI, you will need SOMI, SIMO, and CLK. I've never quite known what ENA does. But you don't want to use the SCS pins connected to the peripheral. The driver expects them to be GPIO pins for more flexiblity. On the right block, you can see how the pins are set up: Open gate, which direction, pull up or pull down, etc. And finally now the name of the pin (say SPI4 SIMO). Now go back to the PINMUX "peripheral". Some of those pins like SPI4 SIMO can appear on one of several actual pins on the chip. For example pin 25 can either be HET1_0 or SPI4CLK or a couple other things. Chose the one you want. It's very frustrating trying to find what you are looking for! The check boxes at the top seem to change a bunch of things at the same time, so I try to avoid them :-) To generate the code that does back into the git repo, use "generalte code" under "file". If you look at the generated code you will see stuff all through it that looks like this: /* USER CODE BEGIN (3) */ /* USER CODE END */ If you have to tweak some stuff (and I did) and you can put the code in between those comments, HALCoGen will not change it! Note for example that I actually replaced a lot of some of the SPI routines (see hcgExtras folder). I can explain why at some point when you are interested. But the main point here is that you have to keep the header and C files in sync between your build machine and your HALCoGen machine. If you change ANYTHING on either side, make sure they are the same on both sides. As I may have said, I use DropBox and have HalCoGen read and write its files there. Then I just copy from the dropbox directory to the IDE on the build machine and we are good, and have source control automatically for all the HalCoGen stuff. At some point, I may remember and talk about the HET code that HALCoGen pays some attention to as well :-) I hope this might get you started in looking at it at least. And I should note that you will also need to TMS570 documentation to figure out what the heck HALCoGen is talking about. For example, what is there an MIBSPI1 and an SPI1 both? (I knew at one time but have forgotten!) What are the "data formats" in SPI (clever actually). 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Initial playing with HALCoGen
by Jim McCullers 17 Nov '23

17 Nov '23

Burns, Thanks. I installed HALCoGen last night after the meeting. 4.07.01 is the latest version. The second file is PacSat.dil, not PacSat.gil. I actually though that might be the output. So the output is the code found in the include/source files? I was expecting something more like a .xml file which is what the .hcg file is. I’m begging to understand it a bit better which is not to say I’m ready to lay down a system. Cypress Semiconductor has a similar system for defining their chips. Rest up this weekend. A long list of questions is likely to follow. 73, Jim McCullers WA4CWI From: Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Friday, November 17, 2023 1:02 PM To: Pacsat Dev <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Initial playing with HALCoGen As we said last night, there are probably some HALCoGen things to change to get the s/w running on Blinky, aka Bob's Board. This is not to tell you what, but just to get you started looking at HCG. First, the version I am using is 4.07.01, released 11Dec2018. I think this is the latest. It has a few bugs which they never fixed. But in any case, once you start it up, what you want to do is to got to file/Open Project and open the file (from the PacSat software repository) called PacSat.hcg. There is also a PacSat.gil. I've never been sure what that does, and it only occasionally actually changes. These files are in the top-level folder of the repository named "hcg". When this loads, you will see a huge number of tabs. Along the top are mostly the "peripheral" devices like GIO (aka gpio), SCI (aka UART), SPIs, CANs, ADCs, etc. When you pick one of those peripherals, say SPI4, you get a second row of tabs relating to the peripheral. In many cases you don't need to change much but post of the peripherals have a "Port" tab which is generally important. On the left column you generally see each logical connection to the peripheral (lets call them pins). For example SOMI (normally called MISO), SIMO (MOSI), CLK, ENA, and a bunch of SCS (chip select) pins. For each one you select whether you want to use it for the peripheral or if you want to use that pin for the peripheral or as a GPIO. Generally if you are using a SPI, you will need SOMI, SIMO, and CLK. I've never quite known what ENA does. But you don't want to use the SCS pins connected to the peripheral. The driver expects them to be GPIO pins for more flexiblity. On the right block, you can see how the pins are set up: Open gate, which direction, pull up or pull down, etc. And finally now the name of the pin (say SPI4 SIMO). Now go back to the PINMUX "peripheral". Some of those pins like SPI4 SIMO can appear on one of several actual pins on the chip. For example pin 25 can either be HET1_0 or SPI4CLK or a couple other things. Chose the one you want. It's very frustrating trying to find what you are looking for! The check boxes at the top seem to change a bunch of things at the same time, so I try to avoid them :-) To generate the code that does back into the git repo, use "generalte code" under "file". If you look at the generated code you will see stuff all through it that looks like this: /* USER CODE BEGIN (3) */ /* USER CODE END */ If you have to tweak some stuff (and I did) and you can put the code in between those comments, HALCoGen will not change it! Note for example that I actually replaced a lot of some of the SPI routines (see hcgExtras folder). I can explain why at some point when you are interested. But the main point here is that you have to keep the header and C files in sync between your build machine and your HALCoGen machine. If you change ANYTHING on either side, make sure they are the same on both sides. As I may have said, I use DropBox and have HalCoGen read and write its files there. Then I just copy from the dropbox directory to the IDE on the build machine and we are good, and have source control automatically for all the HalCoGen stuff. At some point, I may remember and talk about the HET code that HALCoGen pays some attention to as well :-) I hope this might get you started in looking at it at least. And I should note that you will also need to TMS570 documentation to figure out what the heck HALCoGen is talking about. For example, what is there an MIBSPI1 and an SPI1 both? (I knew at one time but have forgotten!) What are the "data formats" in SPI (clever actually). 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software

1 0

Initial playing with HALCoGen
by Burns Fisher (AMSAT) 17 Nov '23

17 Nov '23

As we said last night, there are probably some HALCoGen things to change to get the s/w running on Blinky, aka Bob's Board. This is not to tell you what, but just to get you started looking at HCG. First, the version I am using is 4.07.01, released 11Dec2018. I think this is the latest. It has a few bugs which they never fixed. But in any case, once you start it up, what you want to do is to got to file/Open Project and open the file (from the PacSat software repository) called PacSat.hcg. There is also a PacSat.gil. I've never been sure what that does, and it only occasionally actually changes. These files are in the top-level folder of the repository named "hcg". When this loads, you will see a huge number of tabs. Along the top are mostly the "peripheral" devices like GIO (aka gpio), SCI (aka UART), SPIs, CANs, ADCs, etc. When you pick one of those peripherals, say SPI4, you get a second row of tabs relating to the peripheral. In many cases you don't need to change much but post of the peripherals have a "Port" tab which is generally important. On the left column you generally see each logical connection to the peripheral (lets call them pins). For example SOMI (normally called MISO), SIMO (MOSI), CLK, ENA, and a bunch of SCS (chip select) pins. For each one you select whether you want to use it for the peripheral or if you want to use that pin for the peripheral or as a GPIO. Generally if you are using a SPI, you will need SOMI, SIMO, and CLK. I've never quite known what ENA does. But you don't want to use the SCS pins connected to the peripheral. The driver expects them to be GPIO pins for more flexiblity. On the right block, you can see how the pins are set up: Open gate, which direction, pull up or pull down, etc. And finally now the name of the pin (say SPI4 SIMO). Now go back to the PINMUX "peripheral". Some of those pins like SPI4 SIMO can appear on one of several actual pins on the chip. For example pin 25 can either be HET1_0 or SPI4CLK or a couple other things. Chose the one you want. It's very frustrating trying to find what you are looking for! The check boxes at the top seem to change a bunch of things at the same time, so I try to avoid them :-) To generate the code that does back into the git repo, use "generalte code" under "file". If you look at the generated code you will see stuff all through it that looks like this: /* USER CODE BEGIN (3) */ /* USER CODE END */ If you have to tweak some stuff (and I did) and you can put the code in between those comments, HALCoGen will not change it! Note for example that I actually replaced a lot of some of the SPI routines (see hcgExtras folder). I can explain why at some point when you are interested. But the main point here is that you have to keep the header and C files in sync between your build machine and your HALCoGen machine. If you change ANYTHING on either side, make sure they are the same on both sides. As I may have said, I use DropBox and have HalCoGen read and write its files there. Then I just copy from the dropbox directory to the IDE on the build machine and we are good, and have source control automatically for all the HalCoGen stuff. At some point, I may remember and talk about the HET code that HALCoGen pays some attention to as well :-) I hope this might get you started in looking at it at least. And I should note that you will also need to TMS570 documentation to figure out what the heck HALCoGen is talking about. For example, what is there an MIBSPI1 and an SPI1 both? (I knew at one time but have forgotten!) What are the "data formats" in SPI (clever actually). 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Pacsat dev mtg 11/16/2023
by Bob Stricklin 16 Nov '23

16 Nov '23

Corey, We wish you a safe and uneventful trip and holidays. Hope you can continue to be involved at some level. Bob > On Nov 16, 2023, at 10:46 AM, Corey Minyard via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > I have my monthly Thursday night thing today, so I won't be able to > join. Next week is Thanksgiving, The next week I will be flying to > India, and the next week I'll be in India. So it will be a while > before I can attend, and I wll be very busy during all this. > > I also wanted to talk a bit because I'm not a big contributor to this > effort. I'm ok to attend the meetings, but I will have a limited > capacity to do much else because of other things I work on. So I can > continue as is, but if that's not ok I'm fine with bowing out. > > Thanks, > > -corey > >> On Thu, Nov 16, 2023 at 9:30 AM Bill via pacsat-dev >> <pacsat-dev(a)amsat.org> wrote: >> >> Pacsat dev mtg 11/16/2023 >> Thu, Nov 16, 2023 7:00 PM - 9:00 PM (CST) >> >> Please join my meeting from your computer, tablet or smartphone. >> >> https://meet.goto.com/540413653 >> >> You can also dial in using your phone. >> (For supported devices, tap a one-touch number below to join instantly.) >> >> United States: +1 (872) 240-3311 >> - One-touch: tel:+18722403311,,540413653# >> >> Access Code: 540-413-653 >> >> Join from a video-conferencing room or system. >> Dial in or type: 67.217.95.2 or inroomlink.goto.com >> Meeting ID: 540 413 653 >> Or dial directly: 540413653(a)67.217.95.2 or 67.217.95.2##540413653 >> >> >> Get the app now and be ready when your first meeting starts: >> https://meet.goto.com/install >> >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Pacsat dev mtg 11/16/2023
by Corey Minyard 16 Nov '23

16 Nov '23

I have my monthly Thursday night thing today, so I won't be able to join. Next week is Thanksgiving, The next week I will be flying to India, and the next week I'll be in India. So it will be a while before I can attend, and I wll be very busy during all this. I also wanted to talk a bit because I'm not a big contributor to this effort. I'm ok to attend the meetings, but I will have a limited capacity to do much else because of other things I work on. So I can continue as is, but if that's not ok I'm fine with bowing out. Thanks, -corey On Thu, Nov 16, 2023 at 9:30 AM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Pacsat dev mtg 11/16/2023 > Thu, Nov 16, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/540413653 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (872) 240-3311 > - One-touch: tel:+18722403311,,540413653# > > Access Code: 540-413-653 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 540 413 653 > Or dial directly: 540413653(a)67.217.95.2 or 67.217.95.2##540413653 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Pacsat dev mtg 11/16/2023
by Bill 16 Nov '23

16 Nov '23

Pacsat dev mtg 11/16/2023 Thu, Nov 16, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/540413653 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (872) 240-3311 - One-touch: tel:+18722403311,,540413653# Access Code: 540-413-653 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 540 413 653 Or dial directly: 540413653(a)67.217.95.2 or 67.217.95.2##540413653 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

PacSat help commannds
by Jim McCullers 10 Nov '23

10 Nov '23

In Thursday night's meeting we discussed the current PacSat command process and how to obtain a command list while running. Below are the four help commands that list the available commands by category. Help List common commands Helpall List all commands Helpdevo List commands for software developers Helpsetup List commands for setting up new board As these commands are legacy, at some point we may want to consider removing commands that are not specific to PacSat and adding those we require as Chris and I have done. Jim McCullers WA4CWI

1 0

LaunchPad Protective box in mm
by Bob Stricklin 10 Nov '23

10 Nov '23

This is the LaunchPad base box with updated dimensions and in millimeters. Bob

1 0

Pacsat dev mtg 11/9/2023
by Bill 09 Nov '23

09 Nov '23

Pacsat dev mtg 11/9/2023 Thu, Nov 9, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/587059365 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (224) 501-3412 - One-touch: tel:+12245013412,,587059365# Access Code: 587-059-365 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 587 059 365 Or dial directly: 587059365(a)67.217.95.2 or 67.217.95.2##587059365 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0