16 thoughts on “Pic assembly language update: #2.2 – pipelines harvard”
Hi Julian, thank you 4 the pic micro series using the pic12f675, have had many years break from digital electronics as a hobbyist, & annoyed @ myself 4 letting it slip, but your small series got me back again. I was just about 2 quit @ the end of the last vid, as my led was dim, yet not blinking, but remembered on the 11th hr, in the back of my mind that MCLRE must be tied HIGH at the end of the day, so i changed Bit 5 in the CONFIG register, regards MCLRE, & set it LOW, so i had a better result with the config value 0x3fc6. Then it started blinking, as i build this on a bread board pin 4 was left "open" once i removed the ICSP wires from my PICKIT 3.
I had 2 tell myself " I'm Back "…. i'm pick'n again, felt good 2 see that led finally blink, one second b4 i quit & gave up.
Thanks a mil !! Look forwards to building more from your channel, analogue & digital.
Julian, I really enjoy your videos and presentation technique. I think I have watched almost all. I wanted to get back into assembly language programming ( I did quite a bit years ago with the 68HC11) and picked the PIC because your tutorials were really easy to follow, besides I happen to have almost 100 unused 16F84As laying around. I purchased one of those 12F675 boards you describe, a bunch of extra 675s, a PICkit3 clone and even a 3rd party simulator program. Well I think next week I will be going to the local Salvation Army resale store and look for a good used blender. I am going to convert the above into little particles and bury them in the field outside. Despite your careful tutorials, multiple trips to the Microchip site and hours of trial and error trying to get things to work I have not been able to verify successful programming of the device. I recommend you give some thought to doing tutorials on another processor that is supported by a rational, should I say, functional, development environment. I think I will move on to the 68S12.
Also, I think you'll find that the Atmel gets away with 1 instruction cycle = 1 clock cycle by using a PLL…. probably another reason why they're more expensive than PICs.
Great video, Julian! One of the hardest things for me to wrap my head around coming from high-level programming when I first started getting into hardware was the idea that hardware is always on. Procedural programmers don't think about the fact that ALU is still calculating even if you aren't running an arithmetic instruction, etc. Pipelining reminds me of that because you have to be open to the idea that you can fetch and write at the same time — and when that goto hits and you get the penalty, the fetched instruction doesn't go away — it's just that there is a circuit always running that blanks it to a nop when a branch gets taken.
Hi Julian, thank you 4 the pic micro series using the pic12f675, have had many years break from digital electronics as a hobbyist, & annoyed @ myself 4 letting it slip, but your small series got me back again. I was just about 2 quit @ the end of the last vid, as my led was dim, yet not blinking, but remembered on the 11th hr, in the back of my mind that MCLRE must be tied HIGH at the end of the day, so i changed Bit 5 in the CONFIG register, regards MCLRE, & set it LOW, so i had a better result with the config value 0x3fc6. Then it started blinking, as i build this on a bread board pin 4 was left "open" once i removed the ICSP wires from my PICKIT 3.
I had 2 tell myself " I'm Back "…. i'm pick'n again, felt good 2 see that led finally blink, one second b4 i quit & gave up.
Thanks a mil !! Look forwards to building more from your channel, analogue & digital.
Ernie H.
yes it would be nice to see more tutorial like adding delay loops or using timers ?
Hope there is enough interest to continue the series…
Its like this tutorial series stopped dead in its tracks before we got going. Would love to see more
Please follow this up. I'm eager to follow this down the rabbit hole
These are great videos, too bad this is the last one :(Regarding fosc/4, I suppose this is true for older 8-bit PICs, not for PIC32?
Thanks a bunch, Julian. You make a great teacher!
Did you make that video on branches yet? 🙂
It would be great to see further tutorials in this series!
Julian, I really enjoy your videos and presentation technique. I think I have watched almost all. I wanted to get back into assembly language programming ( I did quite a bit years ago with the 68HC11) and picked the PIC because your tutorials were really easy to follow, besides I happen to have almost 100 unused 16F84As laying around. I purchased one of those 12F675 boards you describe, a bunch of extra 675s, a PICkit3 clone and even a 3rd party simulator program. Well I think next week I will be going to the local Salvation Army resale store and look for a good used blender. I am going to convert the above into little particles and bury them in the field outside. Despite your careful tutorials, multiple trips to the Microchip site and hours of trial and error trying to get things to work I have not been able to verify successful programming of the device. I recommend you give some thought to doing tutorials on another processor that is supported by a rational, should I say, functional, development environment. I think I will move on to the 68S12.
I'm starting to forget everything now, will have to watch them all again I think.
as i have shill got the epe projects on pic 1, 2 mk3
i love this pic course , i would love to see how you build a serial pogrammer
Hi Julian have you done anything on 12v bullet cameras?
Next tutorial should be interrupts and NOPS – that would be very interesting!
Also, I think you'll find that the Atmel gets away with 1 instruction cycle = 1 clock cycle by using a PLL…. probably another reason why they're more expensive than PICs.
Great video, Julian! One of the hardest things for me to wrap my head around coming from high-level programming when I first started getting into hardware was the idea that hardware is always on. Procedural programmers don't think about the fact that ALU is still calculating even if you aren't running an arithmetic instruction, etc. Pipelining reminds me of that because you have to be open to the idea that you can fetch and write at the same time — and when that goto hits and you get the penalty, the fetched instruction doesn't go away — it's just that there is a circuit always running that blanks it to a nop when a branch gets taken.