The nodes are an important prerequisite for a trustworthy network. Low cost and simplicity are initiated through consecutively trustworthy code, which can help easy attestable node into the network. A close cooperation between the System-on-Chip (SoC) software producer and device producer is needed, as unbreakable trust chain among hardware and software with Trust Anchor module (TAm) that lives in SoC for a demonstrable trusted boot. The root public signing key inside a One Time Programmable (OTP) block makes up the physical trust anchor. For instance, the device producer needs to verify and recognize the SoC manufacturer, which is not practically possible for small device producers in each and every case. A small expedient producer can yield products with safe boot using the standard procedure. With huge producers, they are capable of ordering huge count of SoC using the means of self-programmed trust anchor. TrustZone by ARM, which is a Trusted Execution Environment (TEE), gives enough protection to local verification software, as the software performed in TEE need to be appropriately signed in such a way the software comes through the producer of SoC or through any authorized producer. A study of dissimilar approaches on above topic and their pros and cons are discussed in the paper. As an outcome, this paper gives the results of each methodology and suggests better procedure to overcome the existing drawbacks.