Group Actions
Engagement
  • Author Author: Digimorf
  • Date Created: Date Created
  • Views 1270 views
  • Likes 8 likes
  • Comments 7 comments
Related
Recommended

At The Core Design Challenge: Day -3, What to expect when you are expecting.

Digimorf

Today is another day, but the good news is that there is a challenge waiting for me/you.Wink

This is a chance to share something with other developers and enthusiasts alike, learning and going towards a goal, hoping to give your best every day (and of course to win the first prize Stuck out tongue winking eye). 

There are still three days before the kit arrives, so this is the perfect time for me to read the datasheet of the PSoCTm︎ 62 MCU from cover to cover. Why I said "Perfect time"? Because during the waiting you are very excited and you will be more curious about how things work. Read, read everwhere, read all the time. How many times your wife or your mother yelled calling you out of the bathroom while you were focused regarding datasheets? I can't count them. Rofl

I'm not saying that youu have to remember every single word of the datasheet. You only need to remember what the board/MCU can do. You will be able to get back to the datasheet in details more and more later on, but at least you already know what you could do. Do you think that professionals can remember everything of everything? Wrong. The key is to be smart enough to adapt yourself into different situations, for the rest there are datasheets there for you on purpose to remind you technical things. 

Anyway this is a fun time, so enjoy it! Relaxed️ 

  • I could do that in my younger days, but not now.

  • in reply to misaz

    Indeed everyone has his own way, I don't pretend to teach anything to anyone. I am sharing my opinion of course Wink

  • in reply to Digimorf

    This approach worked ten years ago but now the complexity of chips grown significantly. The informations which were in 8-bit era written in datasheet are not written in datasheet anymore. In case of PSoC documentation is split to Datasheet, Technical Reference Manual (TRM) which as two books (Architecture TRM and Registers TRM) and Programming Specification. All these documents have 75 + 601 + 2041 + 82 = 2799 pages and this is short documentation in comparison with some other ARM MCUs. Also note that these 2799 pages still do not contains all ifnromation and for information about Cortex-M core, instruction set and its peripherals like SYSTICK and NVIC you need to browse ARM Documentation which is about additional 1000 pages.

    Nowadays there is very few reasons to read documents other than first page of datasheet because you do not need to write peripherals driver and instead in most cases you just use SDK written by chip vendor Infineon (Cypress). It is mainly because complexity grown as I mentioned above. In 8-bit era ADC was about 2 to 4 8-bit registers containing few configurable options but ADC in PSoC 62 has 131 32-bit registers and supports storing several results, configuring advanced sequencing options, chaining operations, filtering and many other. Good luck when using it in this way. Rather see ADC example in ModusToolbox and let managing these 131 registers on Infineons SDK.

    It is possible to program PSoC62 in this ultra low-level way but it is very hard. I did it single time but I do not recomend wasting time with this approach.

  • in reply to robogary

    Hahaha, it happens all the times, and when you hear "Dinner is ready, come on!" you are shaking your foot in your hands to awake it. Rofl

  • in reply to genebren

    I can understand, you have found your way, and that's OK. You don't have to get everything from a datasheet at once. The important thing is to have an overall view of the MCU. At least you know you have DAC, Timers, SRAM or whatever you need. Then, following your todo list you will implement everything.