Activity
From 03/18/2014 to 04/16/2014
03/24/2014
- JC 05:31 PM Software Development: RE: Encrypted root filesystem experience
- Don,
You'll need to create a custom workorder as those tools aren't built into the demo filesystem they provide. You can start with a copy of the demo filesystem and add/remove packages that you want. The demo filesystem is quite la... - DG 05:26 PM Software Development: RE: Encrypted root filesystem experience
- Thanks for looking into that for me. In looking at the build summary for the timesys mityarm sdk I didn't see the lvm2 , cryptsetup, or libselinux packages which I believe are required. I should just download the SDK and poke around. I n...
- JC 04:42 PM Software Development: RE: Encrypted root filesystem experience
- Don,
I was able to verify that they have the cryptsetup package which contains dm-crypt and luks tools.
- JC 03:44 PM Software Development: RE: Encrypted root filesystem experience
- Timesys has a build system that builds the entire filesystem from source. The only thing we provide them is a working kernel. So it isn't based on our filesystem but most of its file locations should be similar. What would be most use...
- DG 03:02 PM Software Development: RE: Encrypted root filesystem experience
- Thanks Jonathan I will check out the timesys SDK some more. I should add that there is significant investment of time and verification in the existing file system and kernel version so I'm going to pursue adding to the critical link bas...
- JC 10:14 AM Software Development: RE: Encrypted root filesystem experience
- Don,
I'm not aware that anyone here has tried to get encrypted filesystems working, if you find any good resources on the subject feel free to post them on this thread.
It would be worth your time setting up a "Timesys":http://www.... - I'm working with a MityArm-335x SOM and attempting to set up an encrypted root file system on an SD card to be mounted during the boot process. I'm using the latest das-boot port from critical link and the mityarm devkit / cross compile ...
03/20/2014
- DM 11:22 AM Software Development: RE: Mityarm RGMII1 question
- The etc file for setting the eth0 to mac is:
/etc/udev/rules.d/70-persistant-net.rules - DM 11:21 AM Software Development: RE: Mityarm RGMII1 question
- I setup up devices.c with phy_id set to 0:1 and 0:0. The phy is found, but I do not see any activity on the RGMII1 interface. Is there another setting in a file for which MAC to use? I noticed in the SOM.c in U-boot, PROFILE_1 when using...
03/19/2014
- MW 02:24 PM Software Development: RE: Mityarm RGMII1 question
- I think you also need to modify the devices.c.
Search for cpsw_salve_data. The phy_id needs to be assigned to the correct slave index.
The CONFIG_BASEBOARD_MITYARM335X_TESTFIXTURE actually uses the RGMII1 instead of RGMII2.
-... - I am in the process of debugging the SMSC LAN8820 PHY on a board that has a Mityarm board used as the CPU. The PHY is connected as RGMII1, with pinmux files changed in u-boot and baseboard-mityarm335x-devkit.c. I also added this new PHY ...