Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/FCONZYHU5I2GNBLEA3TNHP54KZAVULD5/
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FCONZYHU5I2GNBLEA3TNHP54KZAVULD5/", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/", "message_id": "[email protected]", "message_id_hash": "FCONZYHU5I2GNBLEA3TNHP54KZAVULD5", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/FCONZYHU5I2GNBLEA3TNHP54KZAVULD5/", "sender": { "address": "wa4cwi (a) bellsouth.net", "mailman_id": "4aa6f1e3f4cd4bf4b1492e47285ca527", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/4aa6f1e3f4cd4bf4b1492e47285ca527/emails/" }, "sender_name": "Jim McCullers", "subject": "[pacsat-dev] Re: Initial playing with HALCoGen", "date": "2023-11-18T14:28:58Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Bunch o'pins.\n\nThanks?\n\n \n\nSeriously, nice work.\n\n \n\nJim McCullers\n\nWA4CWI\n\n \n\nAll, \n\n \n\nHere is a revised version of the Pin assignments for the TMS570.\n\n \n\nBob\n\n \n\n \n\n\n\n\n\nOn Nov 17, 2023, at 1:02 PM, Burns Fisher (AMSAT) via pacsat-dev\n<[email protected] <mailto:[email protected]> > wrote:\n\n \n\nAs we said last night, there are probably some HALCoGen things to change to\nget the s/w running on Blinky, aka Bob's Board. This is not to tell you\nwhat, but just to get you started looking at HCG. \n\n \n\nFirst, the version I am using is 4.07.01, released 11Dec2018. I think this\nis the latest. It has a few bugs which they never fixed. But in any case,\nonce you start it up, what you want to do is to got to file/Open Project and\nopen the file (from the PacSat software repository) called PacSat.hcg.\nThere is also a PacSat.gil. I've never been sure what that does, and it\nonly occasionally actually changes. These files are in the top-level folder\nof the repository named \"hcg\". When this loads, you will see a huge number\nof tabs. Along the top are mostly the \"peripheral\" devices like GIO (aka\ngpio), SCI (aka UART), SPIs, CANs, ADCs, etc \n\n \n\nWhen you pick one of those peripherals, say SPI4, you get a second row of\ntabs relating to the peripheral. In many cases you don't need to change\nmuch but post of the peripherals have a \"Port\" tab which is generally\nimportant. On the left column you generally see each logical connection to\nthe peripheral (lets call them pins). For example SOMI (normally called\nMISO), SIMO (MOSI), CLK, ENA, and a bunch of SCS (chip select) pins. For\neach one you select whether you want to use it for the peripheral or if you\nwant to use that pin for the peripheral or as a GPIO. Generally if you are\nusing a SPI, you will need SOMI, SIMO, and CLK. I've never quite known what\nENA does. But you don't want to use the SCS pins connected to the\nperipheral. The driver expects them to be GPIO pins for more flexiblity.\nOn the right block, you can see how the pins are set up: Open gate, which\ndirection, pull up or pull down, etc. And finally now the name of the pin\n(say SPI4 SIMO). \n\n \n\nNow go back to the PINMUX \"peripheral\". Some of those pins like SPI4 SIMO\ncan appear on one of several actual pins on the chip. For example pin 25\ncan either be HET1_0 or SPI4CLK or a couple other things. Chose the one you\nwant. It's very frustrating trying to find what you are looking for! The\ncheck boxes at the top seem to change a bunch of things at the same time, so\nI try to avoid them :-)\n\n \n\nTo generate the code that does back into the git repo, use \"generalte code\"\nunder \"file\". If you look at the generated code you will see stuff all\nthrough it that looks like this:\n\n\n/* USER CODE BEGIN (3) */\n/* USER CODE END */\n\nIf you have to tweak some stuff (and I did) and you can put the code in\nbetween those comments, HALCoGen will not change it! Note for example that\nI actually replaced a lot of some of the SPI routines (see hcgExtras\nfolder). I can explain why at some point when you are interested. But the\nmain point here is that you have to keep the header and C files in sync\nbetween your build machine and your HALCoGen machine. If you change\nANYTHING on either side, make sure they are the same on both sides. As I\nmay have said, I use DropBox and have HalCoGen read and write its files\nthere. Then I just copy from the dropbox directory to the IDE on the build\nmachine and we are good, and have source control automatically for all the\nHalCoGen stuff.\n\n \n\nAt some point, I may remember and talk about the HET code that HALCoGen pays\nsome attention to as well :-)\n\n \n\nI hope this might get you started in looking at it at least. And I should\nnote that you will also need to TMS570 documentation to figure out what the\nheck HALCoGen is talking about. For example, what is there an MIBSPI1 and\nan SPI1 both? (I knew at one time but have forgotten!) What are the \"data\nformats\" in SPI (clever actually). \n\n \n\n\n\n\n73, \n\n \n\nBurns Fisher, WB1FJ\n\nAMSAT(R) Engineering -- Flight Software\n\n\n-----------------------------------------------------------\n\npacsat-dev mailing list -- [email protected]\n<mailto:[email protected]> \nView archives of this mailing list at\nhttps://mailman.amsat.org/hyperkitty/list/[email protected]\nTo unsubscribe send an email to [email protected]\n<mailto:[email protected]> \nManage all of your AMSAT-NA mailing list preferences at\nhttps://mailman.amsat.org\n\n \n\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FCONZYHU5I2GNBLEA3TNHP54KZAVULD5/", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "us-ascii", "size": 10120, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/FCONZYHU5I2GNBLEA3TNHP54KZAVULD5/attachment/2/attachment.html" } ] }