Journal article
Magnetization reversal processes in epitaxial Co/Fe bi-layers grown on MgO(001)
- Abstract:
- We report on the mechanism of magnetization reversal in epitaxial Co/Fe bi-layers grown by molecular beam epitaxy on MgO(001) substrates. For Co films thicker than 5 nm, the crystal structure is hexagonal. The Fe layer follows an epitaxial relation relative to the MgO substrate of (001) [100] Fe// (001) [110] MgO. When deposited on a cubic Fe layer, the Co layer follows a bi-crystal epitaxial relation of (11 2- 0) [0001] Co// (001) 〈 100 〉 Fe as previously reported [Popova, Appl. Phys. Lett. 81, 1035 (2002); Wang, J. Appl. Phys. 101, 09D103 (2007)]. The magnetization reversal in-plane follows a cubic fourfold symmetry, which coincides with that of the underlying bcc Fe layer. In this study, we find that the area of each Co crystal domain spans 200-1500 nm2 and that these two domains are approximately evenly distributed. The micromagnetic reversal mechanism is a combination of coherent rotational processes and domain wall displacement. These magnetic domains are sized tens of μm and separated by predominately 90° or occasionally 180° domain walls along the Fe 〈 110 〉 and Fe 〈 100 〉 directions, respectively. The cubic anisotropy of the bi-crystalline Co layer is explained by exchange-coupling between hcp grains with perpendicular crystallographic orientation, each having in-plane uniaxial magnetic anisotropy along its respective [0001] direction. © 2008 American Institute of Physics.
- Publication status:
- Published
Actions
Access Document
- Publisher copy:
- 10.1063/1.2894594
Authors
- Journal:
- JOURNAL OF APPLIED PHYSICS More from this journal
- Volume:
- 103
- Issue:
- 6
- Pages:
- 063918-063918
- Publication date:
- 2008-03-15
- DOI:
- ISSN:
-
0021-8979
- Language:
-
English
- Pubs id:
-
pubs:15071
- UUID:
-
uuid:ef95c221-801c-4f12-a6eb-7acc71c7367d
- Local pid:
-
pubs:15071
- Source identifiers:
-
15071
- Deposit date:
-
2012-12-19
- ARK identifier:
Terms of use
- Copyright date:
- 2008
If you are the owner of this record, you can report an update to it here: Report update to this record