RASPBERRY PI PICO DEVICE MSC INCREASE SIZE

Don't forget that the Pico / RP2040 only runs USB 1.1. Even at 12 megabit/s, 128 megabyte is going to take a very long time to fill.

You'll probably need to look for examples of projects where people have done what you want, but with other processors.

The process is not as simple as using the TinyUSB example, changing the max size, and "pointing" to the SD Card. You have write the SD Card handler and figure out how to interface it with the communication that TinyUSB provides.

I already manage to send data via VCP, but 4MB file is around 1minute... too much time... that is why I am looking for a way to make it appear as a usb mass storage (MSC the rp2040) and that way copy/paste a file and then copy it at will with my firmware to the SDCARD.. 

in that case just using a flash chip that is big enough for the bioggest expected filesize + Firmware might do the trick.

in that case just using a flash chip that is big enough for the bioggest expected filesize + Firmware might do the trick.

Not a good solution will be..

if you increase the mass storage size that way.. you will need RAM too and might not be supported... look:

In that case, this function from the MSC example seems relevant.

// Invoked when received SCSI_CMD_READ_CAPACITY_10 and SCSI_CMD_READ_FORMAT_CAPACITY to determine the disk size
// Application update block count and block size
void tud_msc_capacity_cb(uint8_t lun, uint32_t* block_count, uint16_t* block_size)
{
  (void) lun;

  *block_count = DISK_BLOCK_NUM;
  *block_size  = DISK_BLOCK_SIZE;
}

this might have some useful info for adding more Ram:
https://forums.raspberrypi.com/viewtopic.php?t=316012
but I really think that just "making the device appear as 128MB" is more of a windows fallback quirk than actual vitrual size.
under linux I never saw the RP2040 appear with that size, just the size of the flash chip used.

Yes, already tried that, but that ENUMs are used also in:

more than meets the eye in that problem, but that indicates its just windows saying 128MB because it does not know better.
have you tried with a Linux OS? How does it react to the same config?

I know, it is a really good magic what raspberry does with pico in boot mode, waiting for the uf2 files, look:

replicating it to a normal firmware is not as easy as I expected.

But you said you don't care about the actual size.

So don't use the ENUM in the function I provided you.

That way it will report a different size to the OS.

FYI, I just tried it on Ubuntu and I see it as 128M:

and on Rapbian:

So I don't think it is a Windows "thing." I think the bootloader is reporting maximum size. Which, makes sense. That way they can support almost any sized-Flash without the OS complaining.

Good to know that LInux uses this magic too