Whether the cboot contains md5 checks on emmc kernel partition and device tree partition?

I want to ask: Does the current cboot include the emmc kernel and device tree partition content verification function?
The kernel, for example, can not start after the kernel partition content is read and loaded into the RAM, considering that the emmc partition may be damaged.

So what I want to do at present is to read the kernel partition content and check the content md5 at the cboot stage (the MD5 check value will be stored in the emmc specific partition in advance), and then copy the kernel to the RAM to run on the premise of the verification. If the check does not pass, I will load the kernel from the kernel_b partition to the RAM!