Search found 201 matches
- Sat Jul 31, 2021 12:34 pm
- Forum: General
- Topic: Building a RP2040-based device
- Replies: 7
- Views: 1754
Re: Building a RP2040-based device
You don't even have to populate the board with the SPI flash. Without the flash (or with empty flash), the board will behave the same as when bootsel was permanently pushed down. You can verify that the board works by plugging it to USB where it will start in the bootloader mode. You can also build ...
- Thu Jul 29, 2021 6:43 pm
- Forum: General
- Topic: Pi Pico - the most user un-friendly MCU?
- Replies: 313
- Views: 26593
Re: Pi Pico - the most user un-friendly MCU?
Exactly! That is why the aproch RPF decided to use is so good!
- Wed Jul 28, 2021 8:19 am
- Forum: General
- Topic: Pi Pico - the most user un-friendly MCU?
- Replies: 313
- Views: 26593
Re: Pi Pico - the most user un-friendly MCU?
As for, 'it will get improved over time', RPT position is that it's already working great on Windows and no improvement is necessary on their part. Well, somehow I don't see it like that. If they didn't care, they wouldn't take part in this discussion at all, and they do, quite heavily. They did al...
- Wed Jul 28, 2021 7:27 am
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
This would include: - disable all ADCs - turn of RTC - ensure that all GPIOs are not in a pullup/pulldown configuration - ensure that all GPIOs are not set for "output" - there may be a way to disable GPIO banks (some other MCUs have this) - there may be a way to turn off the USB interfac...
- Tue Jul 27, 2021 8:07 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
The SRAM arrays are responsible for a good chunk of the total static power dissipation, If that is the case then maybe in some future revisions of this chip or some new parts in the family, it would make sense to make it possible to fully power down some banks at the expense of loosing their conten...
- Tue Jul 27, 2021 5:58 pm
- Forum: General
- Topic: Pi Pico - the most user un-friendly MCU?
- Replies: 313
- Views: 26593
Re: Pi Pico - the most user un-friendly MCU?
I think the approach RPF took for the pico-sdk is just great. While the microcontroller itself might not be the best fit for some of my projects, I just enjoy the development on this platform. I was and still am impressed on how well they did it and I am very happy they didn't use IDE approach. None...
- Tue Jul 27, 2021 3:08 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
I soldered the flash back to be able to easily disable all the memories. The power consumption I got on dormant mode was ~390uA. After disabling all the memory banks via syscfg_hw->mempowerdown, it was reduced to 280uA. So all the memory banks seems to consume ~110uA of current. The flash itself (wh...
- Mon Jul 26, 2021 3:45 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
Just for the records, I managed to make a testing setup. ~380uA was the best I could get with rp2040 on a minimal board, without flash, no pull resistors on the board - just the chip, some required capacitors and a crystal. I am measuring the current on the output of the linear regulator and I'm run...
- Mon Jul 26, 2021 2:11 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
It would be a shame if someone did discount using an RP2040 because of the headline "180uA" figure if it can indeed go lower. Exactly. It seems like it should be possible to go lower than that, we just don't know how much lower. With current situation of chip shortage it is hard to measur...
- Mon Jul 26, 2021 2:03 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
Also is is worth noting that the datasheet says:
So I assume this is the consumption of only RP2040, not the Pico board.For power consumption of the Raspberry Pi Pico, please see the Raspberry Pi Pico Datasheet.
- Mon Jul 26, 2021 12:48 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
Does going into dormant mode preclude running code in RAM rather than flash because of the 20nS recovery requirement of the RAM (=two clock cycles at 100MHz)? I'd presume the first thing it does is to read an instruction when triggered out of dormant mode? I would expect so. But you don't have to p...
- Mon Jul 26, 2021 11:08 am
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
If you power SRAM off it does lose its contents, its not flash. You are right - it makes sense that if you power the memory down completely , it looses its content. The fact that it is SRAM only means that we don't have to refresh the memory. But the datasheet is stating the content is retained. So...
- Mon Jul 26, 2021 9:06 am
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Re: Current consumption on sleep modes
So, to be clear, I'm not doing any direct comparisons, I am interested in understand what makes some micro controllers able to go into 1-digit uA current sleep and not others. at the cost of loosing the contents for a chunk of ram, you can probably get the power usage even lower The idea of RAM cons...
- Sun Jul 25, 2021 7:57 pm
- Forum: General
- Topic: Current consumption on sleep modes
- Replies: 30
- Views: 18142
Current consumption on sleep modes
If you come from the SBC world, the power consumption of the RP2040 seems great and you feel like it can work on a battery forever (compared to RPI, for example). If, on the other hand, you come from the microcontroller world, the 180uA in dormant mode seems very high - like at least one order of ma...
- Tue Jun 04, 2013 9:07 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c pulse stretch
- Replies: 2
- Views: 1000
Re: i2c pulse stretch
Unfortunately, AFAIK it's not driver issue but hardware issue. As such, it may (but doesn't have to, maybe there is some workaround possible) be not fixable.
- Tue Jun 04, 2013 8:49 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c pulse stretch
- Replies: 3
- Views: 1325
Re: i2c pulse stretch
You can also use software bitbanged GPIO driver. You need kernel recompilation for that currently, though. You can take a look at this thread for some more information.
- Mon May 27, 2013 9:08 pm
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: Anyone interested in testing my avrdude with SPI support?
- Replies: 23
- Views: 12145
Re: Anyone interested in testing my avrdude with SPI support
Seems to be working with my atmega328p, using exacly the same wiring as for linuxgpio driver. I was able to properly read fuses and program some basic blink application. Great job! The only problem I have found (but I believe it may be in spi driver, not in your code) is that if I use linuxgpio driv...
- Tue May 14, 2013 7:26 pm
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
Since you are using your own compiled kernel, you have to ensure that it is not overwriten by apt-get update. There are couple of ways you can achieve this. What I'm doing is to rename kernel.img to kernel-my.img and add kernel=kernel_my.img line to config.txt. This makes bootloader use kernel_my.im...
- Tue May 14, 2013 3:28 pm
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
When you update the system with apt-get, your kernel may be updated (and it seems it was the case). The kernel consists of kernel.img file in /boot/ directory and of modules files in /lib/modules directory. It seems that you only overrides kernel.img file and not modules files. This causes your inco...
- Mon May 13, 2013 6:36 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
Check that you have w1-gpio and w1-therm kernel modules.
- Sun May 12, 2013 7:40 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
This is exacly what I was expecting when writing my last post in this thread. Good to hear that you managed to figure out yourself how to compile those modules. And by the way, the answer from SE that you quoted is actually mine. Noticed that in the middle of reading it :)
- Fri May 10, 2013 11:22 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
It's not distribution specific for sure. It may be kernel specific but I doubt it. I'm using latest raspbian image with my custom made kernel. And now that I think about this - this may be the cause of your problem. There is no gpio_pcf857x module in official raspberrypi's kernel. Are you able to lo...
- Fri May 10, 2013 11:00 am
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
I think I should have an entry "gpioXXX" in /sys/class/gpio after initializing the chip but I continue having the initial entries... Yes, you should have additional gpioXXX directory in /sys/class/gpio. And it works perfectly fine for me. But it only appears if i specify first argument to...
- Thu May 09, 2013 7:36 pm
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
You can write anything you want as a frist argument to new_device. For example this wont give you an error: echo blah 0x20 > /sys/bus/i2c/devices/i2c-0/new_device Here's what I get from dmesg: i2c i2c-0: new_device: Instantiated device blah at 0x20 But of course it doesn't work. There is no driver f...
- Thu May 09, 2013 4:28 pm
- Forum: Interfacing (DSI, CSI, I2C, etc.)
- Topic: i2c configuration
- Replies: 25
- Views: 17639
Re: i2c configuration
Are you sure that your device is pcf8574 and not pcf8574a or pca8574? Try those two as a first argument to /sys/bus/i2c/devices/i2c-1/new_device. Hint, you can remove previously created device using
Code: Select all
echo 0x3a > /sys/bus/i2c/devices/i2c-1/delete_device