I got to load and run "am57xx-pruX-prusw-fw.elf" in the PRU by configuring the "ti_prueth.prussX_ethtype" variable.
I also put some printks in "prueth.c" file to confirm that functions comuncating directly with PRU are called, such as "prueth_switchdev_attr_set…
Hi Shiou Mei,
Below is the dump of MMC1 registers after the first SD command failed.
Core Control Module: (0x4A002E00) CTRL_CORE_CONTROL_PBIAS :0xd200000
MMC1 Host Controller regs: (0x480BC000) MMCHS_HL_REV :0x96579b34 (0x4809C004) MMCHS_HL_HWINFO…
Hi Jonathan, Yes, the values in the datasheet are what is to be followed. WEBENCH is also using the correct pin strap resistor values. Attached is the updated excel calculator tool. The 10kOhm resistor value should result a 400kHz fsw. Recommended for…
Gabriele,
I haven't seen your layout, but if you are seeing large ripple voltages at your output and if your output is not stable for no apparent BOM reason, then it could be the layout. Firstly, breadboarding an SMPS with thin traces/wires is not a…
Hello Ian,
While using an SMPS which is switching at a very high frequency, bread-boarding the design is not a good idea. Your layout, even though surface mounted, is not optimized. The SW node should be fat and wide and not long. But on your layout…
Hello Ben,
The BOM that Webench suggested should be correct. The thing with switch mode power supplies is that you cannot bread board them with long wire leads. Since they are switching at high frequencies, any additional lead length will add parasitics…
I attached two files, one preprocessed C source and second one is generated asm output with marked line where it crashed (look for !!! symbol).
Code is generated by tms470_4.9.7, with following switches:
cl470.exe -c -fe aes.obj -DMODEL_TYPE=MODEL_TYPE_ACCESSUNIT…
And here is the install log from my Docker container..
Log started 09/28/2023 at 15:45:30
Preferred installation mode : unattended
Trying to init installer in mode unattended
Mode unattended successfully initialized
[15:45:30] CCS_INFO: Installer…
Thanks Jeff that has cleared up my understanding.
I'm using the attached vendor Information file.
I've also attached the test log. There are a few failures are these down to errors in the VIF ? Thanks in adavnce
Report_RM_TBT3_U16_2017-06-29-09…
If it helps, here is a boot log with CE_DEBUG=2 showing the encoder stopping due to CMEM errors, this was booting up with a "bad" bitrate set for stream 2.
I am unclear how to check that the available memory/buffers are sufficient for the selected option…
